{"type":"rich","version":"1.0","provider_name":"phorkie","provider_url":"https:\/\/p.cweiske.de\/","title":"TYPO3v11: Deprecation: ContentObjectRenderer::parseFunc without any configuration","author_name":"Christian Weiske","cache_age":86400,"width":900,"height":900,"html":"<!-- embedding all files of https:\/\/p.cweiske.de\/900 -->\n<link rel=\"stylesheet\" href=\"https:\/\/p.cweiske.de\/css\/embed.css\"\/>\n<div class=\"phork\" id=\"900\">\n    <div class=\"phork-file\">\n <div class=\"phork-content\">\n  \n<div class=\"document\">\n\n\n<p>Upgrading from TYPO3 v10 to v11 brings following deprecation error:<\/p>\n<blockquote>\nTYPO3 Deprecation Notice:\nInvoking ContentObjectRenderer::parseFunc without any configuration will trigger an exception in TYPO3 v12.0\nin \/var\/www\/typo3\/public\/typo3\/sysext\/frontend\/Classes\/ContentObject\/ContentObjectRenderer.php line 3443<\/blockquote>\n<p>We used <tt class=\"docutils literal\">&lt;f:format.html&gt;<\/tt> in the backend preview sections of flux content elements - those triggered this notice.<\/p>\n<p>Solution is to use <tt class=\"docutils literal\">&lt;f:transform.html&gt;<\/tt>, which works in the backend.<\/p>\n<p><a class=\"reference external\" href=\"https:\/\/docs.typo3.org\/c\/typo3\/cms-core\/main\/en-us\/Changelog\/11.5\/Feature-95176-IntroduceFtransformhtmlView-helper.html\">https:\/\/docs.typo3.org\/c\/typo3\/cms-core\/main\/en-us\/Changelog\/11.5\/Feature-95176-IntroduceFtransformhtmlView-helper.html<\/a><\/p>\n<\/div>\n\n <\/div>\n <div class=\"phork-meta\">\n  <a href=\"https:\/\/p.cweiske.de\/900\/rev-raw\/e99b99fe6d98e0f6b532605a636c5282416c7745\/README.rst\" style=\"float: right\">view raw source<\/a>\n  <a href=\"https:\/\/p.cweiske.de\/900#README.rst\">README.rst<\/a>\n <\/div>\n<\/div>\n<\/div>\n"}