Project

General

Profile

Actions

Bug #8743

closed

Autopublication scheduler task has too many rights

Added by Francois Suter over 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2010-07-08
Due date:
% Done:

0%

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

Description

From the related bug report (http://bugs.typo3.org/view.php?id=15048):

Inside the Scheduler task for autopublication of workspaces, the user rights are temporarily set to admin, but they are not lowered again (if needed). This was not really an issue when this piece of code was called by a CLI script. However now that it is a Scheduler task, the proper rights must be reset when the task is finished, otherwise any Scheduler that may follow will be executed with admin rights too.

The really clean solution would be not to need admin rights at all, but I couldn't figure out the proper rights set up for this. I managed to have a user with rights to the workspaces and rights to publish, but it could not publish from the Live workspace, only from the relevant workspace. The error messages were rather weird, complaining about the user not having rights to change permissions... I don't if this is a bug or if I just had a wrong setup.

Anyway I would be glad if you could take a look at RFC #15048 in the Core list and either vote for it or come up with a better solution.

Thanks.

Actions #1

Updated by Francois Suter over 14 years ago

REMINDER

The RFC is still pending in the Core list. I just updated it to reflect the recent structural changes of the source code (i.e. typo3/mod/user/ws moved to typo3/sysext/version/ws).

Actions #2

Updated by Francois Suter over 14 years ago

Having had no feedback I went ahead and committed RFC #15048 to trunk.

Note that the autopublication feature is not really complete yet, as it would need to be able to handle swap too, thus also respecting the "un-publication" date. In the current state I would recommend either hiding the "un-publication" date entirely or changing the CSH to indicate that it is currently not supported by the Core. Of course the best would be to make it work, but that's not on my agenda.

Actions #3

Updated by Steffen Ritter about 14 years ago

  • Status changed from New to Resolved

as Francois pointed out - already committed to trunk

Actions #4

Updated by Michael Stucki almost 11 years ago

  • Category set to Workspaces
Actions #5

Updated by Michael Stucki almost 11 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions #6

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF