Bug #69310
closed
Attempt to reset workspace failed
Added by Albrecht Köhnlein over 8 years ago. Updated over 3 years ago.
100%
Description
When publishing a workspace, I often see this message:
[newlog()] Attempt to reset workspace for record failed because you do not have edit access
There's no information about table and record uid. So I cannot give more information at the moment.
Files
| Bildschirmfoto 2015-08-24 um 12.14.53.png (13.9 KB) Bildschirmfoto 2015-08-24 um 12.14.53.png | Albrecht Köhnlein, 2015-08-25 14:27 | ||
| log.png (126 KB) log.png | Albrecht Köhnlein, 2015-11-13 08:59 |
Updated by Albrecht Köhnlein over 8 years ago
Sorry, it's not when "publishing" a workspace, but when a workspace is deleted.
(Is there any way for me to edit the text above?)
Updated by Oliver Hader over 8 years ago
- Status changed from New to Needs Feedback
What kind of content are you dealing with? Structured, 1:n, m:n, flexforms?
I think "deleting" in this regard means "discarding", right? Did you discard single elements or the the whole workspace?
Updated by Albrecht Köhnlein over 8 years ago
The errors occured, when the record from "sys_workspace" was deleted. See log.png
And I cannot tell, which kind of content/relation lead to the problem. The log does not give any information about the table name. And I didn't see the errors by myself, but was told by an editor.
Updated by Alexander Opitz about 8 years ago
- Status changed from Needs Feedback to New
- Assignee set to Oliver Hader
Updated by Christian Kuhn over 3 years ago
- Related to Bug #91881: Massive load when deleting sys_workspace record on pid 0 added
Updated by Christian Kuhn over 3 years ago
- Related to Bug #61719: Warnings on flushing whole workspace with localizations added
Updated by Christian Kuhn over 3 years ago
Tried to reproduce this one.
Note we're talking about deleting a sys_workspace record from pid 0 here. This should delete all records in all tables assigned to the workspace.
I ran into the error message "Attempt to reset workspace for record failed: No record" that is raised before quite a lot and fixed that with #61719. The patch also improves the error message to be more useful.
Additionally, #91881 is much more severe and needs immediate fix first. The patch comes with some functional tests to verify workspace records of the to-delete sys_workspace are actually deleted.
For the issue itself (raising error "Attempt to reset workspace for record failed because you do not have edit access"), I'm unable to reproduce directly. Deleting a sys_workspace record requires admin access rights anyway since it is on pid 0, so some access rights problem is unlikely since that is correctly handled in DataHandler.
I suggest to change the error message to contain the table and id it is handling as a patch for this issue. This will simplify debugging so we can handle a fresh issue with clean how-to-reproduce, in case the issue itself persists.
Updated by Gerrit Code Review over 3 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65135
Updated by Gerrit Code Review over 3 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65135
Updated by Gerrit Code Review over 3 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65135
Updated by Christian Kuhn over 3 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 417e5a5634ae5717dbca4c1adc70430e97297420.
Updated by Gerrit Code Review over 3 years ago
- Status changed from Resolved to Under Review
Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65105
Updated by Christian Kuhn over 3 years ago
- Status changed from Under Review to Resolved
Applied in changeset 599603e61b3638dde0d92928312fb372aa8a9a37.
Updated by 
