Bug #31663
Moving pages (and page content) in the Workspace does not work
| Status: | Resolved | Start date: | 2011-11-08 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Stefan Neufeind | % Done: | 0% |
|
| Category: | Workspaces | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.5 | Is Regression: | ||
| PHP Version: | Sprint Focus: | |||
| Complexity: |
Description
TYPO3 version 4.5.7, iOS X or Lion or PC
Moving pages (and page content) on the Workspace (via "drag and drop" on the page tree or using the "cut + paste it into"-function) does not work. If you want to move a page A into a page B, it may appear, but this is invalid after reloading the page tree. If you look at the menu item "workspace" it is to recognize that the changes are not registered/noted. The problem seems random and only on some pages and workspaces to appear. Moreover, the problem can be reproduced on other typo3 installations. Is there any adjustment missing out or can the problem be due to the allocation of rights? Since this is a very big typo3 project, all ext. that write into the page-table + DB have been cleaned + Log on MyISAM converted.
Related issues
Associated revisions
[BUGFIX] Respect move-placeholders when moving records in workspace
When moving records in a workspace existing move-placeholders
need to be taken into account to get values for pid/sorting
correct.
Change-Id: I973899f6940ced60800814a5ffb9271ffd58c8e5
Fixes: #31663
Releases: 4.5, 4.6, 4.7
Reviewed-on: http://review.typo3.org/6725
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader
[BUGFIX] Respect move-placeholders when moving records in workspace
When moving records in a workspace existing move-placeholders
need to be taken into account to get values for pid/sorting
correct.
Change-Id: I3507321fe092bb8e87cec3d4f4bf079983165788
Fixes: #31663
Releases: 4.5, 4.6, 4.7
Reviewed-on: http://review.typo3.org/6792
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
[BUGFIX] Respect move-placeholders when moving records in workspace
When moving records in a workspace existing move-placeholders
need to be taken into account to get values for pid/sorting
correct.
Change-Id: I8d12b0b3e7b7842be64bec0b649661c6a4a054c8
Fixes: #31663
Releases: 4.5, 4.6, 4.7
Reviewed-on: http://review.typo3.org/6794
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
History
#1 Updated by Tolleiv Nietsch over 3 years ago
- Status changed from New to Needs Feedback
It's quite hard to fix "random" behaviour - are you able to reproduce this misbehaviour within the Introduction Package? How?
#2 Updated by Daniela Petrosino over 3 years ago
- File screenshots.jpg added
I was able to reproduce the bug within the Introduction Package. Just create a workspace and try to move some pages as child under for example "Features". Then we moved "Features" and pressed the reload button.
What you see next is that some pages jumped back. This mostly happens with more than 3 child pages, but its pretty random.
We also looked in the mysql.log and the "UPDATE" query has the wrong pid.
#3 Updated by Daniela Petrosino over 3 years ago
I forgot we could reproduce the bug in typo3 4.5.7 and 4.6
#4 Updated by Franz Koch over 3 years ago
I'm currently also having issues on moving pages on the rootlevel of the website. It seems as if instead of the UID of the rootpage the UID of the page itself is stored as PID (thus recursive) and the page is gone then.
#5 Updated by Stefan Neufeind over 3 years ago
- Status changed from Needs Feedback to Accepted
#6 Updated by Mr. Hudson over 3 years ago
Patch set 1 of change I973899f6940ced60800814a5ffb9271ffd58c8e5 has been pushed to the review server.
It is available at http://review.typo3.org/6725
#7 Updated by Stefan Neufeind over 3 years ago
- Status changed from Accepted to Under Review
- Assigned To set to Stefan Neufeind
#8 Updated by Mr. Jenkins over 3 years ago
Patch set 2 of change I973899f6940ced60800814a5ffb9271ffd58c8e5 has been pushed to the review server.
It is available at http://review.typo3.org/6725
#9 Updated by Mr. Jenkins over 3 years ago
Patch set 3 of change I973899f6940ced60800814a5ffb9271ffd58c8e5 has been pushed to the review server.
It is available at http://review.typo3.org/6725
#10 Updated by Mr. Jenkins over 3 years ago
Patch set 1 of change I3507321fe092bb8e87cec3d4f4bf079983165788 has been pushed to the review server.
It is available at http://review.typo3.org/6792
#11 Updated by Mr. Jenkins over 3 years ago
Patch set 1 of change I8d12b0b3e7b7842be64bec0b649661c6a4a054c8 has been pushed to the review server.
It is available at http://review.typo3.org/6794
#12 Updated by Stefan Neufeind over 3 years ago
- Status changed from Under Review to Resolved
#13 Updated by Webadmin no-lastname-given over 3 years ago
Is this change not included in Typo3 4.5.8? I have just updated my installation and the problems are still there. The issue is also not listed in the changelog.
#14 Updated by Stefan Neufeind over 3 years ago
It is included in 4.5.8. Unfortunately the changelog wasn't updated to mention this (and various other) changes when packaging the new release.
Are you maybe hitting a corner-case which is not exactly what this bugfix here was about?
If you can, please try with a clean 4.5.8-installation (introduction-package maybe), try to reproduce your error and create a new issue on how to reproduce the problems you see. I promise to take a look a closer look at it then :-)
#15 Updated by Webadmin no-lastname-given over 3 years ago
Thank you for quick response. You're right. It seems that our test was to weak. See #32592.
#16 Updated by Michael Stucki over 1 year ago
- Category changed from Bugs to Workspaces
#17 Updated by Michael Stucki over 1 year ago
- Project changed from Workspaces & Versioning to Core
- Category changed from Workspaces to Workspaces