CmsKit implement problem #10271

• Template: microservice
• Created ABP Studio Version: 1.3.3
• Current ABP Studio Version: 1.4.2
• Multi-Tenancy: Yes
• UI Framework: angular
• Theme: leptonx
• Theme Style: system
• Theme Menu Placement: side
• Run Install Libs: Yes
• Database Provider: ef
• Database Management System: postgresql
• Mobile Framework: react-native
• Public Website: Yes
• Social Login: Yes
• Include Tests: Yes
• Dynamic Localization: Yes
• Kubernetes Configuration: Yes
• Grafana Dashboard: Yes
• Use Local References: No
• Aspire: Yes
• Optional Modules:
  • GDPR
  • FileManagement
  • TextTemplateManagement
  • AuditLogging
  • OpenIddictAdmin
• Selected Languages: English, Turkish
• Default Language: English
• Create Command: abp new CarbonAI -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --aspire --dont-run-bundling -no-language-management -file-management

Pakages: 9.3.5

Hello In our project, we want to make adjustments to our public site using the CmsKit module. We want to create new menus, adjust menu content, visual positioning, and card designs for the pricing page. As a result, it was said that the CmsKit module could provide this, but when we reviewed the documentation and wanted to add it to our project, we encountered problems. When we added the CmsKit.Pro module, we were told that the CmsKit module could also be used, but when we added the CmsKit.Pro module, we encountered issues with missing menus and navigation, and we couldn't see the tables and menus within CmsKit. Additionally, when we imported CmsKit.Pro from the Nuget menu via Abp Studio, we noticed that the required packages were missing or not present at all. When we tried without adding a different package, it didn't work either. I'm sharing an example below.

When we add Volo.CmsKit.Pro to the Web.Public service (via AbpStudio Nuget)

Volo.CmsKit.Pro.Admin.Web Volo.CmsKit.Pro.Public.Web Volo.CmsKit.Pro.Web

The packages were included by default, but they were not added to the project.

In AdministrationService, however,

Volo.CmsKit.Pro.Admin.Application.Contracts Volo.CmsKit.Pro.Public.Application.Contracts

They were selected by default, but they weren't loaded in the same way.

What we added manually to AdministrationService

Volo.CmsKit.Pro.Domain Volo.CmsKit.Pro.Domain.Shared Volo.CmsKit.Pro.EntityFrameworkCore Volo.CmsKit.Pro.HttpApi

We added the packages.

After setting up this structure, when we performed the migration, we saw that we could only access CmsKit.Pro's tables, but we noticed that the tables related to CmsKit were not included. There were explanations stating that CmsKit could be used within the scope of CmsKit.Pro's usage.

AdministrationService

Web.Public

Here

GlobalFeatureManager.Instance.Modules.CmsKit(cmsKit =>
{
    cmsKit.EnableAll();
});

We get an error when we try to add it.

The menus that appear when we add CmsKit.Pro (Administration and CMS) )

Errors we receive when trying to access menus and URL information

http://localhost:44302/Cms/Faqs

http://localhost:44302/CmsKit/Newsletters

http://localhost:44302/Cms/PageFeedbacks

http://localhost:44302/Cms/Polls

http://localhost:44302/Cms/UrlShorting

http://localhost:44302/SettingManagement

How can we resolve the issue we are experiencing here? Where should we add which package or module? In terms of routing, where should we configure it and how? Unfortunately, the current documentation is insufficient for us. Our priority right now is to resolve this issue.

Additionally, we are currently performing our operations through AdministrationService and Web.Public, but in the future, we will be running CmsKit.Pro control with a separate service, such as CmsKitService and Web.Public. In this case, when we add the CmsKit.Pro module to the new service we have opened, we would appreciate it if you could provide us with detailed configuration settings on which packages and modules need to be loaded to avoid any problems.

Thanks.