Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Luyang TanLuyang Tan(Deactivated)Reporter
Jorge FerrerJorge Ferrer(Deactivated)Labels
Branch Version/s
6.1.xBackported to Branch
CommittedFix Priority
4Git Pull Request
Components
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Luyang Tan
Luyang Tan(Deactivated)Reporter
Jorge Ferrer
Jorge Ferrer(Deactivated)Labels
Branch Version/s
6.1.x
Backported to Branch
Committed
Fix Priority
4
Git Pull Request
Components
Fix versions
Affects versions
Priority
Zendesk Support
Zendesk Support
Zendesk Support
Created February 6, 2012 at 10:00 AM
Updated June 24, 2023 at 3:55 PM
Resolved March 12, 2012 at 2:26 PM
Reproducing this ticket is tricky because it only occurs some times. The problem happens when the site template is exported to update an existing site. That export does not include the content because it is not needed for an update. If later a new site is created, the export of the last time is fixed.
Here is one way to reproduce it:
1) Create a site template (or reuse an existing one) and create a web content inside. Add an Asset Publisher in a page to show that content for easier testing.
2) Create a site called "Site A" from the site template with propagation of changes enabled. Check that it has been created with the content copied over.
3) Go to the site template and move a portlet to a different column (the goal here is to make any change that fires a propagation of changes).
4) Create a new site called "Site B"
Result: "Site B" does not have the content.
Expected result: "Site B" should have the content copied over.