You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are providing the RowWrap and ColumnWrap ViewHelpers to render additional grid system's html around each content element.
An integrator who wants to use this extension has to update the page rendering and the content element rendering by injecting these view helpers.
The integrator may also use them wrong and e.g. put additional html code between the row and the column which might break the grid system.
If the column wrap view helper was used several times inside one content element it might also break the grid system. Even worse: it breaks the html but the user doesn't notice because the browser corrects it.
For an out of the box solution I'd suggest to use the stdWrap.postUserFunc option in the content element rendering definition/configuration.
The FLUIDTEMPLATE content object has a stdWrap property.
For fluid_styled_content based rendering the function has to be added under lib.contentElement.stdWrap.postUserFunc.
This function would then handle the row and column rendering. It is called for each content element.
Please note, that the content element is already rendered before the row and column html are wrapped around it. If the content element needs to have the column context, a DataProcessor should be used.
We are providing the
RowWrap
andColumnWrap
ViewHelpers to render additional grid system's html around each content element.An integrator who wants to use this extension has to update the page rendering and the content element rendering by injecting these view helpers.
The integrator may also use them wrong and e.g. put additional html code between the row and the column which might break the grid system.
If the column wrap view helper was used several times inside one content element it might also break the grid system. Even worse: it breaks the html but the user doesn't notice because the browser corrects it.
For an out of the box solution I'd suggest to use the
stdWrap.postUserFunc
option in the content element rendering definition/configuration.The
FLUIDTEMPLATE
content object has astdWrap
property.For
fluid_styled_content
based rendering the function has to be added underlib.contentElement.stdWrap.postUserFunc
.This function would then handle the row and column rendering. It is called for each content element.
Please note, that the content element is already rendered before the row and column html are wrapped around it. If the content element needs to have the column context, a DataProcessor should be used.
What do you think @codemonkey1988 ?
The text was updated successfully, but these errors were encountered: