Bug #32962
closed
Cannot enable live workspace in user account
0%
Description
When trying to enable permissions on the live workspace for a user, this change is not saved.
Even updating a user which has this permission, removes the permission.
The log shows "Record 'foobar' (be_users:123) was updated. (Online). Changes in fields: usergroup,workspace_perms. (msg#1.2.10)"
but this is not reflected in the databases and the box will be unticked in the form after saving.
There is no error message to the user.
I don't know if this is related but I sometimes see the error messages
Core: Error handler (BE): PHP Warning: Invalid argument supplied for foreach() in /var/www/typo3/typo3_src-4.6.2/typo3/sysext/workspaces/Classes/Service/Workspaces.php line 409
Core: Error handler (BE): PHP Warning: array_diff(): Argument #2 is not an array in /var/www/typo3/typo3_src-4.6.2/typo3/sysext/workspaces/Classes/Service/Workspaces.php line 402
Core: Error handler (BE): PHP Warning: array_keys() expects parameter 1 to be array, null given in /var/www/typo3/typo3_src-4.6.2/typo3/sysext/workspaces/Classes/Service/Workspaces.php line 402
in the logs.
I have two draft workspaces only one of which I currently use. My database compare shows no errors
and a mysqlrepair on all tables did not fix this.
Updated by Tolleiv Nietsch almost 13 years ago
- Status changed from New to Needs Feedback
Are you able to reproduce this in more than one installtion and maybe also within the introduction-package?
Updated by Michael Stucki almost 11 years ago
- Category changed from Bugs to Workspaces
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Updated by Alexander Opitz over 10 years ago
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?
Updated by Alexander Opitz about 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.