Links point to sections for manaully deleting files in the /storage
directory (without database interaction) and deleting database entries (without
storage file interaction). These sections are marked as 'danger zone' because
they should be used carefully and only if the site's storage files and database
have become out-of-sync. with each other.
The back-end functionality has not been implemented yet.
This commit establishes the 'danger zone' in the site's settings page. This will
need to be added to over time. This commit set-ups the 're-populate search DB'
feature but the back-end is not yet implemented.
I was faffing in this file and had Emacs do a quick re-indentation (with
web-mode) enabled. I don't think I have touched this file since installing
web-mode.
This will need updating. I copied over a quick-list section from another
template. I'm off home after this commit (got one more commit to enter after
this). Thought I would get something in before I left, though.
Only 'Month' and 'Year' are used because 'Day' is not relevant -- at time of
writing. You might see an change to this form in a later commit if requirements change.
This commit makes the header (site's name and logo) a link which points back to
the site's "/" (I.E. Home page/route). It, also, centralises the header and the
navigation menu (in the header). This is so the header doesn't look weird when
viewed on a mobile phone.
I removed the <hr> at the bottom of the file because the site has enough styling
applied to it to make the <hr> look out of place now. I can clearly
denote/identify where the site's (front-end) header and footer stops and starts.
This page is populated in this commit but is broken because it requires several
JavaScript files which have not be committed to the repository as of yet. This
commit is in preparation of adding those files.
I've removed the 'extends' blocks and built a completely seperated template from
the rest of the website. The template was not rendering properly because certain
parts of the website had not been set-up yet so the complete isolated template
was/is required.
I've, also, added extra options for the user to set during this first run
process which will be processed by the back-end. I've not put much work into
adding validation checks because it is a one-time thing (this page). You'll need
access to the server anyway -- at this point -- so a bit of manual correction of
mistakes will be easy to achieve. Deleting the database will be enough to
trigger the first run process again.
This update seperates the form previous version of the template (for updating
the user's display name and password) into two. This is because of a change in
the back-end defroutes. It's makes it easier on the back-end to update the
password and display name seperately with different HTTP POST requests (and HTML
form data).
This is a multi-file commit because the code is essentially the
same. Each HTML template has either had a 'quicklist' section added or
had links added to it.
'Quicklist' is just a section with a collection of links to other
parts of the website based on the context of the page/user's current
location.
