Activities of "abpdevPro"

[maliming] said: hi

I have joined the repository.

But for an existing project , when we add CMS KIT , navigation links are getting updated but the CMS admin Module and Public site is not loading .

Can you share the steps?

Thanks.

We have shared repository access. Below are the exact steps we followed and the issue we are facing.

Steps Performed

1. We created a fresh ABP solution using ABP Studio:

   • .NET backend + Angular UI
   • Public Website option was NOT selected
   • CMS Kit was NOT selected during initial project creation

2. After project creation, we installed CMS Kit using the ABP CLI with the required configurations.

   • The CMS Kit installation completed successfull
   • All required database tables were created
   • Migrations ran without issues

3. At this point, we expected CMS Kit to be usable from the UI.

Expected Behavior

After installing CMS Kit, we expected:

• CMS Kit-related UI modules (Blogs, Pages, Menus, etc.) to appear
• Admins to be able to:
  • Create blog posts
  • Create CMS pages
  • Manage menus
• These pages/content to be usable once the public website is enabled

Actual Behavior

• CMS Kit tables exist in the database
• CMS Kit APIs/services seem installed
• However:
  • No CMS Kit module appears in the UI
  • There is no admin UI for managing blogs, pages, or menus
  • Public website functionality is not available

Done, You can check once.

Yes, sure - here you can find the attached github repo - https://github.com/Amitavpanda-omiyal/CMSModuleDemo

CMSModuleTest - is the project made of angular and .net - where we want to add CMSKit + Public website and want to have all features of CMS Kit.

Please once have a look.

Hi @maliming, can we get over a call, it will be easier for me to understand.

Yeah, but is there anyway that we can achieve in our case as we discussed above.

[abpdevPro] said: Hi @maliming,

We tried the same approach in our setup. Our Project A is an ABP solution with Angular UI + .NET backend.

1. After installing CMS Kit in Project A, the backend side (DB migrations, tables, etc.) got updated successfully, but we couldn’t see any CMS Kit UI/menu on the Angular side. From what we understand, the CMS Kit UI is currently available only for MVC/Razor Pages (and Blazor Server via MVC/Razor hosting), not for Angular, so our tenants won’t have a UI to manage pages/menus/content from the Angular application. For reference, the CMS management screen is working fine for us in a separate Razor Pages-based project (screenshot attached). -
   
2. Is there any official command or recommended approach to add the Public Website to an existing Angular + .NET solution (i.e., to generate/add the Web.Public project/folder into our current solution structure)? If there is no direct CLI command, please confirm the recommended way

Would appreciate guidance on the best supported path for an Angular UI solution where tenants need CMS management capabilities.

Hi @maliming , Need response from you on this - not satisifed with the response of AI.

Hi @maliming,

We tried the same approach in our setup. Our Project A is an ABP solution with Angular UI + .NET backend.

1. After installing CMS Kit in Project A, the backend side (DB migrations, tables, etc.) got updated successfully, but we couldn’t see any CMS Kit UI/menu on the Angular side. From what we understand, the CMS Kit UI is currently available only for MVC/Razor Pages (and Blazor Server via MVC/Razor hosting), not for Angular, so our tenants won’t have a UI to manage pages/menus/content from the Angular application. For reference, the CMS management screen is working fine for us in a separate Razor Pages-based project (screenshot attached). -
2. Is there any official command or recommended approach to add the Public Website to an existing Angular + .NET solution (i.e., to generate/add the Web.Public project/folder into our current solution structure)? If there is no direct CLI command, please confirm the recommended way

Would appreciate guidance on the best supported path for an Angular UI solution where tenants need CMS management capabilities.

Hi ABP Support Team,

We have an ABP Commercial project A (our main product) that is already live and running in production.

Now we have a new requirement for a subset of tenants: we want to provide CMS functionality (CMS Kit + Public Website) for those tenants.

To explore this, we created a separate ABP project B using the ABP template with CMS Kit and Public Website enabled, and we’ve already done some customizations in project B.

At this point, we want to bring this CMS capability into our main project A, and we are considering two approaches:

Option 1: Convert project B into a module and integrate it into project A

Make B a reusable module and then include it in A.

Option 2: Install CMS Kit + Public Website into project A directly, and migrate our customizations from project B

We need guidance on:

1. Which option is the recommended approach for long-term maintainability and upgrade safety (especially since A is already live)?
2. If option 1 is feasible, what is the recommended way to extract what we built in B (CMS + Public Website customizations) into a proper ABP module and integrate it into A (projects to reference, DependsOn setup, migrations, UI packages, etc.)?
3. If option 2 is preferred, what is the safest migration path to move the B customizations into A after installing CMS Kit + Public Website (including any typical pitfalls around global features, migrations, and unified admin/public layout configuration)? ​

Our goal is to keep one main solution (A), enable CMS features only where needed, and avoid creating an architecture that becomes difficult to maintain across ABP upgrades.

Thanks in advance for your recommendation and the best-practice steps to implement it.

I’m reviewing it now and will verify whether it’s working. I’ll get back to you with a response.

We are using CMS Kit Pro in our application. https://abp.io/docs/commercial/8.1/modules/cms-kit

Right now, the host admin (host) configures CMS Kit Pro and our users can use the features that the host admin has created (pages, blogs, etc.). Now we want to enable multi‑tenancy for CMS Kit Pro. https://abp.io/docs/2.1/Multi-Tenancy

The requirement is: Each tenant should be able to use CMS Kit Pro to create blogs, pages, newsletters, etc.

The end users of that tenant should be able to access this content without login (public website), similar to a WordPress site.​

Questions:

1.What is the recommended way to implement this scenario with CMS Kit Pro in a multi‑tenant application?

2.Is there any built‑in feature or recommended pattern for exposing tenant‑specific CMS content (pages newsletter subscription, FAQ, etc.)

3.Publicly without requiring authentication?

Do we need a separate public web site host per tenant, or can we have a single public site that serves different content based on the current tenant?

Any guidance or example configuration (especially for the public website + multi‑tenancy setup) would be very helpful.