DEPRECTAED The solution was added to the Neos Core in version 4.3 see https://neos.readthedocs.io/en/stable/Appendixes/ReleaseNotes/430.html?highlight=error#native-404-error-rendering-that-can-be-controlled-via-fusion
Render 4xx status pages via fusion
The status codes that are handled via fusion error-rendering can be controlled via settings.
Neos:
Flow:
error:
exceptionHandler:
renderingGroups:
notFoundExceptions:
matchingStatusCodes: [ 403, 404, 410 ]The fusion code that actually renders the error-message.
#
# Main error matcher
#
error = Neos.Fusion:Case {
#
# Find the document to render in case of 404
#
@context.notFoundDocument = ${q(site).children('[instanceof Neos.Neos:Document]').filter('[uriPathSegment="404"]').get(0)}
#
# Custom matcher for 404 status
#
4xx {
@position = 'start'
condition = ${statusCode >= 400 && statusCode < 500 && notFoundDocument}
renderer = Neos.Fusion:Renderer {
@context.node = ${notFoundDocument}
@context.documentNode = ${notFoundDocument}
renderPath = '/root'
}
}
#
# Default rendering of classic error-message
#
default {
@position = 'end 9999'
condition = true
renderer = Sitegeist.MoveAlong:ErrorMessage
}
}
- Wilhelm Behncke - [email protected]
- Martin Ficzel - [email protected]
The development and the public-releases of this package is generously sponsored by our employer http:https://www.sitegeist.de.
Sitegeist.MoveAlong is available via packagist. Just run composer require sitegeist/movealong. We use semantic-versioning so every breaking change will increase the major-version number.
see LICENSE file