DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
Documentation¶
Custom error 404 pages made simple.
Use TYPO3 pages for display 404 errors. Optional error 403 redirect handling. Works for multi domain and multilingual installations.
How it works¶
This extension adds a new custom page type for rendering 404 documents.
This extensions overrides the ['FE']['pageNotFound_handling'] configuration with its own configuration.
Integration¶
Simply install the extension and create a new page with your error message.
- No TypoScript setup to include.
You can use following markers in your content.
| Marker | Description |
|---|---|
| ###CURRENT_URL### | The url of the called page. |
| ###REASON### | A text why the error occured. |
| ###ERROR_STATUS_CODE### | 404|403 |
If you like redirect non logged in users when a 403 (forbidden) error occurs, simply include the available "Page TSConfig" or define by yourself:
tx_error404page.redirectError403To = auto | [url] | [uid]
Configuration¶
Extension configuration¶
| Key | Description |
|---|---|
| doktypeError404page | If required, you can change the page type. |
| enableErrorLog | Enables the error log and statistic backend modul. |
| excludeErrorLogPattern | Regex without delimiters (/ /) and modifiers (i). Example: select|union |
| basicAuthentication | Username and password for basic authentication. |
| debug | Enable debug log. |
Warning
If you change the page type, you must update the doktype of your previously created error pages by yourself.
Log and statistic¶
If log is enabled, the last 10'000 errors are logged and listed in the backend module "Errors".
FAQ¶
- How it works?
- The error handler makes a request to fetch the error page and returns it.
- Instead of the error page, the home page is shown?
- Perhaps you have some htaccess rules that redirects the error handler's request. Make sure it is possible to call your error page directly (ex. http://typo3.request.host/index.php?id=123&type=0&L=0&tx_error404page_request=ab12cd34de56).
- How to redirect 403 (Forbidden) errors to a login page?
- Please read the section "Integration".
Contributing¶
Changelog¶
| 3.0.0: | Support for TYPO3 8.6, dropped support for TYPO3 6.2 |
|---|---|
| 2.1.1: | Bugfix for language detection with realurl 1.x.x |
| 2.1.0: | Added exclude pattern for error log |
| 2.0.0: | Refactoring, Feature 403 redirects |
| 1.3.0: | Updated backend modul |
| 1.2.0: | TYPO3 6.2 compatibility |
| 1.1.0: | Feature error log |
| 1.0.0: | First release |