Bug #18734
closed
SQL debug output is not shown in the Backend
0%
Description
I have SQL debug output enabled in the Install Tool which works really good. But after upgrade from 4.1.6 to 4.2.0, there is a problem with the debug output: It's shown "behind" other stuff from the BE. Through this, the debug output is not readable (one just sees the red borders - but not the contents of the message as it's hidden behind the other stuff from the BE).
As the error message is completely available when I look at the HTML source, I think this is just a CSS issue.
(issue imported from #M8305)
Files
Updated by Mario Rimann almost 16 years ago
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.
Updated by Steffen Kamper almost 16 years ago
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
Updated by Mario Rimann almost 16 years ago
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.
Updated by Steffen Kamper almost 16 years ago
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.
Updated by 
Updated by 
Updated by Steffen Kamper almost 16 years ago
@Ingo does it work for you on Mac/Safari?
Updated by Steffen Kamper almost 16 years ago
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.
Updated by Rob Vonk over 15 years ago
This patch removes the scrollbar for long records. See attached image ( sql_error_patch.png)
Updated by Steffen Kamper over 15 years ago
yeah, that was the reason why i gave up for the moment
Updated by Stefan Galinski almost 14 years ago
The attached patch fixes the issue by introducing a debug console based upon ExtJs and the currently introduced TYPO3 Viewport.