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.

Common problems¶

No static files are generated¶

There must be a root page with at least one domain in the root line of every error page

Somehow a static file is missing¶

When updating a page (e.g. page#1) a cache file for the configured error group is created. If there’s another error page (e.g. page#2) for the same error group and with the same parent page its static file gets overwritten. When the error group of page#1 is changed, the cache for page#2 does not get recreated. This results in a missing cache entry.

As a solution you can run the scheduler task that rebuilds the whole cache.

I use nested domains¶

Nested domains are not supported by the extension and may lead to unexpected behaviour when generating paths of the static files.

When using the Crawler extension an error page is shown in backend.¶

Actually that’s not a problem with ext:form4_errordocs but ext:crawler or TYPO3 itself.

Because the crawler creates speaking URLs with ext:realurl sometimes the TYPO3 page-not-found-handling kicks in and triggers an error page if $GLOBALS['TYPO3_CONF_VARS']['FE']['pageNotFound_handling'] is set. That’s the setting ext:form4_errordocs uses to register its page-not-found-handler.