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?

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, awaiting response from you.

So currently , we cannot access the admin features currently in angular, so the admin will not be able to built web pages, menus and all in angular UI?

[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.