Bug #35122
closed
Provide an upgrade script or at least a meaningful log message for the deprecated HTML TypoScript type
Added by Niels Pardon about 12 years ago.
Updated over 9 years ago.
Description
I've just discovered that the core team decided to drop the support for the HTML TypoScript type with version 4.8. I would have expected that the Install Tool offers some kind of upgrade functionality for existing TS templates currently using the HTML type.
Wouldn't have been too hard to replace all occurences of "= HTML" with "= TEXT" in TypoScript setup templates. Instead the depreciation log gets flooded with messages don't giving any hint.
If you decide to not add an upgrade wizard for version 4.6 then please add a meaningful depreciation log message instead of no message at all.
Thanks!
can you give an example how it does look currently?
IMO it is not possible to just replace all occurences as a cObj can created in external TS files, in PHP code, ... also I doubt that it is used very much.
The depreciation log entry looks like this:
2012-03-18 15:10: tslib_content_Html->render() - - require(typo3_src-4.6.6/typo3/sysext/cms/tslib/index_ts.php),typo3_src-4.6.6/index.php#78 // include(typo3_src-4.6.6/typo3/sysext/cms/tslib/pagegen.php),typo3_src-4.6.6/typo3/sysext/cms/tslib/index_ts.php#385 // TSpagegen::renderContent#74 // tslib_cObj->cObjGet#266 // tslib_cObj->cObjGetSingle#548 // tslib_content_User->render#601 // tslib_cObj->callUserFunction#55 // call_user_func_array#6380 // tx_templavoila_pi1->main_page# // tx_templavoila_pi1->renderElement#196 // tx_templavoila_pi1->processDataValues#331 // tslib_cObj->cObjGetSingle#609 // tslib_content_Html->render#601 // t3lib_div::logDeprecatedFunction#45 (typo3_src-4.6.6/typo3/sysext/cms/tslib/content/class.tslib_content_html.php#44)
You can only understand the reason for the log entry if you have deep knowledge of the TYPO3 core and know that tslib_content_Html is the class representing the HTML TypoScript type. I didn't know it till I digged in deeper. I first thought it was TemplaVoila related.
How much work would it be to create something similar to a search in the TS Object Browser to at least detect most usages. I know we'd miss the ones introduced when certain conditions are met, but it would at least catch the majority.
- Status changed from New to Closed
- Is Regression set to No
thanks for trying to improve the quality of TYPO3. as this is already quite a while ago, a upgrade wizard won't be added anymore.
since development of CMS 7 and the new release cycle, every breaking change is documented far better by using a separate documentation file for every issue.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by