We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27261
    • 10 Posts
    Hey everyone,

    I have been strugling with the WebSignUp snippet for the past three or so hours and am totally out of ideas. undecided I have created a new document called "Registration" and unchecked the "rich container" option. My call to the WebSignup snippet is "[[WebSignup? &groups=`Member` &useCaptcha=`1`]]".

    When I load the page in my browser after logging out of the control panel the default template for the snippet loads just as it should. However, after filling in all of the various forms and clicking submit, they all clear to default and nothing else happens. No email is sent, no user is created.

    I can however manually add a user in the control panel and modx will dispatch an email with the password.

    Is there something I am missing? Has anyone experienced this behavior? Most importantly is there a solution?

    Thanks in advance,
    - Peter H.
      • 7231
      • 4,205 Posts
      NOt sure if this helps but I would chack and make sure that the document where the WebSignup snippet is on is not Cacheable.
        [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]
        • 27261
        • 10 Posts
        My hero. grin It magically works with the cache disabled! Seems like something like this should be mentioned in the documentation... undecided

        Thanks for the help,
        - Peter H.
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          Actually it is mentioned frequently that if your page is cached, your snippet must be called uncached in the form [!WebSignup? ... !]. This is true of any interactive snippets, or snippets that will fetch dynamic content, such as forms or feed readers.

          If the page with the snippet output is cached, the page is served next time without processing the snippet, which means there’s nobody listening to the POST from the form.

          Calling the snippet uncached means that even if the page is cached, any uncached snippets will be processed, and then it will pick up the POST and generate the appropriate output.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 7231
            • 4,205 Posts
            Sottwell, I hope you don’t mind but I pasted you great description into the Snippet Anatomy article in the wiki:
            http://wiki.modxcms.com/index.php/Snippet_call_anatomy#Snippets_and_the_MODx_Cache

            You said it so well that it would have been useless to try to do any better grin
              [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]
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              I don’t mind; I’ve posted this a number of times in response to similar questions.
                Studying MODX in the desert - http://sottwell.com
                Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                Join the Slack Community - http://modx.org