From b2ece0b0e573d7ce166da278ddd7771d1ce28a49 Mon Sep 17 00:00:00 2001 From: Enis Necipoglu Date: Thu, 19 Feb 2026 13:12:55 +0300 Subject: [PATCH] Docs: CMS Kit Pro package requirements Add an Important note to docs/en/modules/cms-kit-pro/index.md clarifying that CMS Kit Pro requires both the base Volo.CmsKit.* packages and the Volo.CmsKit.Pro.* packages. Notes that the `abp add-module Volo.CmsKit.Pro` command will handle this automatically, but if adding packages manually you must include both sets. --- docs/en/modules/cms-kit-pro/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/en/modules/cms-kit-pro/index.md b/docs/en/modules/cms-kit-pro/index.md index b7ce2f03d4..2aec352cab 100644 --- a/docs/en/modules/cms-kit-pro/index.md +++ b/docs/en/modules/cms-kit-pro/index.md @@ -54,6 +54,11 @@ If you want to add the CMS kit to your existing solution, you can use the ABP CL ```bash abp add-module Volo.CmsKit.Pro ``` + +> **Important**: CMS Kit Pro requires both the Pro packages **and** the base CMS Kit packages. The `add-module` command handles this automatically, but if you're adding packages manually, you need both: +> - `Volo.CmsKit.*` packages (base CMS Kit) +> - `Volo.CmsKit.Pro.*` packages (Pro features) + Open the `GlobalFeatureConfigurator` class in the `Domain.Shared` project and place the following code to the `Configure` method to enable all open-source and commercial features in the CMS Kit module. ```csharp