This package enables editable 404 pages. It allows you to configure several 404 pages in the page tree, in case you need different content or styling in different situations.

ATTENTION: This package will add a http-component via Settings.yaml. This component will try to find a matching 404 page for the current path an override the http-request accordingly.

• 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 add "sitegeist/movealong" : "~1.0" to the require section of the composer.json or run composer require sitegeist/movealong. We use semantic-versioning so every breaking change will increase the major-version number.

To activate Sitegeist.MoveAlong, the smallest configuration you're going to need is the following:

Sitegeist:
  MoveAlong:
    enable: TRUE

By default, Sitegeist.MoveAlong will match any requestPath and map it to /404. You can configure your own rules to handle Dimensions for example:

Sitegeist:
  MoveAlong:
    rules:
      english:
        pattern: 'en\/.*'
        target: 'en/404'
      german:
        pattern: 'de\/.*'
        target: 'de/404'

The rule pattern and targets support pattern matching and replacement:

Sitegeist:
  MoveAlong:
    rules:
      main:
        pattern: '^(en|de)\/.*'
        target: '$1/404'

!!! Regardles of any existing defaultUriSuffix configuration, you need to omit that uri part. So, if your 404 page is reachable via 404.html, you need to configure 404 as your target.

If you just want to override the default behavior, you can overwrite the pre-configured all rule:

Sitegeist:
  MoveAlong:
    rules:
      all:
        target: 'NotFound' # will display NotFound.html

If you want to change the order in which the rules apply, you can add a position argument to your rule configuration:

Sitegeist:
  MoveAlong:
    rules:
      english:
        ...
      german:
        position: 'before english'
        ...

If you want to return a 410-gone status for an obsolete section you can configure this:

Sitegeist:
  MoveAlong:
    rules:
      fileadmin:
        position: 'before all'
        pattern: '^fileadmin.*'
        target: '410'
      all:
        ...

Since the fallback mechanism will cause Neos to think, that a node has been found, the system won't respond with a 404 status code anymore. Therefore, some TypoScript configuration is applied, to determine, whether we are on an error page and then send a 404 status code accordingly.

By default, that TypoScript will assume, that your error page will have a uriPathSegment property that is set to 404 or 410.

If this is not the case for your configuration, you can simply apply a different rule for that by overriding the Sitegeist.MoveAlong:Match404Page or the Sitegeist.MoveAlong:Match410Page prototype :

prototype(Sitegeist.MoveAlong:Match404Page) {
  [email protected] = ${value && q(node).property('is404Page') == true}
}

see LICENSE file