Activities of "abpdevPro"

Description :- We customized the Suite MVC templates for :-

1. Frontend.Mvc.Page.CreateModal.cshtml.txt
2. Frontend.Mvc.Page.EditModal.cshtml.txt The customized templates are complete in the Suite Templates UI (including footer actions and closing tags for the form / panel markup). After Save and generate for a new entity, the generated files :-

• Pages/.../CreateModal.cshtml
• Pages/.../EditModal.cshtml are only partially written.

Observed behavior :-

1. Generation writes the page header, opening form tag, panel/body chrome, and the injected property inputs (from the main entity tab placeholder).
2. Generation then stops.
3. Everything after the property fields is missing: footer actions, closing panel tags, and the closing form tag.
4. This causes Razor build errors such as malformed form tag helper (start tag without end tag).
5. Sometimes markup near the top of the generated modal is also corrupted (e.g. a tag’s opening portion is dropped and only attributes remain).

Expected behavior :- Suite should emit the full customized template after placeholder replacement, including all content after the property-injection placeholder (footer and closing tags).

Important notes :-

• The customized template content in Suite is complete before generate; the footer is not missing from the template itself.
• Default (non-customized) Create/Edit templates generate correctly for us.
• The problem appears when Create/Edit templates are customized away from the default abp-modal structure (we use a custom off-canvas-style layout with Suite placeholders and suite-custom-code-block-* markers).
• Removing Suite fingerprint/hash lines (##...##) from the template does not fix truncation.
• Reproducible across entities and modules when the same customized Create/Edit templates are used.
• Backend generation (entity, app service, etc.) generally succeeds; this is specifically the MVC Create/Edit cshtml output.

Steps to reproduce :-

1. Open ABP Suite for an MVC module solution.
2. Customize Frontend.Mvc.Page.CreateModal.cshtml.txt and Frontend.Mvc.Page.EditModal.cshtml.txt (replace default modal chrome with a custom panel layout; keep Suite placeholders such as the main entity tab placeholder and custom-code-block markers).
3. Create a new entity with a few properties (string/bool/enum is enough).
4. Enable UI generation and click Save and generate.
5. Open the generated CreateModal.cshtml / EditModal.cshtml.

Result :- Files end after the last generated property input; footer and closing tags are absent; project fails to build.

Workaround :- After every generate, manually append the missing footer and closing tags to Create/Edit cshtml files.

Questions for support :-

1. Is this a known issue with customized CreateModal/EditModal templates when the structure differs from default abp-modal?
2. Is there a supported template pattern (marker order / placeholders / custom-code blocks) that guarantees content after the main entity tab placeholder is always written?
3. Can Suite validate that generated Create/Edit cshtml still contains a closing form tag and fail the generate step loudly if not?
4. Is there a recommended way to customize Create/Edit UI (off-canvas/panel) without hitting this truncation?

Environment :-

• ABP / Suite: 10.5.0
• Target framework: .NET 10
• UI: MVC
• OS: Windows 11
• Happens on multiple developer machines with the same customized templates.

Hi ABP Support Team,

We are evaluating the Newsletter feature available in CMS Kit Pro and would like to understand its capabilities regarding email delivery.

Based on the CMS Kit Pro Newsletter documentation, we can see that the module currently supports:

Newsletter subscription management Subscriber listing Exporting subscribers as CSV

However, we could not find any documentation related to sending emails or managing newsletter campaigns.

Could you please clarify the following: We need guidance on:

Does CMS Kit Pro provide any built-in functionality to send emails/newsletters to subscribed users?

If email sending is supported, what is the recommended approach and which APIs/services should be used?

Is there any UI available for creating and sending newsletter campaigns?

If this functionality is not currently included, is the expected approach to export subscribers and implement a custom email campaign solution using ABP's Emailing infrastructure or an external provider?

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

Hi Team,

We are facing an issue with ABP Suite when trying to add ABP module entities as navigation properties inside our custom modules.

What works: When importing ABP modules into the main solution and adding them as navigation properties on entities — this works correctly without any issues.

What doesn't work: When importing the same ABP modules inside a custom module (a separate module in the solution), we are unable to see or add ABP module entities as navigation properties on entities within that module.

What we tried:

1. Added the ABP package reference directly inside the custom module project
2. Re-opened ABP Suite after adding the reference
3. Still unable to select ABP module entities as navigation properties in the Suite UI

Expected Behavior: After adding the ABP package reference in a custom module, ABP Suite should recognize and expose the ABP module entities as available navigation property targets for entities within that module — consistent with how it behaves in the main solution.

Environment:

1. ABP Suite Version: [your version]
2. ABP Framework Version: [your version]
3. Project Type: Modular / DDD
4. DB Provider: [EF Core / MongoDB]

Steps to Reproduce:

1. Create a custom module in ABP Suite
2. Add an ABP package reference (e.g., Volo.Abp.Identity) to the module
3. Open an entity in that module in ABP Suite
4. Attempt to add a navigation property pointing to an ABP module entity (e.g., IdentityUser)
5. The ABP entity does not appear as an option

Please advise on whether there's a specific configuration required to enable this at the module level, or if this is a known limitation/bug.

Thank you

Hi Team,

We are currently using the CMS Kit PRO module in a multi-tenant setup and facing an issue in the production environment.

Issue Summary

In the local environment, everything works as expected:

• Creating pages, blogs, and menus
• Setting a page as the home page for a tenant via the admin dashboard
• All content is visible correctly on the public website

However, in the production environment:

• Menus are not visible unless the user is logged in
• The home page configured from the admin dashboard is not visible publicly
• Content seems restricted to authenticated users only

Expected Behavior

• Menus and home page content should be visible to anonymous users (public access), same as local setup

Questions

• Is there any configuration we might be missing for production?
• Are there any permissions, caching, or environment-specific settings required for public visibility?
• Anything specific to multi-tenancy or CMS Kit PRO that behaves differently in production?

Additional Info

• Local environment: Working correctly
• Production environment: Issue persists consistently

Would appreciate your guidance on what could be causing this.

Hi Team,

We previously connected for an overview of the AI Management Module, and I've been following the same setup steps since then.

With OpenAI (embedding + vector database setup), everything works as expected — I can upload and manage data sources and get responses from the playground without any issues.

However, when switching to Ollama, I'm getting the following error in the playground:

"Error with tool" or "Unable to retrieve information"

I've attached screenshots covering the full setup and the error for your reference. Please let me know if any additional configuration is needed for Ollama or if there's a known compatibility issue.

Looking forward to your guidance!

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.