TYPO3 Core

Fixed target version, always set target to final release, use "Fixed in Version" for specific preview releases...

Code is already in the debug exception handler, but this is still the FLOW3 link. Should we add this link to 4.5 still, considering that it will be there for 3 years?

And if yes, should we use the same redirect as FLOW3 / v5? There shouldn't be a "clash" of unix timestamps in our exceptions. :)

Yes, as the error numbers are pretty unique, I woud use the same redirect.

If we get something other than a wiki, the redirect should just be changed, thus I see no problem in having valid links for >3 years. Do you?

Do you agree with also adding this to the ProductionExceptionHandler?

I would maybe separate the landing-page which is hardcoded in the core to different from the FLOW3 one, else we won't be able to separate the requests at a later point. FLOW3 might want to redirect to "its own wiki" or some other resource while in v4 we want to keep it in wiki.

About the ProductionExceptionHandler, we might add another redirect to be able to differenciate the requests also:

I imagine something like this:

http://typo3.org/go/exception/xxx => FLOW3, already in use
http://typo3.org/go/exception/v4/xxx => v4 productionHandler
http://typo3.org/go/exception/v4/debug/xxx => v4 debugHandler

I will discuss in the release meeting to see if this is ok or not.

Thanks, Steffen!

I agree in having some differentiation. We don't know, what might change...
However having different targets for debug and production mode? I fear nobody will ever create exception descriptions, which differentiate between editor and developer.

Basically IMHO the ProductionExceptionHandler is not for production. I would not display weird (for them) error messages, but only show a "sorry.. sth. went wrong" page.

I think the only reason, why technical output is made also in production mode is that (almost?) nobody sets devIPmask.

• Production: Only show that an error occured (current design without technical error message)
• BackendUser: the Procution state: Error message with technical details
• Debug: current DebugExceptionHandler for developers with stack trace

As long as this is only a vision, I would go adding the way the link to the error handler (which btw. I plan to do the next days).

About the linking: differenciating it from start on allows us to later handle them differently. As soon this is released, it is "too late" to change again. :)

The target of both v4 links will be the same for the start. Maybe later we decide to put less technical info in the "production handler".

The production handler is meant to be for "anonymous users", i.e. the public. Other known mechanisms to trigger the debugHandler are enough. If the production handler is too technical, we should make that less technical.

The error / exception handling is documented here: http://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.3.0/view/8/2/

Review: http://review.typo3.org/1282