Download the PHP package silverstripe/errorpage without Composer
On this page you can find all versions of the php package silverstripe/errorpage. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package errorpage
Silverstripe ErrorPage Module
Overview
Provides an ErrorPage page type for the Silverstripe CMS, allowing CMS authors to set custom content for error page responses by error code. Error page responses are fully themed.
Installation
Limitations
The functionally in this module was separated out from the Silverstripe CMS module and retains some existing issues. An issue of note is that static error pages are generated but are rarely served up, and rarely re-generated. This can lead to website visitors seeing a stale or broken page in the event of a 500 server error. Contributions are welcome, please open a pull request if you want to add a feature or fix a problem.
Documentation
To Do
Theming
To apply a custom template for the error page you will need to create a ErrorPage.ss file in either templates/SilverStripe/ErrorPage/ErrorPage.ss or templates/SilverStripe/ErrorPage/Layout/ErrorPage.ss
Detailed error messages
If you're using $this->httpError($code, $message) in your codebase and want to include the message that is passed into that method, you can add the $ResponseErrorMessage to your ErrorPage template. Use caution when including this information, as these messages are often intended for developers rather than end-users.
For example, one of your controllers may throw a 401 status code for some specific reason. Very broadly, a 401 means the request is Unauthorised; if your controller throws a 401, it can add also add a specific reason:
These messages are appended to the ErrorPage template automatically when the site is in dev mode. You can disable this using the Config API. Setting this to false will also remove the $ResponseErrorMessage variable from your template.
Limiting options in the CMS
By default, all available error codes are present in the dropdown in the CMS. This can be overwhelming and there are a few (looking at you, 418) that can
be confusing. To that end, you can limit the codes in the dropdown with the config value allowed_error_codes like so:
Reporting Issues
Please create an issue for any bugs you've found, or features you're missing.
All versions of errorpage with dependencies
silverstripe/framework Version ^5
silverstripe/cms Version ^5
silverstripe/vendor-plugin Version ^2