Activities of "yekalkan"

Hi again @LinchArnold,

Now I reproduced the issue, fixed it internally and added it to next patch release.

For now, i can provide you a simple but dirty workaround if this is urgent for you:

1. Change the name of DbContext interface file (I{Your_Project_Name}DbContext.cs) in your project to something else (example: Random_Name.cs).
2. Generate your entity via suite.
3. Revert the file name.
4. Manually add the new entity to DbContext interface file. (Line to add: DbSet<{Your_Enttiy's_Name}> {Your_Entity's_Name_Plural} { get; set; })

Be sure to rename both MongoDb & EfCore DbContext interfaces before entity generation, but do not take any action for DbContext classes.

Can you try AccountResource instead of AbpAccountResource?

@LinchArnold Have you made any changes to *{You_Project_Name}DbContext.cs file after project creation? Can you share the file content?

There is a typo in the screenshot (AbpAccountrResource instead of AbpAccountResource). Does the error persist when you fix it?

What does the error say?

Namespace for AbpAccountResource is Volo.Abp.Account.Localization, and Volo.Abp.UI.Navigation.Localization.Resource for AbpUiNavigationResource.

using Volo.Abp.Account.Localization;

using Volo.Abp.UI.Navigation.Localization.Resource;

However, make sure that you are overriding these resources in a project/layer that references Volo.Abp.Account.Pro.Shared.Application.Contracts package. I suggest you to make these changes in the top layer (i guess HttpApi.Host for blazor) of your solution.

Hi @safi,

You overrided AbpUiNavigationResource localizations, and registration form localizations don't belong to that resource. So you need to override AbpAccountResource as well.

If there is anything that we can add in the JSON file (present in the localization folder) for this?

You won't change anything in your current localization files. You need to create another localization folder and configure it to extend the resource you want to change.

See Extending Existing Resource section in the documentation.

In your scenario, you need to extend AbpUiNavigationResource.

Localization key for administration menu is Menu:Administration.

example code:

services.Configure<AbpLocalizationOptions>(options =>
{
    options.Resources
        .Get<AbpUiNavigationResource>()
        .AddVirtualJson("/Localization/Resources/Test/Extensions");
});

/Localization/Resources/Test/Extensions/en.json file:

{
  "culture": "en",
  "texts": {
    "Menu:Administration": "Custom administration translate"
  }
}

Hi @safi

I answered this question at https://support.abp.io/QA/Questions/2413/Changing-the-name-of-Administration-menu-item#answer-c47fcd18-b187-5cae-4a43-3a0160d834cf

Hi @SushantPawar,

Client can change it in runtime using Language Management module. See screenshot below.

Also, you can also override the existing localization in development time, by extending AbpUiNavigationResource. See Extending Existing Resource section in the documentation.

If an extension file defines the same localized string, it overrides the string.