Answered Passing values into a snippet - A question mark value in parameter causes failure of IF filter

MODX version 2.3.3-pl
In a MODX template i am calling a chunk and inside that chunk i am using a conditional statement to check if it is the home page or resource 1, if so then lets show something. In this case the output should output some settings to the screen.
This seems to work fine until i add the &data=`a?`, now the 'a' can be any length of characters or whitespace with characters, once adding the '?' all code gets removed including the div with id of settings-wrapper.
if i remove all characters and just leave the '?' it works ok, I have changed the &data to &shawn=`a?` and got the same results. Also if i add any characters or whitespace after the '?' not having any thing in front of it there is no problem

Fails


Works


Works


Thanks
Shawn

Quote from: BobRay at May 22, 2015, 04:36 PM

A character followed by a question mark is tells the parser that arguments follow. If there is more than one such combo in a tag, the parser will get confused.

If _utility is your own snippet, you can use some other character or character combination where you want the question mark (e.g., QQ) and translate it in the snippet.

So I would expect this outside of the '`' (ticks), but inside of the ticks i could be passing a title like &data=`How was your day?`, and when i remove the conditional statement it works fine
Works


But add the conditional statement and it fails

The MODX parser is very complex and I don't pretend I can explain it fully, but your second example has both a conditional output modifier and a nested tag. Either one (or the combination) could be causing the trouble, but the solution I suggested should solve the problem in any case.

It will definitely be easier than re-writing the parser.

I just thought i would mention the issue, and yes im sure the parser is complex and there is probably a bit of black magic that goes on in there.
Thanks again Bob, for your quick responses and helpful advice.
Shawn

Good point. The trouble with parser issues, though, is that trying to fix them often causes other things to break.

I'm glad you got it sorted.

Quote from: markh at May 24, 2015, 09:20 AM

Just for kicks, have you tried this?

[[!*id:is=`1`:then=`
    <div id="settings-wrapper" style="min-height: 50px;">
    [[!_utility? &type=`settings` &data=`?`]]
    </div>
`]] 

If my understanding of the parser is any good, the problem you're seeing is due to the parsing order. _utility is uncached, causing it to be processed later, and the [[*id]] processing taking place first, which is where the parser gets confused with the extra backticks and the question mark..

Hi Mark, Thanks for the information, this worked.