frankmullenger/underconstruction

SilverStripe Under Construction Page Module

SilverStripe Under Construction Page Module

Maintainer Contacts

• Frank Mullenger (frankmullenger_AT_gmail(dot)com) My Blog

Requirements

• SilverStripe 3.0

Documentation

This is essentially just a much, much better version of the holding page module and achieves practically the same thing. This module will create a static HTML error page in the assets folder when it is installed. Then when a non admin user tries to visit the website the error page will be displayed. Once an admin user has logged in they will be able to browse the website at will., _(*1)

Additionally, when the under construction page is displayed it responds to the browser with a 503 - Service Unavailable HTTP status code., _(*2)

This module could easily be changed to generate any kind of maintenance page and return any kind of HTTP status code., _(*3)

I have updated the module so that under construction pages can be turned on or off via the SiteConfig->Access tab for convenience., _(*4)

Installation Instructions

1. Place this directory in the root of your SilverStripe installation and call it 'underconstruction'.
2. Visit yoursite.com/dev/build to rebuild the database and create the under construction page.
3. Check that the under construction page was created by looking for an error-503.html page in the /assets folder.
4. If you want to update the error page at any time (because your page template has changed perhaps), just delete the error-503.html page in the /assets folder and run /dev/build again to regenerate it.
5. If your site is in dev mode then the under construction page will not be shown.
6. You will need to go to the SiteConfig->Access tab and tick the checkbox to 'Display an under construction page?'.

You can find this module on Packagist., _(*5)

Usage Overview

1. Install the module using instructions above.
2. When you no longer want to display the under construction page you can either remove this module (by removing the 'underconstruction' directory) or uncheck the relevant checkbox in SiteConfig->Access tab.