Bug #92191
closed
Page tree not showing in workspace renamed page title after move
0%
Description
The page tree is not showing the correct name after moving a renamed record in a non-live workspace.
How to reproduce:
- Create page in live workspace
- Go to other workspace
- Rename a page
- You will see the new name in the page tree
- Move the renamed page to another parent
- You will now see the old name again
Updated by Dominic Petit over 3 years ago
We've seen this bug on version 10.4.14 too.
Updated by Riccardo De Contardi over 3 years ago
For now, I am not able to reproduce it on current master or 10.4.14 :/
Updated by Riccardo De Contardi 6 months ago
I think that I completely did my previous test wrongly; I repeated the test on:
10.4.37
11.5.35
12.4.14
13.2.0-dev
The test¶
1) LIVE workspace:
2) Create a page "AAAAA"
3) Go to a "Draft" workspace
4) Rename it "BBBBB"
5) Move it under another existing page
The result:¶
On version 11.5.35, 12.4.14, 13.2.0-dev the page is moved and its title is "BBBBB"; if you switch back to "LIVE" workspace, the page is still named "AAAAA" and it is still in its original position
Only version 10.4.37, the moved page is renamed ""AAAAA"! Plus, if you switch back to "LIVE" workspace, you will see that it is still in its original position, but the title has been changed to "BBBBB" (!!).
Switching again to "Draft" workspace, the page is moved to its new position and titled "BBBBB"
Updated by Riccardo De Contardi 5 months ago
- Status changed from New to Closed
I close this issue for now as it seems it affects only TYPO3 10
If you think that this is the wrong decision or experience the issue again on recent TYPO3 versions like 12 or 13 please reopen it or open a new issue with a reference to this one. Thank you
Updated by Benni Mack 5 months ago
Riccardo De Contardi wrote in #note-4:
I close this issue for now as it seems it affects only TYPO3 10
If you think that this is the wrong decision or experience the issue again on recent TYPO3 versions like 12 or 13 please reopen it or open a new issue with a reference to this one. Thank you
The reason why this is now solved is that we got rid of the MOVE placeholders in v11, before it was not possible to have it fixed.