Custom site page based on page template can be accidentally deleted when propagating changes from a site template
Activity

Cynthia WilburnMarch 12, 2012 at 2:14 PM
Reopening to add 6.1.1 CE GA2. Close as Fixed.

Luyang TanFebruary 15, 2012 at 1:01 AM
PASSED Manual Testing following the steps in the description.
Reproduced on:
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 9fbc284ff2c4b5102647c3640c4ddbff2736f30d.
The page which based on a page template is deleted.
Fixed on:
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 89e805dcb7a16568e03f0b40bc6abde75fb2cf83.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: c771e7e7873adb140b1c1fee9421acbba94b022b.
The page which based on a page template is not deleted.

Jorge FerrerFebruary 12, 2012 at 1:45 AM
The root cause of this behavior is that the Layout.sourcePrototypeLayoutUuid is reused for linking to the source page for both site templates and page templates. But this causes some scenarios in which it is not possible to know where it points to.
This field is not absolutely necessary for implementing page templates, so the solution is to reserve it only for site templates.
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

Reporter

Labels
Branch Version/s
Backported to Branch
Fix Priority
Git Pull Request
Components
Fix versions
Affects versions
Priority
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support

This situation can only happen when a site was created from a site template and has propagation of changes enabled. Under this context follow these steps:
1. Create a new page based on a page template
2. Click Manage > Page and disable the propagation of changes from the page template.
3. Make a change to the page like moving a portlet (this step might not be necessary)
4. A message appears under the dockbar telling the user that a change has happened since the last propagation from the site template was done. Also there is a button that allows to "Reset" to the original. This message is wrong because that specific page was not "inherited" from the site template.
5. Click the "Reset" button.
Result: The custom page gets deleted when the reset to the site template occurs. It is worth noting that the reset does not delete other custom site pages that were not created from a site template
Expected result: The message of step 4 should not have appeared and the reset button should not appear either. In any case, executing a reset should never cause the page to be deleted.