Function pi_wrapInBaseClass in tslib/class.tslib_pibase.php
This function produces div-tags around html-output of certain extensions (newloginbox).
Generated comments can be disabled via TS config.disablePrefixComment = 1 but the div-tags will allway produced.
It would be nice if this feature (div-tag-generation around plugin-code) could be disabled vi TS. So that we have more control over the generated html and more flexibility.
The problem was already discussed at firstname.lastname@example.org (17.01. / 11:04 Code-Änderungen im CORE...)
Greeting und thank a lot Thomas
(issue imported from #M4801)
#1 Updated by Oliver Hader almost 14 years ago
I agree to the statement, that such wraps should be set in typoscript and there should be default setting for it. The wrap you mentioned is mostly used for CSS reasons, to give it a CSS-namespace.
But, there could be an extension-dependent configuration like this one:
disableWrapInBaseClass = 1
If the php extension file itself (e.g. pi1/class.tx_myext_pi1.php) puts the $conf to $this->conf in the main-function, pi_wrapInBaseClass could get knowledge of this configuration.
#6 Updated by Steffen Kamper over 13 years ago
yes, i think too, because some extensions come with default css defined with the wrapclass, otherwise this css will not work any longer.
So the easies way would be a setting for extension, that prevent the wrapping like
plugin.tx_ext_pi1.disableWrapInBaseClass = 1
and in pi_wrapInBaseClass
$content = $this->conf['disableWrapInBaseClass '] ? $str : '<div class....