TYPO3 Core

I just had another look in to that issue and see two possibilities to fix it:

- change the CSS in a way that it allows content like the SQL debug output to be shown
- change the TYPO3 Core in a way that the SQL debug stuff is returned within the div#typo3-docbody.

I did a patch that change debug in this way:

- t3lib_div::debug doesn't echo but collect debug info in $GLOBALS['debugOut']
- template.php fills marker ###DEBUG### with $GLOBALS['debugOut']
- possibility to supress all debugs with $GLOBALS['noDebug'] = 1
- placed ###DEBUG### in all BE-templates behind ###CONTENT###

- placed $GLOBALS['debugOut'] in FE after admin panel

I applied the patch to my TYPO3 Core and tried again. But I get the same problem again. Please see the attached screenshot of the problem.

i think i found a very easy solution, please test it in your browsers

See last patch and screenshot, where i did a debug and implemented a line producing php warning.

http://support.typo3.org/index.php?id=17&tx_nntpreader_pi1[nid]=2&tx_nntpreader_pi1[mid]=340465&cHash=81605dc4b4

@Steffen looks simple!

@Ingo does it work for you on Mac/Safari?

didn't test

ok, but Francois did, so it works on FF /IE7/IE6 and Safari (Mac)

I will make a RFC and glad to have this issue fixed.

This patch removes the scrollbar for long records. See attached image ( sql_error_patch.png)

yeah, that was the reason why i gave up for the moment

The attached patch fixes the issue by introducing a debug console based upon ExtJs and the currently introduced TYPO3 Viewport.

Committed to trunk, rev 7486