Actions
Bug #48572
closedThe page unavailable handler does not get the exception number which would be thrown without it
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-05-27
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:
Description
To identify a problem it would be genius to allow error identification by a unique number :D
Therefore i suggest to add the issue information to the unavailable and page not found handlers:
Snipped from TypoScriptFrontendController :: getConfigArray if ($this->checkPageUnavailableHandler()) { $this->pageUnavailableAndExit($message); } else { $explanation = 'This means that there is no TypoScript object of type PAGE with typeNum=' . $this->type . ' configured.'; \TYPO3\CMS\Core\Utility\GeneralUtility::sysLog($message, 'cms', \TYPO3\CMS\Core\Utility\GeneralUtility::SYSLOG_SEVERITY_ERROR); throw new \TYPO3\CMS\Core\Error\Http\ServiceUnavailableException($message . ' ' . $explanation, 1294587217); }
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.1 (Cleanup)
- Is Regression set to No
Updated by Benni Mack over 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Gerrit Code Review almost 9 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46060
Updated by Mathias Schreiber over 8 years ago
- Status changed from Under Review to Resolved
The code looks like in this issue.
No idea what should be missing.
Actions