[TYPO3-core] RFC #14231: csc static template "v4.3" won't include the registered plugins
Ernesto Baschny [cron IT]
ernst at cron-it.de
Wed Apr 28 08:34:38 CEST 2010
Hi,
This is an SVN patch request.
Type: bugfix (major)
Bugtracker references:
http://bugs.typo3.org/view.php?id=14231
Branches:
trunk
Problem:
If you upgrade from 4.3 and choose the css_styled_content static
template "v4.3/", no frontend plugin from extensions will be rendered in
the frontend.
Switching to another css_styled_content template will make the rendering
appear.
Additional info:
FE-plugins are registered through t3lib_extMgm::addPItoST43() which
includes typoscript code right after the "content (default)" or
"css_styled_content". This is currently hardcoded in
t3lib_extmgm::addTypoScript().
When we added the v4.3 static template, we forgot to update the array or
content rendering templates.
Solution:
Move the hardcoded array away from the core and provide a registry of
renderingTemplates which css_styled_content then uses (including the new
v4.3 template). By doing that we automatically provide a way for other
extensions to register themselves as "content rendering templates" (so
also solving "long term feature request" #3930, see my last comment of
2006).
How to reproduce:
Include the template "CSS styled content TYPO3 v4.3" in your main
TypoScript. See the frontend: no plugin is rendered. Switch to any other
"CSS styled content" template: plugins are rendered again.
Install the patch. Frontend plugins rendered in all cases.
Cheers,
Ernesto
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 14231.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100428/a3cbd62f/attachment.txt>
More information about the TYPO3-team-core
mailing list