Bug #71580
closed
Switch-User feature uses wrong user id for logging
Added by Remo H. over 8 years ago.
Updated over 6 years ago.
Category:
Backend User Interface
Description
Situation: One workspace with a usergroup assigned as editors. Admin is owner. Workspace is freezed for editing.
If the admin saves a content element a flash message is shown that workspace has been frozen (1: [newlog()] All editing in this workspace has been frozen!).
If the editor saves a content element no flash message is shown at all.
There must be a message for all content editors shown that the workspace is frozen. Otherwise content editors are confused.
In TYPO3 6.2 it's not an issue, only in 7 LTS.
- Status changed from New to Accepted
- Priority changed from Must have to Should have
Confirmed. It would be even better, if modification elements are not shown at all and the frozen status is visualized always...
Reason is issue #17643 which uses the original user to log the notification.
This happens only if a user is simulated, not if the user is logged in correctly.
- Subject changed from Missing notification when saving content in frozen workspace. to Switch-User feature uses wrong user id for logging
- Category changed from Workspaces to Backend User Interface
- Is Regression changed from No to Yes
The mentioned issue that introduced this misbehavior is partly wrong.
All actions of a simulated user are executed with the permissions of that user.
Using the initial (admin) uid is wrong in that regard and also introduces a regression in the quick-edit mode (PageLayoutController::renderQuickEdit for resolving the NEWid).
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by