[TYPO3-core] RFC: #10118: Make pi_wrapInBaseClass wraps configurable

[Steffen Müller]

Hi.

I have rewritten the patch and cleaned up the whole function.

The functionality is now:

-  If nothing is set, we have the div tag as before (backward compatible)

- If pi_wrapInBaseClass is set in the TypoScript setup of a plugin, it 
is used as wrap/stdWrap. Examples:

plugin.tx_t3cpodcasts_pi1 {
   pi_wrapInBaseClass = <div class="PODCAST">|</div>
}

plugin.tx_t3cpodcasts_pi1 {
   pi_wrapInBaseClass.dataWrap = <div class="PODCAST-{field:pid}">|</div>
}

- If config.disable_pi_wrapInBaseClass = 1 is set, the wrap is disabled 
for all plugins (plugin setup is ignored).

- If config.disable_pi_wrapInBaseClass = ifEmpty is set, the wrap is 
disabled only for plugins with no content.


Although this looks rather complex, it gives admins good control. It 
also resolves the request of #10102 (no wrap if content is empty). And 
it's backward compatible.


-- 
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Microblog:  http://twitter.com/t3node

-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug_10118_v3.diff
Type: text/x-diff
Size: 2926 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100116/769c733b/attachment.diff>