Feature #17794
Updated by Mathias Schreiber over 9 years ago
A custom error handler has not enough infos to react corretly upon different error reasons. The only way is to parse the reason text which may change from one TYPO3 version to the next. Therefor it is necessary that the various $TSFE functions pass an error code to pageNotFoundAndExit() as parameter. eg 100 = The requested page does not exist! 101 = The requested page does not exist (type)! * 200 = Page is not available in the requested language. 201 = Page is not available in the requested language (strict). 202 = Page is not available in default language. 300 = Request parameters could not be validated (&cHash comparison failed) 301 = Request parameters could not be validated (&cHash empty) etc * for spacers (issue imported from #M6719)