Feature #44218

TYPO3.Flow - Feature #39423: Custom Error Renderers

Custom Error Renderers

Added by Anja Leichsenring almost 9 years ago. Updated over 5 years ago.

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.


Related issues

Related to TYPO3.Flow - Feature #42135: Include technical details to exceptions in dev contextResolvedBastian Waidelich2012-10-18

Actions
#1

Updated by Alexander Schnitzler over 8 years ago

  • Target version set to Extbase 6.2
#2

Updated by Alexander Schnitzler over 8 years ago

  • Status changed from New to On Hold
#3

Updated by Anja Leichsenring over 8 years ago

  • Target version changed from Extbase 6.2 to Extbase 6.3
#4

Updated by Alexander Opitz about 7 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
#5

Updated by Anja Leichsenring about 7 years ago

  • Status changed from On Hold to New
#6

Updated by Mathias Schreiber almost 7 years ago

  • Target version changed from 7.0 to 7.1 (Cleanup)
#7

Updated by Benni Mack over 6 years ago

  • Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
#8

Updated by Susanne Moog about 6 years ago

  • Target version changed from 7.4 (Backend) to 7.5
#9

Updated by Benni Mack about 6 years ago

  • Target version changed from 7.5 to 8 LTS
#10

Updated by Benni Mack over 5 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.

Also available in: Atom PDF