Feature #20167
closed
Integrate nice looking message and integrate resend when backend was locked for maintenance
Added by Oliver Hader about 15 years ago.
Updated almost 9 years ago.
Description
The backend can be locked down for maintenance by placing the file ./typo3conf/LOCK_BACKEND. The first 60 seconds are critical since the AJAX updater won't get the information about the lock in that time window. Imagine an editor wants to save the modified data and runs into the stop message...
The feature request is to beautify the message (currently it's just a PHP die() call) and to integrate a possibility to resend the submitted POST data. Maybe an periodical updater using AJAX can be integrated here as well. It notifies the user when the backend is unlocked again.
(issue imported from #M10669)
I think the die() call is fixed with #23464
Is this feature really so frequently used that we need the resending? Feel free to close or keep this entry open.
- Status changed from Needs Feedback to New
- Complexity set to easy
Steffen Gebert wrote:
Is this feature really so frequently used that we need the resending? Feel free to close or keep this entry open.
Don't close this issue, it's still valid (except for the die() call maybe).
Just like with the backend news there should be an easy way to create that file from the backend and then have a process start notifying all users to stop working, save drafts and so on (with a deadline maybe). After that deadline the admin should get notified that the editors are out and that it is now safe to start with whatever he had in mind when locking the backend.
- Target version deleted (
4.6.0-beta1)
Ingo Renner wrote:
Don't close this issue, it's still valid (except for the die() call maybe).
Just like with the backend news there should be an easy way to create that file from the backend and then have a process start notifying all users to stop working, save drafts and so on (with a deadline maybe). After that deadline the admin should get notified that the editors are out and that it is now safe to start with whatever he had in mind when locking the backend.
I don't think this belongs to the category of easy bugs with those requirements (alltough it would be nice to see this implemented).
- Complexity changed from easy to hard
Ack, definitely not so easy. But would be very nice..
- Assignee deleted (
Steffen Gebert)
- Status changed from New to Needs Feedback
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by