Bug #94510
closedSiteConfig with a config for a not available extension breaks errorHandling e. g. 404 page
0%
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: slug
Updated by Riccardo De Contardi over 3 years ago
- Category set to Site Handling, Site Sets & Routing
Updated by Benni Mack about 3 years ago
- Status changed from New to Needs Feedback
Hi Christian,
thanks for your feedback. I guess you get a SQL error, because the DB table "tt_address" does not exist? Can you share some more information?
Updated by Benni Mack about 3 years ago
- Related to Bug #94585: Siteconfig - 404 error not triggered if routeEnhancers is configured added
Updated by Christian Kuhn almost 3 years ago
- Status changed from Needs Feedback to Closed
hey. i'm going to close this due to lack of feedback for now and hope this is ok. please share more information on this in case the issue is still relevant.