Project

General

Profile

Actions

Bug #25265

closed

Error after upgrading workspaces to 4.5 : Reviewer is not able to do his review-job anymore

Added by Markus Kappe over 13 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-03-07
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The review stage is bypassed or the reviewer has not the required rights to send an entry to the next stage (depending on your configuration)

This happens when you already had your workspaces configured prior to TYPO3 4.5 and do an core update.

Reason is that the field "reviewers" in the table sys_workspace is not used any more by the "workspace" extension, but it still exists in the database (after the upgrade) AND is used by t3lib_userauthgroup::checkWorkspace()

In the class t3lib_userauthgroup the function workspaceCheckStageForCurrent() checks if the current user is in the "responsible_persons" and has the "_ACCESS" "member" or "owner" (on a custom stage). But the function checkWorkspace() in the same class reports, that the user has "_ACCESS" "reviewer" which is not used anymore - because the data keeps in the database after upgrading to version 4.5

Workaround: delete the data in the column "reviewers" in the table "sys_workspace"

--sql
update sys_workspace set reviewers = ''

Maybe the script that does the creation of the table "sys_workspace_stage" on upgrading TYPO3 should also clean the "reviewers" column.
(issue imported from #M17877)

Actions #1

Updated by Alexander Opitz over 10 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.3)?

Actions #2

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.

Actions

Also available in: Atom PDF