Bug #52104: Exception: No such workspace defined - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (3)

Georg Ringer
Nicole Cordes
Philipp Gampe

Actions

Copy link

Bug #52104

closed

Exception: No such workspace defined

Added by Ralle Büchnitz about 11 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Nicole Cordes

Category:

Target version:

6.2.0

Start date:

2013-09-18

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

6.0

PHP Version:

5.3

Tags:

Complexity:

easy

Is Regression:

Sprint Focus:

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)

Related issues 3 (1 open — 2 closed)

Related to TYPO3 Core - Bug #80901: Missing workspace causes exception when "Edit Live" flag is cleared in user settings

Closed

2017-04-20

Actions

Related to TYPO3 Core - Bug #97129: No such workspace defined after create a new user and assigning usergroups to users

New

2022-03-07

Actions

Has duplicate TYPO3 Core - Bug #34314: workspace_perms checkbox doesn't save state

Closed

2012-02-27

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Philipp Gampe about 11 years ago

Status changed from New to Needs Feedback

What did you do before the error occured? Did you update TYPO3 CMS?

Actions

Copy link

Updated by Ralle Büchnitz about 11 years ago

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.

Actions

Copy link

Updated by Thorsten Kahler about 11 years ago

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?

Actions

Copy link

Updated by Thorsten Kahler about 11 years ago

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.

Actions

Copy link

Updated by Philipp Gampe about 11 years ago

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.

Actions

Copy link

Updated by Nicole Cordes about 11 years ago

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.

Actions

Copy link