Project

General

Profile

Actions

Bug #72273

closed

In 6.2.16, publishing a deleted page containing a moved subpage will delete the whole web site!

Added by STI UdeS over 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Workspaces
Target version:
Start date:
2015-12-16
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
medium
Is Regression:
Yes
Sprint Focus:

Description

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.

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.

How to reproduce:

In Live, create a page structure like this:

|-page1 |-page2 |-page3 |- subpage3-1 |- subpage3-2

Now go in a workspace, and do the following:
1) move subpage3-1 after subpage3-2 (this will create a move placeholder in the workspace for subpage3-1)
2) delete page3 (the page is marked as deleted in the workspace) (note: user must have recursive delete allowed to do that)

Now go to the workspace menu and publish all changes. This should delete page3 and all it's children in live
-> this is what happen in 6.2.15
-> in 6.2.16, ALL live pages are deleted recursively!! (including page1, page2 and their subpages...)

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.

This might be related to the fix introduced by #39383 ?


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #39383: Cannot delete record moved in draftClosed2012-07-30

Actions
Related to TYPO3 Core - Task #72291: Extend workspace functional tests on placeholder deletionClosedOliver Hader2015-12-17

Actions
Actions

Also available in: Atom PDF