Feature #51990
closed
Allow overriding pageNotFound_handling by TypoScript
Added by Stefan Neufeind about 11 years ago.
Updated over 9 years ago.
Description
Currently pageNotFound_handling (and similar values?) can only be set through LocalConfiguration. For a more complex setup it would be great to be able to override it by TypoScript. Since the page can't be found :-) maybe the root-page for that matching domain could be used. It would be nice if normal conditions (for language-handling, ...) could be used to easily make a decision on how to proceed.
are you really sure you wanna do that? in many cases there is just something broken and it is quite possible that the TYPO3 error page is broken as well?
This is a good idea, because it would clearly simplify the way for integrators to set up error pages for different domains, languages etc.
The only problem: Afaik we dont have a TypoScript configuration ready at the point where a »page not found« error is shown (the page id is determined (or not, then an error occurs), then the cache is called, then a TypoScript configuration array is loaded).
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
The classic doens't cut it?
Redirect to /404/, but a page with the title 404 in the tree?
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Mathias Schreiber)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by