Activities of "maksym"

• ABP Framework version: v5.3.1
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace: AbpException: Could not find the bundle file '/client-proxies/identity-proxy.js' for the bundle 'Volo.CmsKit.Admin.Web.Pages.CmsKit.Menus.MenuItems.IndexModel'!
• Steps to reproduce the issue:"

We initially created override code for the Menus page for the CmsKit in an MVC-based project without issues.

But now we are trying to migrate our infrastructure to Blazor and tried to override the CmsKit page the same way with no success.

Here are the page files we used to override CmsKit (which worked in MVC and not in Blazor):

And the problematic area seems to be here in the index.cshtml file

And gives us the following error:

Is there a way to generate these proxy javascript files?

We've tried everything from "abp install-libs" and deleting the yarn.lock files before to recreating a new Blazor solution from scratch and even trying to run the javascript proxy generator as well as reinstalling the Volo.Indentity.Pro module into the solution.

Yup, that worked!

Thanks for the help!

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.3.0
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace: 401
• Steps to reproduce the issue:"

We created a Module using ABP Suite and added the Feature support as explained in the documentation, but when using the RequiresFeature attribute, it doesn't work when the feature is set to "True".

I see the feature when editing features of an edition:

And in the database:

But when adding the RequiresFeature attribute to either a class or a method:

Always throws an error stating that the feature is not enabled. This is the error I copied from Audit Logging:

These are the Settings strings consts:

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v4.3.0
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• • Exception message and stack trace:
• Steps to reproduce the issue:"

We are unable to get dependency injection of ISettingManager in the constructor of a Blazor component we created to configure the settings for a module.

The module which uses the ISettingManager is as follows:

This has worked in a separate ABP Blazor solution, but in this case we have it in a separate module in another ABP solution and when visiting the respective page we get this error:

Hi, I guess you've created a new module and want to use the ISettingManager on it, right?

If so, please ensure you added the related depends on statement to your module class (ensure your domain module depends on the AbpSettingManagementDomainModule ([DependsOn(typeof(AbpSettingManagementDomainModule))])).

That is correct, I've created a new Module using ABP Suite and want to setup Settings specifically within that module.

I've already added that dependency to the Module's Domain Module:

reopening

I was wondering if it could be because it was a long-lived ABP solution and we did a lot of changes to it. But I created a brand new ABP Solution and created a module within that Solution and tried again and still couldn't get ISettingManagement to work in the module.

btw, I used ABP suite to create this module within the solution (both times) using this button:

Hi, were you able to replicate the issue? Or are you able to get ISettingManager in a module instantiated in an ABP solution?

Hi, were you able to reproduce the issue?

I've added virtual and async to the methods but the results are still the same.

As mentioned previously, the issue isn't in the feature management system itself not working, it's the fact that the feature which is set correctly in the database to "true"

Is still being read as "false" in abp via the feature checker