We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Question mark (?) in output filter breaks parser

    • 33968
    • 863 Posts
    Lucas Reply #1, 14 years ago
    I have something like this in a chunk:
    [[+placeholder:!empty=`
    <p>Question mark breaks the filter: ?</p>
`]]

This text is also not displayed!


    When the question mark is present in the !empty=`` content, it somehow breaks the parser and in fact the entire chunk is not displayed.

    Can anyone else reproduce before I file a bug report?
      • 37523
      • 141 Posts
      Glyn Reply #2, 14 years ago
      Have you tried using a html entity such as the below instead of the question mark:

      & #63;

      remove the space between the & and #. The forum will not let me post the full code as it reinterprets it.

      A full list of entity can be found on this page
      http://www.w3schools.com/tags/ref_ascii.asp [ed. note: glynszasz last edited this post 14 years ago.]
        Glyn Szasz
        Sydney, Australia

        Happy to help (when can) and happy to learn

        If you are a Sydney based MODX developer would love to hear from you. Please contact me.
        • 33968
        • 863 Posts
        Lucas Reply #3, 14 years ago
        Yep, it's the '?' character that's breaking it. Presumably because it's part of the MODX tag syntax, but can't be sure.

        But I'm not looking for a workaround, I want to verify it as a bug. Output filters generally work on content input by users, who can't be expected to always enter the correct html entity.