Bug #20793
closed
noTrimWrap = | || won't work inside a menu
Added by Christian Zenker about 15 years ago.
Updated almost 7 years ago.
Description
TYPO3 seems to recognize this pattern as an optionSplit inside a HMENU...
10 = HMENU
10 {
1 = TMENU
1 {
ATagParams.cObject = COA
ATagParams.cObject {
wrap = class="|"
10 = TEXT
10.value = menu
20 = TEXT
20 {
value = highlight
noTrimWrap = | ||
fieldRequired = ...
}
}
}
}
should also be present in lower versions of TYPO3:
compare:
http://www.typo3.net/index.php?id=13&action=list_post&tid=79003 [de]
(issue imported from #M11598)
- Category set to TypoScript
- Status changed from New to Accepted
- Target version deleted (
0)
- TYPO3 Version changed from 4.3 to 4.7
- PHP Version changed from 4.3 to 5.3
I can confirm this issue using the following setup:
temp.mainMenu.10 = HMENU
temp.mainMenu.10 {
entryLevel = 0
1 = GMENU
1.expAll = 1
1.wrap = <ul class="firstLevel">|</ul>
1.NO = 1
1.NO {
allWrap = <li>|</li>
XY = [10.w]+10,[10.h]+10
backColor = #ffffff
transparentColor = #ffffff
transparentBackground = 1
10 = TEXT
10 {
text.field = title
text.noTrimWrap = | -- | |
fontSize = 14px
fontFile = fileadmin/fonts/momstypewriter.ttf
fontColor = #535f5f
offset = 0,26
}
}
1.ACT < .1.NO
1.ACT {
allWrap = <li class="current">|</li>
}
}
- Assignee set to Jochen Rau
The issue is caused by the implementation of the optionSplit. Specifically by an explode pattern '||' used in t3lib_TStemplate::splitConfArray. This pattern can also occur in a noTrimWrap wit different semantics.
- Status changed from Accepted to Under Review
- Target version set to 4.7.0-beta2
- Status changed from Under Review to Accepted
- Assignee deleted (
Jochen Rau)
- Status changed from Accepted to Under Review
- Target version changed from 4.7.0-beta2 to 4.7.0-beta3
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Target version changed from 4.7.0-beta3 to 6.1.0
- Status changed from Resolved to Closed
Also available in: Atom
PDF