#22109Wrong Parsing of wraps when combining noTrimWrap and option Split
Description
when a wrap is parsed, first it is splittet by the string “|*|” to get the three parts.
Then the parts are splitted by “||” to get the “single wrap definitions”.
Thats generally fine, when not using the noTrimWrap-Function.
In the following Example (for better reading i use “.” instead of space, its still confusing enough):
noTrimWrap= ||.».||*||*|.|||
This should be working
Left option: ||.».| <—- valid noTrimWrap
Right option: ||| <—— valid noTrimWrap
but each option is splitted to subparts
left: “empty”,”» |“
right: “empty”,”|“
as single wraps passed to noTrimWrap
you need to pass the following wrapstring into Typoscript
noTrimWrap= |.|.».||*||*|.|.|.|
Whats wrong is, that you generate the subparts by simply splitting the options by “||”, that results in a wrong precedency. And the correct way of splitting is possible and defined. You can see, that the splitting the way it is done IS false, and makes no sence, since you always have three pipes for each single wrap
(issue imported from #M13516)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.