Activities of "Sturla"

Updating an entity with Suite is overriding everything in a MenuContributor!! The only thing I added was a one-to-many relationship so why its messing with the menu I don´t know...

it only leaves this

Try creating a Guid property for Blazor and get a generated error

Suit fails like this

I remember this being reported loooooong time ago somewhere..

Please add the nullable checkbox to all types

I want my strings to be nullable

and I can... but I need to manually do it in the suite json

then it shows up with 'N'

btw. Is somebody reading all of these suggestions?

Seems like you are the only one active in this thread

It does, doesn’t? 😅 Do they value my inputs or should I just stop?

Found it and got it by abp get-source Volo.Account.Pro --old

It would have been nice to have this documented somewhere.. no way to just know these things... but thanks anyways

I´m almost done but I need your help with Register.cshtml page. I have overriden the Login page but the Register page is causing me issues.

Its missing the Strength tracker, Show / hide icon, and caps-lock warning.

What I did was to get the LeptonX theme ( abp get-source Volo.Abp.LeptonXTheme.Pro --old) but there is no Register.cshtml file in there so have been trying to get it to work with this Register.cshml and that results in what you see on the image.

Am I missing something from You do it wrong! Customizing ABP Login Page Correctly (even though this is the Register page it should follow similar path, correct?)

Hope you can help me over the finishline with this one..

When trying to get the LeptonX theme (as shown in https://dev.to/enisn/you-do-it-wrong-customizing-abp-login-page-correctly-l2k) with CLI I get this error

Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown.

PS C:\Dev\LeptonX> abp get-source Volo.Abp.LeptonXTheme
[22:00:17 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli
[22:00:17 WRN] Volo.Abp.Studio.Extensions.StandardSolutionTemplates extension not found in the NuGet cache. Directory: C:\Users\sturlath\.nuget\packages\volo.abp.studio.extensions.standardsolutiontemplates\1.1.2\lib\net9.0
[22:00:17 INF] Volo.Abp.Studio.Extensions.StandardSolutionTemplates (v: 1.1.2) extension trying install from the NuGet

🕐  Checking extensions...
🧩 Extensions downloaded: Volo.Abp.Studio.Extensions.StandardSolutionTemplateslutionTemplates (v: 1.1.2) package downloaded from https://api.nuget.org/v3/index.jso
🚲 The CLI is restarting to apply the changes with arguments: get-source Volo.Abp.LeptonXTheme
PS C:\Dev\LeptonX> [22:00:52 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli
[22:00:52 INF] Downloading source code of Volo.Abp.LeptonXTheme (Latest)
[22:00:52 INF] Output folder: C:\Dev\LeptonX
[22:00:53 ERR] Downloading source code failed for: Volo.Abp.LeptonXTheme
Volo.Abp.Studio.AbpStudioException: Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown.
  at async Task Volo.Abp.Studio.Modules.Installing.SourceCodeDownloader.DownloadSourceCodeAsync(string moduleName, string targetFolder, string version, bool
     includeNightly)
  at async Task Volo.Abp.Studio.Cli.Commands.StudioGetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs)
  at async Task Volo.Abp.Studio.Cli.StudioCliService.RunInternalAsync(CommandLineArgs commandLineArgs)
  at async Task Volo.Abp.Studio.Cli.StudioCliService.RunAsync(string[] args)

I only managed to download it with abp get-source Volo.Abp.LeptonXTheme.Pro --old

New line in tables not working. At least not when using <br>

It works fine when in preview mode

| Column | | ------ | | • Some text <br> • Another text | | • With / br </br> • More text |

Looks fine here

But not when published, then there is no new line...

Is there maybe another way to acheive this?

Hi Maliming and Alper,

Thanks for the clarification. I’ve decided to keep ABP multi‑tenancy enabled even though the first release will have only one user per account, for these reasons:

1. Future multi‑user access – Account owners may later invite staff or content reviewers; multi‑tenancy gives me roles and isolation out‑of‑the‑box.
2. Editions & feature flags – I need the SaaS module to bundle limits (e.g., blog/landing‑page quotas etc.) and toggle new features for pilot groups or VIP customers. If I´m correct then multi-tenancy is needed for this, correct?
3. One‑offs for enterprise clients – With per‑tenant feature overrides (and connection strings) I can deliver bespoke functionality or move heavy customers to their own DB without refactoring. This is maybe the most unlicly scenario of the all but still a posibilitiy.
4. Easier forward than backward – Starting multi‑tenant now avoids the high cost of retro‑fitting TenantId filters, migrations, and per‑tenant workflows later.
5. Clean data isolation & compliance – Built‑in tenant boundaries simplify GDPR requests and potential future on‑premise deployments. (thinking about all of this has opened up the quite possible scenario of on-premise deployment).

I’ll hide the tenant selector on the login/registration pages (using the SignIn‑Without‑Tenant pattern) so the UX remains “email + password” only.

I’ve weighed the pros and cons, and although this approach might be a bit more complex upfront, I believe it will better futureproof the system—enabling it to handle a wide range of scenarios and simplifying updates and changes when the time comes.

Appreciate your guidance—just wanted to confirm the rationale behind staying multi‑tenant.

No there will only ever be one user per tenant. I see no reason why there would ever be another one.