Bug #16790
closed
Only white page on backend
0%
Description
After installing some extension with the EM the backend color turned into white and only one text is displayed:
,1 /* cached */); ?>1-1'); ?>
Nothing works any more.
I have found out the reason:
tt_products/ext_localconf.php:
t3lib_extMgm::addPItoST43($_EXTKEY,'pi1/class.tx_ttproducts_pi1.php','_pi1','list_type',1 /* cached */);
This line causes problems to the EM. Maybe because a comment is passed as together with a parameter 1 to the function. I think so because it contains the same text which is also displayed in the install tool.
The error disappears after copying tt_products again and deletion of the temp_CACHED_* files in typo3conf. This should however not only be corrected in tt_products.
(issue imported from #M4659)
Files
Updated by Michael Stucki almost 18 years ago
How come you found a fix in version 4.0.4?
Updated by Michael Stucki almost 18 years ago
Anyway, please fix this on your own or change that line in the extension. Obviously the PHP codeline is parsed wrong.
Updated by Franz Holzinger almost 18 years ago
A similar bug now in TYPO3 4.0.2:
Message displayed in Frontend:
$value]; } } // NO extension of class - does not make sense here. ?>
Warning: Cannot modify header information - headers already sent by (output started at /typo3_src-4.0.2/typo3/sysext/cms/tslib/class.tslib_pibase.php:1400) in /typo3_src-4.0.2/typo3/sysext/cms/tslib/class.tslib_fe.php on line 2830
This comes from the end of class.tslib_pibase.php:
// NO extension of class - does not make sense here.
Updated by Franz Holzinger almost 18 years ago
All the backend display shows only: TYPO3 4.1beta3
Somehow one extension has output a '>'. After an update it has worked.
The extension has been called from config_default.php. The HTML output got invalid by this and therefore only a '>' on the screen.
How can it be avoided that a bug in an extension causes the backend to disappear completely?
There should be a TYPO3 echo function which must always be used instead of the PHP echo.
Updated by David Bruchmann over 17 years ago
Hy Franz,
the Echo-function as you proposed is a nice idea but perhaps no solution for all possible faults.
Another Idea - perhaps that's not realizable or also no allround solution - is a parser for sourcecode of extensions. Something like that would be a big project needing a lot of work, but perhaps in future it could be used to review extensins in general in a first step. Some variation of my idea must exist already i.e. inside rte.
Best Regards
David
Updated by Franz Holzinger over 17 years ago
I have now detected the reason which has caused the change inside of PHP files. I write it down here to make it complete.
Some files have been modified during the filetransfer with GFTP under KDE.
Thanks to David's proposal. Maybe an extesnion should be written which compares changes in the system and gives infos. Esp. core files like localconf.php should be restored if problems occur.
Updated by Oliver Hader over 17 years ago
Thus, this report isn't a bug at all and we can close it?
Please open new feature requests for the "restore localconf.php" and "parse/validate structure" to have things separated.
Updated by Franz Holzinger over 17 years ago
Please don't close it. Others might have a similar error with a FTP client. This won't be searchable any more if closed.
Updated by Michael Stucki over 17 years ago
It's not a bug, so it should not remain in here.