Actions
Feature #44218
closed
Custom Error Renderers
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2012-12-25
Due date:
% Done:
0%
Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
This is a backport from FLOW 1.1, described and resolved in http://forge.typo3.org/issues/39423
This one needs to be taken into account, too: http://forge.typo3.org/issues/42135
Very nice Feature, but we lack the manpower right now to solve it for 6.1. Feel free to work on this, anyway.
Updated by Alexander Schnitzler about 11 years ago
- Target version set to Extbase 6.2
Updated by Alexander Schnitzler almost 11 years ago
- Status changed from New to On Hold
Updated by Anja Leichsenring almost 11 years ago
- Target version changed from Extbase 6.2 to Extbase 6.3
Updated by Alexander Opitz over 9 years ago
- Project changed from 534 to TYPO3 Core
- Category changed from Extbase to Extbase
- Target version changed from Extbase 6.3 to 7.0
Updated by Anja Leichsenring over 9 years ago
- Status changed from On Hold to New
Updated by Mathias Schreiber over 9 years ago
- Target version changed from 7.0 to 7.1 (Cleanup)
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 8 years ago
- Status changed from New to Rejected
- Target version deleted (
8 LTS)
won't be added for the core, as long as there is no need to add it to the core (except for the "Flow has that as well" reason). I think it's better to close it than to mark it "on hold" as long as nobody is actively willing to put manpower into extbase at all.
Actions