I have double-checked, it work as expected Hi, I just create a new project and done all the steps you were mentioned (including db migration also) , shows the same result.
Hi, The same issue is still there, can you share the add migration and update database code using CLI ?
Hi,
I guess you are missing this step: https://support.abp.io/QA/Questions/5982#answer-3a0e4ac8-9583-fd36-2fe6-fb67b60f678a
I have shared the project with you. you can check your email.
Hi, It's already there, and I copied from your code, pasting it into my project, but the result remains the same. I also attempted to run your code, and I encountered the same result. Could this be related to a database issue? I recently deleted the CMS tables, added a new migration for CMS, and updated the database.
Hi
1 Install the CMSKit packages:
2 Add module dependencies
3 Add MyGlobalFeatureConfigurator
https://support.abp.io/QA/Questions/5982#answer-3a0e4ac8-9583-fd36-2fe6-fb67b60f678a
4 Configure the DbContext
5 Delete&Recreate the DB migration file
Hi, I have implemented all the changes, but the 'CMS' menu still hasn't appeared. All the updates have been pushed to the Git repository. Is there anything I missed?
Hi,
Please make the repo private, because it include your license code
Done.
Hi,
Can you share the project with me? I will check it. my email is shiwei.liang@volosoft.com
Hi, I sent you an email on October 17, 2023, containing details and a project link. However, I did not receive a response. I have already sent a follow-up email. I am looking forward to your response and the resolution of this matter at your earliest convenience.
Hi,
Oh, the single-layer template missing the
GlobalFeatureConfigurator
class.You can add the
GlobalFeatureConfigurator
to your project manually.For example:
public class MyGlobalFeatureConfigurator { private static readonly OneTimeRunner OneTimeRunner = new OneTimeRunner(); public static void Configure() { OneTimeRunner.Run(() => { GlobalFeatureManager.Instance.Modules.CmsKit(cmsKit => { cmsKit.EnableAll(); }); GlobalFeatureManager.Instance.Modules.CmsKitPro(cmsKitPro => { cmsKitPro.EnableAll(); }); }); } }
public class MyProjectNameModule .... { ..... public override void PreConfigureServices(ServiceConfigurationContext context) { MyGlobalFeatureConfigurator.Configure(); } }
PS: You also need to add the database migration file.
"I have completed all the steps you mentioned before, but the result remains the same; the 'CMS' menu is not displayed.
1.Create a single-layer Application. 2.Install the CMS Kit using NuGet Package Manager. 3.Create the 'MyProjectName' GlobalFeatureConfigurator file and copy the configuration code as well. 4.Add the configuration in the 'MyProjectName' Module. 5.Regarding the migration, we are currently experiencing an issue. We are unable to generate migration data directly, so we've been copying migration data from a multi-layer application.Its also working. Is there anything we missed?
Hi,
You may need to install the CMS kit module manually. The CLI doesn't support it yet.
Yes, I installed it from the NuGet Package Manager. After the installation process, we need to add code GlobalFeatureManager.Instance.Modules.CmsKit(cmsKit => { cmsKit.EnableAll(); }); in GlobalFeatureConfigurator in Domain.Shared but in Single layer application Where I can paste this code.
Hi,
As I understand, you want to install the CMS Kit module to the single-layer project.
Of course, you can do it.
But I'm unable to run it in a single-layer application. When I attempt to install the command 'abp add-module Volo.CmsKit.Pro' using CMD, it shows 'successfully installed,' but nothing actually gets installed. However, the same command works in a multi-layered application.
Is it possible to install a single-layer ABP Suite application CMS kit and create public pages using the CMS kit without requiring a master page or other components for a public project?