Bug #15988
closedconditions problem
0%
Description
in this construction typo3 see only last directive
[compasion1][comparsion2]....[comparsionN]
....
[end]
so it works same as
[comparsionN]
.....
[end]
(issue imported from #M3137)
Updated by Dmitry Pikhno over 18 years ago
please take a look. seems there is problem with multilevel conditions.
Updated by Michael Stucki over 18 years ago
Hi Wolfgang, can you please have a look at this?
- michael
Updated by Michael Stucki over 18 years ago
Dmitry, we probably need some more feedback from you:
What are the conditions you have tried? How can you prove it does not work?
- michael
Updated by Dmitry Pikhno over 18 years ago
page.10.marks.CONTENT =TEXT
page.10.marks.CONTENT.value = hello world!
[globalVar = TSFE:id > 80][globalVar = TSFE:type = 80][globalVar = TSFE:id =3]
page.10.marks.CONTENT =
[end]
i am on page with id = 3 and type=1. what should i see according to this code?
seems "hello world!"
but i see nothing.
if i made
[globalVar = TSFE:id =3]
page.10.marks.CONTENT =
[end]
it is works ok. i see nothing
also i tried treeLevel, PIDinRootline rules in multilevel comparsion. same result
Updated by Wolfgang Klinger over 18 years ago
No, simply
[condition1] [condition2]
equals
[condition1] OR [condition2]
and not
[condition1] AND [condition2]
so it's correct that you see nothing because
[globalVar = TSFE:id =3]matches
Updated by Michael Stucki over 18 years ago
Ah! I assume this is a misunderstanding then!
The default operation is "OR" not "AND".
Please try this instead:
[globalVar = TSFE:id > 80]&&[globalVar = TSFE:type = 80]&&[globalVar = TSFE:id =3]
Updated by Dmitry Pikhno over 18 years ago
crap. sorry guys. it is misunderstanding
Updated by Dmitry Pikhno over 18 years ago
please add this to the reference (tsref).
Updated by Michael Stucki over 18 years ago
Will be written in TSref, of course!
BTW, the default operation is OR because this was already working in past-4.0 versions.