Overview
The issue "Modules move into ContentPane after duplicating a module on Interior.ascx skin" occurs post-upgrade from Evoq Content 9.4.4 to 9.13.9. This was traced to custom Breadcrumb code in the Interior.ascx skin, not pane definitions. Updating the custom Breadcrumb code resolved the issue.
Information
Issue: Modules move into ContentPane after duplicating a module on Interior.ascx skin.
Affected Version: Evoq Content 9.13.9
Resolution Steps:
-
Identify the Custom Code:
- Open the Interior.ascx skin file.
- Locate the custom Breadcrumb code that may not align with the new DNN version requirements.
-
Update the Custom Code:
- Obtain the latest .cs file for Breadcrumb from the updated DNN version.
- Apply your customizations to the new Breadcrumb code to ensure compatibility.
-
Test the Changes:
- Save the updated Interior.ascx file.
- Clear the site cache and recycle the app pool.
- Test module duplication to ensure modules remain in their respective panes.
Note: The issue was not related to missing runat="server" attributes in pane definitions, as initially suspected.
Frequently Asked Questions
- How do I know if this issue applies to my situation?
- If you experience modules moving to ContentPane after duplicating a module on a custom skin post-upgrade, this issue may apply.
- What if updating the Breadcrumb code doesn't resolve the issue?
- Ensure all custom code aligns with the new DNN version requirements. If issues persist, review other customizations for compatibility.
- Why did this issue arise after the upgrade?
- Major platform upgrades often enforce stricter requirements for custom code and skins, which can reveal previously unnoticed issues.
Priyanka Bhotika
Comments