CmsKit implement problem #10271

4 Answer(s)

• 

  0

  yazilim.ithinka created one month ago

  We are waiting for your response so we can move forward with our project. Do you have an answer?

  Save Cancel
• 

  0

  enisn created one month ago

  Support Team .NET Developer

  It seems you added following packages to your backend application:

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

  But Application layer is missing, this is where AppServices are located. Canyou add Volo.CmsKit.Pro.Applicaton package to your project and try again?

  Save Cancel
• 

  0

  yazilim.ithinka created one month ago

  

  As you said, I added the Volo.CmsKit.Pro.Application package, but there was no change in the menus or redirects; the same errors persist.

  Save Cancel
• 

  0

  enisn created 2 days ago

  Support Team .NET Developer

  Hi there,

  As I see you're having trouble getting CmsKit Pro working in your microservice template. Let me help you fix this.

  The Problem

  When you add CmsKit Pro to your project, you're only getting the Pro features but missing the base CmsKit (open-source) tables. That's because CmsKit Pro doesn't include the base CmsKit - they're two separate modules that need to be installed together.

  What You Need to Do

  Step 1: Add Both Packages

  In your EntityFrameworkCore project (AdministrationService), make sure you have:

  <!-- Base CmsKit (required!) -->
  <PackageReference Include="Volo.CmsKit.EntityFrameworkCore" />
  <PackageReference Include="Volo.CmsKit.Domain" />
  
  <!-- CmsKit Pro -->
  <PackageReference Include="Volo.CmsKit.Pro.EntityFrameworkCore" />
  <PackageReference Include="Volo.CmsKit.Pro.Domain" />
  

  The same applies to your Web.Public project.

  Step 2: Update Module Dependencies

  In your EntityFrameworkCore module, add the base CmsKit module:

  [DependsOn(
      typeof(CmsKitProEntityFrameworkCoreModule),
      typeof(CmsKitEntityFrameworkCoreModule)  //👈 Add this!
  )]
  public class YourServiceEntityFrameworkCoreModule : AbpModule
  {
  }
  

  Step 3: Enable Both Global Features

  In your GlobalFeatureConfigurator (or create a FeatureConfigurer class), enable both:

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

  Step 4: Run Migration Again

  After making these changes:

  1. Rebuild your solution
  2. Add a new migration: dotnet ef migrations add CmsKit_Complete
  3. Update your database

  Now you should see both CmsKit tables (CmsUsers, BlogPosts, Pages, Tags, Comments, etc.) and CmsKitPro tables (NewsletterRecords, Polls, Faqs, PageFeedbacks, etc.) in your database.

  ---

  The CmsKit Pro module adds extra features (Newsletter, Polls, FAQ, Page Feedback, etc.) but it doesn't include the base CMS features (Pages, Blogs, Comments, Ratings, etc.). They're designed to work together but remain separate packages.

  Future: Creating a Separate CmsService

  If you want to create a dedicated CmsService in the future, just follow the same pattern - add both base CmsKit and CmsKit Pro packages to that service's EF Core project.

  Let me know if you run into any other issues!

  Save Cancel