Bug #89387
closed
Tasks backend:lock & backend:unlock most not be schdulable
100%
Description
The tasks backend:lock and backend:unlock must not be allowed to be triggered via backend. this doesn't make any sense.
triggered it by accident (As it is the 1st task) and locked myself and full backend and of course couldn't get back via backend.
Updated by Gerrit Code Review over 4 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61938
Updated by Gerrit Code Review over 4 years ago
Patch set 1 for branch 9.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61925
Updated by Georg Ringer over 4 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 26c9a8e32637d506249989318941c923171b7658.
Updated by Benjamin Franzke over 4 years ago
- Related to Bug #89873: backend:lock/backend:unlock are not longer available as scheduler tasks added
Updated by Benjamin Franzke over 4 years ago
- Status changed from Resolved to Accepted
The schedulers primary task is to schedule tasks, not to execute them from the backend.
The backend-execution is an additional functionality, because it's sometime handy for manual tasks/testing.
- Planned Maintenance locks:
schedule a backend lock for a planned update or migration where you agreed to stop editing as of a certain date. - Regular edit-locks, e.g.:
schedule a backend lock for let's say every friday as of 8pm
schedule backend unlock on mondays at 8am.
Therefore let's revert this patch. Patch is here:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/62551
Updated by Georg Ringer about 4 years ago
- Status changed from Accepted to Closed