Project

General

Profile

Actions
Copy link

Feature #17794

closed

add an error code to pageNotFoundAndExit

Added by Martin Kutschker about 17 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
9.4
Start date:
2007-11-15
Due date:
% Done:

100%

Estimated time:
PHP Version:
5.5
Tags:
Complexity:
Sprint Focus:

Description

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)

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #58728: Regression: unaccessible protected section with shortcut in rootlineClosed2014-05-12

Actions
Actions
Copy link

Also available in: Atom PDF