netlogix / errorhandler
Package info
github.com/netlogix/Netlogix.ErrorHandler
Type:neos-package
pkg:composer/netlogix/errorhandler
Requires
- php: ^8.0
- ext-curl: *
- guzzlehttp/guzzle: ^7.9
- neos/flow: ^9.0
- neos/neos: ^9.0
- symfony/yaml: ^5.4 || ^6.0 || ^7.0
Requires (Dev)
None
Suggests
- netlogix/cli-increasedatabasetimeout: Increase database timeout errorpage:generate command
- netlogix/sentry: Log exceptions to sentry
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-11-03 12:18:09 UTC
README
This package allows you to generate static error pages by using the content of Neos pages. These static files will be used for error handling in Flow & Neos depending on their configuration.
You can also use these files as ErrorDocument in your webserver.
Install package
composer require netlogix/errorhandler
Configuration
Option 1: Add error pages manually as document nodes.
Create a custom document node, which uses the
Netlogix.ErrorHandler.NodeTypes:Mixin.ErrorPage mixin.
Every child page of this error page as well as child pages of siblings of this error age are covered by this error page.
Every error counts for its exact dimension and for the error codes configured within that page node.
A dynamic error page is omitted, if no error code is assigned.
There still needs to be a storage folder where cached error pages will be placed.
Netlogix: ErrorHandler: # File path where this error page should be saved to. Available variables are `site`, `dimensions` and `node`. destination: '${"/var/www/default/" + site + "/" + dimensions + "/" + node + ".html"}'
Generate error pages
To generate the static error pages, run the following Flow command:
./flow errorpage:generate --verbose
This will loop all error pages and download them to their destination. Depending on how often the content of the configured Neos pages changes, you might want to do this during deployment or periodically using a cronjob.
Show current configuration
./flow errorpage:showconfiguration
This call responds in YAML format, although not all settings are actually given in YAML settings. Instead, the result will be the merged result of both, YAML configuration and node based configuration.