TYPO3 Core

We should have something for all errors and outputs etc. there, not just the ones done by PHP.

I've seen this now, too

removed from 4.2 as it's no blocker and will happen most likely during development only anyways

I think it's a blocker, as you can't work with the backend (no Icons). Is it to late to provide a patch?

using cc_debug works.

Attached patch corrects CSS for TYPO3 Backend, so that edit icons are always on top. Screenshot also attached. Patch will be posted to core list in a few minutes

Hi Ingo,

i don't think this is a good solution. Output looks crap also.

We need a proper solution for this, maybe integrating cc_debug.

Output looks crap, but it's working. As Ingo mentioned, it will happen most likely during development only anyways. So this is a better solution than none solution !

This is still a usability problem for setups with enabled php warnings in productive environments, see #18980 for some more user feedback.

Any chance to find an acceptable solution?

I think it's no problem to disable displaying php errors (or at least lowering the error-level - only errors but no warnings) and enabling a php-error-log (file).

This may be suggested in the TYPO3-setup so the non admins know that there is something...

solved with #18734