Activities of "abpdevPro"

Hello Team,

In our previous tickets, we raised concerns regarding CMS functionality not working properly in Angular-based ABP projects.

We recently noticed that in the 10.1 final milestone (https://github.com/abpframework/abp/milestone/131?closed=1 ), the following items have been implemented:

• Angular – Implementing the CMS Kit module features
• Angular – Dynamic Form Component
• Dynamic form component

However, the official documentation does not yet appear to reflect these updates, particularly regarding installation steps, configuration, and integration guidance for Angular projects. We are planning to implement CMS Kit in our Angular-based solution before March, and clear documentation is critical for us to proceed confidently.

Could you please guide us on:

• The correct installation steps for CMS Kit in Angular projects
• Required module dependencies and configurations
• Any breaking changes or migration notes
• Expected timeline for documentation updates

Looking forward to your guidance.

Thank you.

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.

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.

We are following this articles to customise the sidebars - https://abp.io/docs/latest/framework/ui/angular/component-replacement?_redirected=B8ABF606AA1BDF5C629883DF1061649A#how-to-replace-a-layout https://github.com/abpio/abp-commercial-docs/blob/dev/en/themes/lepton-x/how-to-use-lepton-x-components-with-angular-custom-layout.md

Initially we used to do it in our previous projects and it was working completely fine. We were using app.module.ts (Traditional Module-Based Configuration).

With ABP studio new update - we were using app.config.ts (Standalone API-Based Configuration)

we are following the appraoch that we used to follow and the imports

import { LpxSideMenuLayoutModule } from '@volosoft/ngx-lepton-x/layouts'; import { LpxResponsiveModule } from '@volo/ngx-lepton-x.core';// optional. Only, if you are using lpxResponsive directive

these imports I am doing in app.config.ts ,

We are able to see the Customised Sidebars in the UI, but none of the leptonX components are visible in the UI.

like <lpx-navbar></lpx-navbar>, <lpx-footer></lpx-footer> and all.