Instruct users to contact admin, not WF developers on 500 page #772
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Misconfigured or broken servers have directed people to the wrong place in the past. This fixes that with a simpler 500 error page directing visitors to a Contact page.
This also adds the ability to customize an instance-wide Contact (
/contact) page. It provides some boilerplate text that admins might use to describe who runs the instance -- but unlike other dynamic pages, it won't publicly show up until the admin has personally customized the page.Action required: all admins of multi-user instances should go to
https://YOUR-INSTANCE/admin/page/contactand explain the best way for users and visitors to contact them.Fixes #684