An error occurs when I load these two themes simultaneously. #10083

2 Answer(s)

• 

  0

  AI-Bot created yesterday

  Support Team ABP Agent

  1. Solution

  • You can’t load Lepton (v1) and LeptonX themes at the same time. Both modules register the same keys and services (e.g., AbpErrorPageOptions.ErrorViewUrls["401"], DefaultTheme, toolbar contributors, bundle names), which causes “An item with the same key has already been added” and “service not registered” errors. ABP supports only one active MVC theme per application.

  • Pick one theme and remove the other theme module(s) and registrations:

    • If you want LeptonX:
      • Remove AbpAspNetCoreMvcUiLeptonThemeModule from all DependsOn attributes and delete any custom module inheriting from AbpAspNetCoreMvcUiLeptonThemeModule.
      • Add AbpAspNetCoreMvcUiLeptonXThemeModule to your Web module DependsOn.
      • Remove any Configure<AbpErrorPageOptions>() entries you copied from Lepton to avoid duplicate keys; LeptonX already configures these.
      • Ensure you register the theme in AbpThemingOptions only once (DefaultThemeName should be LeptonXTheme.Name or let LeptonX register itself).
      • If you use LeptonX theme management/settings, add Volo.Abp.LeptonXTheme.Management.Domain.Shared to your Domain.Shared project and add [DependsOn(typeof(LeptonXThemeManagementDomainSharedModule))] to your domain shared module.
    • If you want Lepton (v1):
      • Remove AbpAspNetCoreMvcUiLeptonXThemeModule from DependsOn and any LeptonX nuget/package references.
      • Keep AbpAspNetCoreMvcUiLeptonThemeModule and its options.

  • Do not inherit one theme module from the other. Theme modules are independent and each configures its own services/options. Inheriting or registering both leads to duplicate option keys and missing service registrations for the “current theme” resolver.

  • After changes:

    • Clean and rebuild to ensure only one theme remains:
      • abp clean
      • dotnet restore
      • dotnet build
    • If you switched to LeptonX and see “Undefined setting: Volo.Abp.LeptonXTheme.ApplicationLayout”, add the LeptonX theme management shared module as noted above.

  Code example (use LeptonX only):

  using Volo.Abp.AspNetCore.Mvc.UI.Theming;
  using Volo.Abp.Modularity;
  using Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX;
  
  [DependsOn(
      typeof(AbpAspNetCoreMvcUiLeptonXThemeModule)
      // remove: typeof(AbpAspNetCoreMvcUiLeptonThemeModule)
  )]
  public class MyWebModule : AbpModule
  {
      public override void ConfigureServices(ServiceConfigurationContext context)
      {
          Configure<AbpThemingOptions>(options =>
          {
              // Don’t add Lepton and LeptonX together
              options.Themes.Add<LeptonXTheme>();
              options.DefaultThemeName = LeptonXTheme.Name;
          });
  
          // Remove duplicate error page mapping if you had both:
          // Configure<AbpErrorPageOptions>(options => { ... }); // Not needed for LeptonX
      }
  }
  

  If you need to switch themes dynamically at runtime, implement a single theme that changes its resources/layouts based on a setting or cookie rather than loading two different theme modules simultaneously.

  2. Sources

  • https://docs.abp.io/en/abp/latest/UI/AspNetCore/Theming
  • https://github.com/abpframework/abp

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  maliming created yesterday

  Support Team Fullstack Developer

  hi

  Could you share a template project to show the error?

  liming.ma@volosoft.com

  Thanks.

  Save Cancel