Feature #20167

Integrate nice looking message and integrate resend when backend was locked for maintenance

Added by Oliver Hader over 10 years ago. Updated over 4 years ago.

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

0%

PHP Version:
5.2
Tags:
Complexity:
hard
Sprint Focus:

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)


Related issues

Related to TYPO3 Core - Bug #20180: The Message "The backend is locked" is not translatable Closed 2009-03-14
Related to TYPO3 Core - Bug #20935: Use typo3printError() if backend is locked Closed 2009-08-27
Related to TYPO3 Core - Feature #23464: Enable customization for fatal error messages in the backend and frontend Closed 2010-08-27

History

#1 Updated by Steffen Gebert about 9 years ago

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.

#2 Updated by Tolleiv Nietsch about 8 years ago

  • Status changed from Needs Feedback to New
  • Complexity set to easy

#3 Updated by Ingo Renner about 8 years ago

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.

#4 Updated by Xavier Perseguers about 8 years ago

  • Target version deleted (4.6.0-beta1)

#5 Updated by Mario Rimann about 8 years ago

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).

#6 Updated by Steffen Gebert about 8 years ago

  • Complexity changed from easy to hard

Ack, definitely not so easy. But would be very nice..

#7 Updated by Steffen Gebert about 8 years ago

  • Assignee deleted (Steffen Gebert)

#8 Updated by Mathias Schreiber almost 5 years ago

  • Status changed from New to Needs Feedback

Is this still valid?

#9 Updated by Alexander Opitz over 4 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.

Also available in: Atom PDF