We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 7231
    • 4,205 Posts
    I tested it in a TV, chunk, chunk in a TV, page cached and page uncached and all are working here. Just curious, are you using 0.9.6.1? I am testing in 0.9.6.1. I read that there were some bugs fixed regarding the parse order with some snippets, this could be the problem.
      [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

      Something is happening here, but you don't know what it is.
      Do you, Mr. Jones? - [bob dylan]
      • 27302
      • 154 Posts
      I haven’t upgraded to 9.6.1 just yet. I’ll give that a try though.
        • 27302
        • 154 Posts
        Okay, just upgraded to Modx 9.6.1, and the problem still exists.
          • 27302
          • 154 Posts
          I’ve tried a few more snippets using [!......!] instead of [[........]]

          I cannot get any of them, including Wayfinder to work if I use [!

          Each and every time it just displays the snippet call as if it was part of the page text. This would explain why Ultimate Parent wasn’t working with [!...!] and just displayed the root level.

          I cannot understand why my version of ModX won’t understand [!...!]
            • 25663 MODX Staff
            • 12,272 Posts
            Did you copy the snippet call from an online demo? Are you using an RTE?

            If so, I suspect when you turn off rich text mode you’ll find that the snippet call actually looks like this in the code:
            [<!-- -->[snippet?param=`foo`[<!-- -->]
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 27302
              • 154 Posts

              Are you using an RTE?

              No, I’m editing it from within the chunks editor in plain html.
                • 27302
                • 154 Posts
                I just tried a [!...!] command in the ModX Minimal Template that comes with the CMS. The call worked perfectly. So it must be something to do with my template that is causing the problem.

                The trouble is I haven’t got a clue what it could possibly be!
                  • 10449
                  • 956 Posts
                  Well, among other things, the HTML validator isn’t happy with the MIME type. Some clash between the doctype and content-type...
                  http://validator.w3.org/check?verbose=1&uri=http://domain.com
                  (it’s under "tools", if you have the Firefox web-developer toolbar -> "validate HTML")
                    • 27302
                    • 154 Posts
                    Okay thanks, I’ll check that out.

                    But in another twist, I put the revised Ditto call right slap bang in the raw template, and it now works!

                    The only trouble is that I need it to work from within the TV/Chunk call, which currently it is refusing to do.
                      • 27302
                      • 154 Posts
                      I think I’m going to admit defeat. Now that I’ve got the call working on the raw template I might as well use a different template for each of those document levels.