Attività di "mattw@agilenova.com"

Hello,

The module must be developed with the Module Entity Extensions system in mind. All the official modules support this system wherever possible. more

Also, you can generate a YourModuleExtensionConfiguration by inheriting from ModuleExtensionConfiguration.

There is no direct method for CmsKitModule.
It requires the type ModuleExtensionConfiguration for the action. You're right.

Regards

Hello,

I have a similar requirement. I wish to extend the CmsKitModule by adding extra properties. Is adding the Module Extension Configuration in the product roadmap for a future release (and, if so, when)?

Thanks

I found the issue. I had to manually assign the OpenId permission to the admin user in order to see the menu option.

I followed the migration guide to upgrade from ABP 5.3.x (commercial) to ABP 6.0.0 (commercial), including the addition of cadministration.SetSubItemOrder(OpenIddictProMenus.GroupName, 2); to MyProjectAppMenuContributor.cs. Per the screen snapshot, the menu is not appearing in the portal:

    //Administration
    var administration = context.Menu.GetAdministration();
    administration.Order = 5;

    //Administration->Identity
    administration.SetSubItemOrder(IdentityMenuNames.GroupName, 1);

    //Administration->OpenIddict
    administration.SetSubItemOrder(OpenIddictProMenus.GroupName, 2);

    //Administration->Language Management
    administration.SetSubItemOrder(LanguageManagementMenuNames.GroupName, 3);

    //Administration->Text Template Management
    administration.SetSubItemOrder(TextTemplateManagementMainMenuNames.GroupName, 4);

MyProjectWebModule.cs depends on the OpenIddictPro modules:

typeof(AbpOpenIddictProWebModule),
typeof(AbpAccountPublicWebOpenIddictModule),

• ABP Framework version: v6.0.0 Commercial
• UI type: MVC
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no (monolothic)
• **Theme: ** Lepton (not LeptonX)

Please advise.

Thank you. That's just what I needed to resolve the permission issue.

I am receiving an authorization exception when attempting to assign a tag to an entity using the cms-kit-admin-proxy.js in a custom page. The server trace includes: [12:13:51 INF] Request starting HTTP/1.1 PUT https://REDACTED/api/cms-kit-admin/entity-tags application/json 88 [12:13:51 INF] No CORS policy found for the specified request. [12:13:51 INF] Executing endpoint 'Volo.CmsKit.Admin.Tags.EntityTagAdminController.SetEntityTagsAsync (Volo.CmsKit.Admin.HttpApi)' [12:13:51 INF] Route matched with {area = "cms-kit-admin", action = "SetEntityTags", controller = "EntityTagAdmin", page = ""}. Executing controller action with signature System.Threading.Tasks.Task SetEntityTagsAsync(Volo.CmsKit.Admin.Tags.EntityTagSetDto) on controller Volo.CmsKit.Admin.Tags.EntityTagAdminController (Volo.CmsKit.Admin.HttpApi). [12:13:51 WRN] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "An internal error occurred during your request!", "details": null, "data": {}, "validationErrors": null }

[12:13:51 WRN] Exception of type 'Volo.Abp.Authorization.AbpAuthorizationException' was thrown. Volo.Abp.Authorization.AbpAuthorizationException: Exception of type 'Volo.Abp.Authorization.AbpAuthorizationException' was thrown. at Volo.CmsKit.Admin.CmsKitAdminAppServiceBase.CheckAnyOfPoliciesAsync(IEnumerable`1 policies) at Volo.CmsKit.Admin.Tags.EntityTagAdminAppService.SetEntityTagsAsync(EntityTagSetDto input)

I am executing the script as admin and have confirmed the following:

1. I can tag BlogPosts as admin in the portal and so default CMS tags are working.
2. I confirmed that the custom entity type exists, as it is visible in the portal.
3. I confirmed that required parameters are included in the Ajax proxy request: volo.cmsKit.admin.tags.entityTagAdmin .setEntityTags({ entityType: 'Value', entityId: valueId, tags: tags }) .then(function (result) { finishSaving(result); });

The CmsKit documentation refers to policies but I'm not sure if they are required or optional and where to define them on my Value entity type.

• CreatePolicies: List of policy/permission names allowing users to create tags under the entity type.
• UpdatePolicies: List of policy/permission names allowing users to update tags under the entity type.
• DeletePolicies: List of policy/permission names allowing users to delete tags under the entity type.

Please let me know how to resolve this exception. Do I need to define policies on the entities and, if so, how do I do that?

• ABP Framework version: v5.3.4
• UI type: MVC
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no (monolithic)
• Exception message and stack trace: See above
• Steps to reproduce the issue:
• 1. Define a custom entity type
• 2. Create a custom page with TagEditorViewComponent
• 3. Use volo.cmsKit.admin.tags.entityTagAdmin to add the tag to an existing entity

Hello,

Even after applying the :root css change, the collapsed menu is still displaying the default Lepton icon. Can I replace that with my custom logo as well?

I have deployed a dockerized, monolith deployment of ABP to an AKS cluster. When running with 1 pod, everything works. When I have > 1 pods behind a load balancer, I start getting JWT invalid / 401 errors for some requests. I am using IdentityServer4 with the default configuration.

I have enabled Redis by adding the Volo.Abp.Caching.StackExchangeRedis to my .Web csproj and updating appsettings.json to include:

"Redis": { 
 "IsEnabled": "true",
 "Configuration": "xxx.redis.cache.windows.net:6380,password=..."
}

My XXXAppWebModule.cs enables IDS using:

app.UseIdentityServer();

Is there anything else that I need to do to properly enable IDS in a clustered environment or have I completed the necessary steps?

CONFIGURATION:

• ABP Framework version: v5.2.1
• UI type: MVC
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no (monolith)

Thanks, Matt

Do you have an estimate on when v5.3.1 will be available? Thanks

Understood, that is the error that I receive when I attempt to publish and run the Web project in 5.3.0 even when the Polling feature is disabled.

dotnet publish "MyCompany.MyProduct.Web.csproj" -c Release -o /app dotnet /app/MyCompany.MyProduct.Web.dll**

[10:31:34 FTL] Host terminated unexpectedly! Volo.Abp.AbpInitializationException: An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module ... Culture=neutral, PublicKeyToken=null: The type 'qgApoZ2OmDdJqiAoXp5.L4ObZ82mStp54vqoB0A' is not a valid page. A page must define a public, non-static 'Model' property.. See the inner exception for details. ---> System.InvalidOperationException: The type 'qgApoZ2OmDdJqiAoXp5.L4ObZ82mStp54vqoB0A' is not a valid page. A page must define a public, non-static 'Model' property. at Microsoft.AspNetCore.Mvc.ApplicationModels.DefaultPageApplicationModelProvider.CreateModel(PageActionDescriptor actionDescriptor, TypeInfo pageTypeInfo) at Microsoft.AspNetCore.Mvc.ApplicationModels.DefaultPageApplicationModelProvider.OnProvidersExecuting(PageApplicationModelProviderContext context

I have made the change in Domain.Shared / XXAppGlobalFeatureConfigurator.cs. Although the Poll menu option is no longer visible from the admin portal, I am still receiving the same exception when running the published (precompiled) web project using the dotnet cli or in a docker container.