#19809make pi_wrapInBaseClass wraps configurable
Description
Background:
Plugins often use pi_wrapInBaseClass function in tslib_pibase to wrap the content with a base class. The outcome HTML looks like:
… content …
This is widespread, because kickstarter ships this function as default.
Problem:
The wraps can be annoying if content is empty or in cases where plugin content is used for AJAX. Unfortunately the wraps are generally not configurable.
Solution:
The appended patch adds some conditions to tslib_pibase::wrapInBaseClass to give user some control (with the precedence that general configuration is overruled by special configuration) :
- no baseWrap container for any plugin if content is empty or new TS option config.disableBaseWrap is set
- custom baseWrap container if configured in TS setup of a certain extension (using stdWrap): plugin.tx_extensionname_pi1.baseWrap
(issue imported from #M10118)