Bug #20793: noTrimWrap = | || won't work inside a menu - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (1)

Jochen Rau

Actions

Copy link

Bug #20793

closed

noTrimWrap = | || won't work inside a menu

Added by Christian Zenker over 15 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

TypoScript

Target version:

6.1.0

Start date:

2009-07-29

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

4.7

PHP Version:

5.3

Tags:

Complexity:

Is Regression:

Sprint Focus:

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)

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #67669: noTrimWrap not working with optionSplit

Closed

2015-06-22

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Jochen Rau almost 13 years ago

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>
  }
}

Actions

Copy link

Updated by Jochen Rau almost 13 years ago

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.

Actions

Copy link