TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692015-12-16T18:06:28ZTYPO3 Forge
Redmine TYPO3 Core - Bug #72273 (Closed): In 6.2.16, publishing a deleted page containing a moved subpage...http://forge.typo3.org/issues/722732015-12-16T18:06:28ZSTI UdeS
<p>Publishing a deleted page from a workspace may recursively delete the whole website. This happens if the deleted page contains a child page that has been moved in the workspace.</p>
<p>This happens only since 6.2.16. In 6.2.15, we have an error that we cannot move a page that has been deleted but only the good pages are deleted.</p>
<p>How to reproduce:</p>
<p>In Live, create a page structure like this:</p>
<p>|-page1
|-page2
|-page3
|- subpage3-1
|- subpage3-2</p>
<p>Now go in a workspace, and do the following: <br /> 1) move subpage3-1 after subpage3-2 (this will create a move placeholder in the workspace for subpage3-1)<br /> 2) delete page3 (the page is marked as deleted in the workspace) (note: user must have recursive delete allowed to do that)</p>
<p>Now go to the workspace menu and publish all changes. This should delete page3 and all it's children in live<br /> -> this is what happen in 6.2.15<br /> -> in 6.2.16, ALL live pages are deleted recursively!! (including page1, page2 and their subpages...)</p>
<p>It seems that while recursively deleting the subpages of page3, the new code now deletes the move place holder, but then continues to recursively delete pages with a PID of 0.</p>
<p>This might be related to the fix introduced by <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: Cannot delete record moved in draft (Closed)" href="http://forge.typo3.org/issues/39383">#39383</a> ?</p>