TYPO3 Core

Code examples would have made the issue easier to understand. I assume the following:

[globalString = = ]

is false while

[globalVar = = ]

is true?

Or does the issue occur when the left value of the comparison evaluates to an empty string? Like this:

[globalString = GP:someNonExistentGetParameter = ]

Thorsten Kahler wrote:

Code examples would have made the issue easier to understand.

you are right :-)

I assume the following:

No

Or does the issue occur when the left value of the comparison evaluates to an empty string? Like this:

[...]

yep, meant this or e.g.

[globalString = GP:theValueOfThisParameterIsEmpty = ]

Fixed this for the moment via attached patch.

I ever used globalVar for this comparison, but now it's time to fix this, because globalVar isn't for string comparison, right?

Btw.: it works in globalVar because the equals is the only case in function compareNumber() where no doubleval() is called on the rightValue, what is inconsistent.

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/21979

Applied in changeset 06bf27df49a2ae3b1de49e64169139ac5c449681.

Patch set 1 for branch TYPO3_6-0 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/27250

Applied in changeset db90a2676cd96e34203713545d98be2c5a891a4a.