Activities of "zhongfang"

• ABP Framework version: v8.0.5
• UI Type: Blazor Server
• Database System: EF Core (MySQL)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:

[09:51:14 WRN] Unhandled exception rendering component: Value cannot be null. (Parameter 'stringLocalizer')
System.ArgumentNullException: Value cannot be null. (Parameter 'stringLocalizer')
   at System.ArgumentNullException.Throw(String paramName)
   at System.ArgumentNullException.ThrowIfNull(Object argument, String paramName)
   at Microsoft.Extensions.Localization.StringLocalizerExtensions.GetString(IStringLocalizer stringLocalizer, String name)
   at Volo.Abp.FeatureManagement.Blazor.Components.FeatureManagementModal.<>c__DisplayClass43_5.<BuildRenderTree>b__21(RenderTreeBuilder __builder9)
   at Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder.AddContent(Int32 sequence, RenderFragment fragment)
   at Blazorise.SelectItem`1.BuildRenderTree(RenderTreeBuilder __builder)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)

• Steps to reproduce the issue:

• I define many features while ABP 4.1 or later
• All features I defined work very well. So I need not to maintain them.
• I have not got into https://localhost:44313/saas/host/editions for more than 1 year
• Now, I click functions for a edtion in above url, I got above exception.

Thanks! It has worked for my.

OH, i have "Reply to" noreply@abp.io.

I have sent again to liming.ma@volosoft.com just now.

I have sent mail to you. The mail includ a webtransfer short link.

Perhaps you can find in Junk box. I have sent successfully by qq mail. And I didn't receive a refund mail.,

I have sen you my Module project. Perhaps it has been created by ABP Suite 4, after update to 5, then to 6, then to 7, then to 8.0.0, then to 8.0.2... 8.0.4 I delete all involved module, and then packege for you to reproduce the error.

yes, I hav runned abp install-libs in proper path.

but how to check for leptonx updates while upgrading?

1. I use new package.json to run abp install-libs I always use new version Abp Suite to create a new Application. Then I got this package.json from new 8.0.4 newest Application under Blazor project:

{
  "version": "1.0.0",
  "name": "my-app",
  "private": true,
  "dependencies": {
    "@volo/abp.aspnetcore.mvc.ui.theme.leptonx": "~3.0.3",
    "@volo/aspnetcore.components.server.leptonxtheme": "~3.0.3",
    "@volo/cms-kit-pro.admin": "~8.0.4",
    "@volo/account": "~8.0.4",
    "@volo/language-management": "~8.0.4"
  }
}

2. two LeptonX packages are version 3.0.4.

a very old Module. And it can run correctly under my ABP 8.0.3 in the morning.

I upgrade my ABP from 8.0.3 to 8.0.4. Then I got above error.

I see a information in browser console. I pasted as below.

blazor.server.js?_v=638411564080000000:1 [2024-02-23T14:26:04.460Z] Information: Normalizing '_blazor' to 'https://localhost:44313/_blazor'.
localhost/:1 Third-party cookie will be blocked. Learn more in the Issues tab.
blazor.server.js?_v=638411564080000000:1 [2024-02-23T14:26:04.490Z] Information: WebSocket connected to wss://localhost:44313/_blazor?id=FsS-vjaaPLj9VmpNuguOJw.
utilities.js?v=1.4.1.0:303 Thank you for using the free version of the Blazorise component library! We're happy to offer it to you for personal use. If you'd like to remove this message, consider purchasing a commercial license from https://blazorise.com/commercial. We appreciate your support!

May I need to purchase a Blazorise comercial lisense?

• ABP Framework version: v8.0.4
• UI Type: Blazor Server
• Database System: EF Core (MySQL)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

• dotnet tool update -g volo.abp.cli
• abp suite update
• run abp install-libs under Blazor.Server.Host
• start Debug under Visual Studio 2022
• first page (not logged in) is confused
• click 'log in' button. page is normal.

My problem has been resolved. Thanks for you quick reply.