Details

    • Sub-task
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      The admin can configure a maintenance date and time in the configuration.

      After log-in in the editor this date and time is communicated to the user. How many hours before the point in time of the update this communication starts can be configured as well. The message should be different / special as the other info messages.

      In addition the admin can configure, how many minutes before the point in time of the update the application is locked for new log-ins.

      Also he can configure in the config-array, when in the time span before the update warning messages should be shown to users, that are logged in (e. g. 2 hours before, 1 hour before, 15 min, 10 min, 5 min, 1 min before).

      When the point in time of the update is reached, all normal HTML requests should deliver then a maintenance HTML page (customizable - plain file from client-specific). All requests (also AJAX) should get a HTTP 503 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.4 http://yoast.com/http-503-site-maintenance-seo/). This Ajax-status-code produces a corresponding error message in the application. The result page of ajax can also be the maintenance HTML page.

      If the application receives a 503 ajax answer, the user is informed, that maintenance is in progress, and that he will be redirected to the maintenance page.

      The maintenance page sends refreshing requests to the server every 30 seconds to ask, if the update is still in progress - and inform the user, when it is finished.

      The base concept will be implemented in ZfExtended-library and will work for all modules that build on it, special GUI features are translate5 specific.

      The maintenance-mode is also automatically activated when starting the translate5 updater.

      Attachments

        Activity

          People

            aleksandar Aleksandar Mitrev
            marcmittag Marc Mittag [Administrator]
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: