Bug #52104
closed
Exception: No such workspace defined
Added by Ralle Büchnitz almost 11 years ago.
Updated almost 7 years ago.
Description
My backend is broken due to the following error after logging in into Backend with non-admin user:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: No such workspace defined | InvalidArgumentException thrown in file /html/typo3/typo3_src-6.0.10/typo3/sysext/workspaces/Classes/Service/WorkspaceService.php in line 102. Requested URL: http://www.somethin.org/typo3/backend.php
The $title is FALSE and so the exception is thrown.
The $wsId is INT (-99)
- Status changed from New to Needs Feedback
What did you do before the error occured? Did you update TYPO3 CMS?
There was an Update from 6.0.5 to 6.0.10 before.
BUT I didn't used that minor login for a longer time. So I can't say whether this is related to the update.
Additional data:
- I dont really use the workspaces
- Workspace Installtation happened earlier through the upgrade wizard in install tool
- I created a new non-admin-user and this one works fine
If you want to know more about it tell me. Anyway, i'm going to use the new user and you can close this ticket if you like.
- Assignee set to Ralle Büchnitz
The mentioned "non-admin user" is lacking access to any workspace. See comment in classs BackendUserAuthentication
:
// User workspace. -99 is ERROR (none available), -1 is offline, 0 is online, >0 is custom workspaces.
public $workspace = -99;
Please check workspace permissions for that user. Can the issue be fixed by giving the user access to any workspace?
- TYPO3 Version changed from 6.1 to 6.0
Ralle Büchnitz wrote:
There was an Update from 6.0.5 to 6.0.10 before.
I change the TYPO3 version according to reporter comment.
- Status changed from Needs Feedback to Accepted
- Assignee deleted (
Ralle Büchnitz)
- Target version set to 6.2.0
- Complexity set to easy
Relic of the old draft workspace. The checkboxes in the backend user records fill a bitmask. If you have a user who does not have access to the life workspace, the value will be 2 while it should be 0. To change that, you cannot simple check/uncheck the checkbox, but you have to check all checkboxes at least twice (and uncheck in between) to change the value to 0 (no live) and then to 1 (live).
We need a migration wizard here that adapts the bitmasks of all backend users.
- Category deleted (
Workspaces)
- Assignee set to Nicole Cordes
The problem is a wrong calculation of workspace permission bit mask. After any change to the user record is it stored with a wrong value in the database. This was triggered because the second item (Draft workspace) was removed in the mean time.
- 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 Under Review
- Status changed from Under Review to Resolved
- Related to Bug #80901: Missing workspace causes exception when "Edit Live" flag is cleared in user settings added
- Status changed from Resolved to Closed
- Related to Bug #97129: No such workspace defined after create a new user and assigning usergroups to users added
Also available in: Atom
PDF