[TYPO3-dev] output ends up in white page

Dmitry Dulepov [typo3] dmitry at typo3.org
Fri Sep 12 13:40:17 CEST 2008


Hi!

Steffen Kamper wrote:
> Further we could enhance the error handling. This was discussed in some 
> threads. May be with displayErrors=0 the errors could be fetched and the 
> standard TYPO3-errorbox cold tell that there occured a php error so the 
> page could not be displayed, enable displayErrors to see more details.

"If you get engine error, unscrew four nuts on the engine top. Next pull out four cylinders...". No one would want this in the car manual. "Consult your dealer" is the right thing in this case.

Another error message of the same inappropriate technical style presented to the user:
http://tamba2.org.uk/pix/2007/awindowserror.png

* * *

I think these block screen situations are rare. May be some kind of error message should be shown. But I am definitely against anything technical (like "enable displayErrors"). People should ask their support company for help. And company should be educated enough to know what to do.

-- 
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extension-development/book
In the blog: http://typo3bloke.net/pages/book-reviews/presentation-zen-by-garr-reynolds/




More information about the TYPO3-dev mailing list