[TYPO3-core] RFC: #12614: Debug output destroys BE HTML

Steffen Kamper info at sk-typo3.de
Tue Nov 17 12:46:21 CET 2009


Hi Ivan,

Ivan Kartolo schrieb:
> I created a new backend module with kickstarter (the old one, not mvc
> and not extbase). You put the renderFlashMessages in two places:
> 1. class.t3lib_pagerenderer.php (render function)
> 2. template.php (startPage function)
> 
> for extension, which is created by the old kickstarter, at the time
> these functions are called, the flashMessages are empty.
> 
> These two functions are called in the main function of the BE-module
> index.php. After that then the moduleContent (here are the most debug
> function being called). After that printContent function is being called
> and the $this->doc->endPage().
> 
> the only place to put renderFlashMessages is in the endPage function of
> template.php. It means all debug output will be put at the end of a
> module (not at the top).
> 

i will recheck this.
The idea was that pagerenderer do that at the very end. You're right, 
the problem is that this should be at the end so all content is 
available and all debug calls are already called.
Now old modules call render function of pageRenderer twice (Header and 
Footer) and both calls are in startPage.

Maybe it's much easier to have both available: debug with echo (old 
style) and debug with flashmessages. Old would be default, and 
flasmessages would be activated in bodymodules, so only mods with 
docheader would use the flashmessages.

vg Steffen


More information about the TYPO3-team-core mailing list