#94510SiteConfig with a config for a not available extension breaks errorHandling e. g. 404 page
Description
If you have a siteconfig.yaml with e.g. a configuration for tt_address, BUT tt_address is not present in the TYPO3 system / tt_address is not installed and then try to call a non-existing page in the FE (e.g. “domain.tld/not_existing_page” you get the error message that the table tt_address does not exist.
This would be fine with “Debug”-Enabled and even desirable – but with Production/Live you should get the 404-page instead of the error message.
errorHandling:
-
errorCode: '404'
errorHandler: Page
errorContentSource: 't3://page?uid=30'
routeEnhancers:
AddressPlugin:
type: Extbase
extension: TtAddress
plugin: ListView
routes:
- routePath: '/{address_slug}'
_controller: 'Address::show'
_arguments:
address_slug: address
aspects:
address_slug:
type: PersistedAliasMapper
tableName: tt_address
routeFieldName: slugReviews 0
No change resolves or names this issue in its commit message, and no comment links one.