Project

General

Profile

Actions

Bug #93153

open

No such workspace defined after assigning usergroups to users

Added by David Menzel over 3 years ago. Updated 2 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2020-12-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
be user, workspace
Complexity:
Is Regression:
Sprint Focus:

Description

I got a bug which I had in TYPO3 7, 8 and now in 9 again. Not sure if it is already fixed in 10.

A BE user has some be usergroups assigned. I added one group to that user and as an admin I wanted to test that user. I then changed into that user role in the backend and I got the following error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1476045469: No such workspace defined | InvalidArgumentException thrown in file /var/www/typo3/public/typo3/sysext/workspaces/Classes/Service/WorkspaceService.php in line 124. Requested URL: https://my.domain.de/typo3/index.php?route=%2Fmain&token=--AnonymizedToken--&referrer-refresh=1608632069

The group I added had the following access rights:

Erlaubte Ausschlussfelder
sys_file_metadata:caption
sys_file_metadata:latitude
sys_file_metadata:duration
sys_file_metadata:download_name
sys_file_metadata:unit
sys_file_metadata:creator
sys_file_metadata:creator_tool
sys_file_metadata:content_creation_date
sys_file_metadata:color_space
sys_file_metadata:publisher
sys_file_metadata:categories
sys_file_metadata:location_country
sys_file_metadata:content_modification_date
sys_file_metadata:longitude
sys_file_metadata:note
sys_file_metadata:source
sys_file_metadata:ranking
sys_file_metadata:location_region
sys_file_metadata:keywords
sys_file_metadata:pages
sys_file_metadata:visible
sys_file_metadata:language
sys_file_metadata:location_city
sys_file_metadata:status
sys_file_metadata:title
sys_file_metadata:copyright
sys_file_metadata:fe_groups

Module
file_FilelistList

The result: the BE didn't work anymore

I fixed it with going to the be_user table and changed the value in 'workspace_id" from -99 to 0. After that I needed to restart the browser in order to be able to login again. As said, that I had this bug in earlier TYPO3 versions and it happend when assigning usergroups to users. Something must be wrong with the usergroups but I don't know why such an error can appear and break the BE...

Actions

Also available in: Atom PDF