Activities of "abpdevPro"

Hi maliming,

Thanks for the explanation. We applied your guidance and regenerated — the truncation is still happening.

What we changed On both customized templates (Frontend.Mvc.Page.CreateModal.cshtml.txt and Frontend.Mvc.Page.EditModal.cshtml.txt):

1. Moved footer actions, closing panel tags, and closing form tag outside the suite-custom-code-block-* markers.
2. Left blocks 2 / 3 / 4 as empty pairs (same pattern as the default modal template).
3. Kept each custom-code-block index used only once.
4. Kept the ##...## hash line on the disk files under .suite/customized-templates.
5. Confirmed the Suite Templates UI for this solution shows the updated content (footer after the empty markers, not inside them).

Relevant tail of CreateModal template after the placeholders:

What still happens after Save and generate Generated CreateModal.cshtml / EditModal.cshtml still stop immediately after the last property opening abp-input tag. Missing from the output:

• empty suite-custom-code-block-2/3/4 markers
• opening ta-offcanvas-body tag
• footer
• closing ta-offcanvas tag / closing form tag So this is not only “content inside custom-code blocks being stripped.” Even content after empty marker pairs is never written.

We also see this with Preserve custom code / Customizable code = true on the entity (first generate of a new entity, not a regenerate of an existing file).

Layout difference vs default We are not using the default abp-modal / abp-tabs structure. Our customized templates use a custom off-canvas panel (ta-offcanvas / ta-offcanvas-body / ta-offcanvas-footer) and place %%main-entity-tab%% + %%navigation-connection-lookup-tabs%% without wrapping opening abp-tabs tags / closing abp-tabs tags.

Default templates generate correctly. Only these customized Create/Edit templates truncate after the property placeholders.

Questions

1. Besides keeping footer markup outside custom-code markers, is an opening abp-tabs tag / closing /abp-tabs tag wrapper around the two placeholders required for Suite to emit anything after %%navigation-connection-lookup-tabs%%?
2. Is there another post-processing step (beyond custom-code-block removal and <abp-tab line removal) that drops the remainder of the template when the Create/Edit layout differs from the default modal?
3. Can you confirm whether content after %%main-entity-tab%% / %%navigation-connection-lookup-tabs%% is expected to always be emitted for customized templates, or is that currently unsupported unless the default modal/tabs chrome is kept?
4. What's the final soultion for this?

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

1. I tested this - it works fine in local when i open in incognito browser.
2. will try this too.
3. have updated it in the https://docs.google.com/document/d/1fS_wG1uZhVi99sYsYiRerRwmMpKW7qL0tsE6-qyulHY/edit?tab=t.0

https://docs.google.com/document/d/1fS_wG1uZhVi99sYsYiRerRwmMpKW7qL0tsE6-qyulHY/edit?tab=t.0 - update in the same docs. Once check and if anything else you required, do let me know.

once check now.

https://docs.google.com/document/d/1fS_wG1uZhVi99sYsYiRerRwmMpKW7qL0tsE6-qyulHY/edit?usp=sharing - here is the code , you can ask me for access once.

[maliming] said: reproduce

HI , Did this , but when we test in the local - it's working fine , even after changing the local environment to production.

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.