[TYPO3-dev] Problem with debugging

Steffen Kamper steffen at sk-typo3.de
Thu Nov 22 13:08:18 CET 2007


"Malte Jansen" <mail at maltejansen.de> schrieb im Newsbeitrag 
news:mailman.1.1195732759.16400.typo3-dev at lists.netfielders.de...
> Dmitry Dulepov [typo3] schrieb:
>> Hi!
>>
>> Malte Jansen wrote:
>>> since there is no frame I the output of echo or print_r() is writing 
>>> behind the layer in a tceform. So it's very difficult to get it.
>>>
>>> Is there somewhere a function were the echo/print_r can be redirct or 
>>> something simular.
>>>
>>> For the tceform on the getMainFields
>>> this works fine:
>>>         ob_start();
>>>         echo '<div>';
>>>         print_r($data);
>>>         echo '</div>';
>>>         $temp = ob_get_contents();
>>>         ob_end_clean();
>>>         return $temp.$output;
>>>
>>> but it does not work at every place...
>>>
>>> Any suggestion?
>>
>> cc_debug + t3lib_div::debug(). This will open new window with nucely 
>> formatted debug information.
>>
>
> The problem is that,
>
> div#typo3-docbody {
> position:absolute;  <-- should be relative ?
> top:49px;           <-- should be removed ?
> z-index:2;
> }
> div#typo3-docheader {
> top:0pt;
> z-index:5;
> }
>
> So this part is moving. If the doc body starts at a absolute value There 
> could be other problem

this is a sideeffect from the new BE - problem is that you can't make the 
div in front of the iframe.
a solution could be to get debug in var and print it at the end instead of 
the beginning.

vg  Steffen 






More information about the TYPO3-dev mailing list