Tiki has various interfaces which override the standard interface (Bootstrap-based themes). As of 2019-08-26, there are various UIs because they were done by different people at different times. Next steps:
- Make a list of all interfaces
- Compare UIs
- Determine which ones (some or all) should be unified
- Determine if and how they should be themable
- Make it happen
- Tiki Installer Disabled: https://doc.tiki.org/tiki-install.php
(mentioned by Jonny)
- Site closed via tiki-error_simple.php: Site Access
- When Tiki is on a server without minimum PHP version. Ref: How to set minimum requirements in Tiki
- Content delivery network: when the CDN URL is improperly accessed, there is an error message.
- Site currently being updated (with a useful timer) "Maintenance in Progress"
- Tiki Manager Web not yet installed
In standalone mode: not really any theme
Within a configured Tiki: should take them of the Tiki
http://show.tiki.org (suggested by Jean-Marc)
At Tiki sites, for invalid URLs ending in .php (or .html, etc.), instead of a normal 404 error, this is displayed: "No route found. Please see http://dev.tiki.org/URL+Rewriting+Revamp". (Related bug reports: https://dev.tiki.org/item7039-Admin-page-not-found-error-is-too-geeky and https://dev.tiki.org/item5565-With-URL-rewriting-enabled-attempt-to-access-invalid-URL-yields-strange-techie-error-message-rather-than-usual-page-not-found.)
Also, an issue with page not found is a very broken page being returned. See https://dev.tiki.org/item3537--htaccess-issue#contenttabs_view_tracker_item-1
The server errors right now are not handled by Tiki, and hence have the default view of the server default, or sometimes on shared hosting the somewhat prettier messages they provide. It is a simple matter to take control over these, but of course, we need somewhere pretty to send users.
These currently unhelpful errors should probably be redirected to a 403 page.