We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    I don't know why that wouldn't work. The Subscribe extra uses the same method. Do you have a password manager that might be filling in the hidden spam field?


    ------------------------------------------------------------------------------------------
    PLEASE, PLEASE specify the version of MODX you are using.
    MODX info for everyone: http://bobsguides.com/modx.html
      Did I help you? Buy me a beer
      Get my Book: MODX:The Official Guide
      MODX info for everyone: http://bobsguides.com/modx.html
      My MODX Extras
      Bob's Guides is now hosted at A2 MODX Hosting
      • 38357
      • 178 Posts
      No - there's no password manager. I have commented out the hidden spam field line and it makes no difference.
        • 38357
        • 178 Posts
        In desperately searching for an answer I have used Firebug to lookat the headers and compare with my testing server. Not having any experience in this area my interpretations may be innacurate - maybe someone can interpret for me?
        Testing Server:
        Response Headers
        Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0
        Connection Keep-Alive
        Content-Encoding gzip
        Content-Length 20
        Content-Type text/html
        Date Mon, 24 Sep 2012 12:47:36 GMT
        Expires Thu, 19 Nov 1981 08:52:00 GMT
        Keep-Alive timeout=5, max=100
        Location http://192.168.72.11/modx/index.php?id=59&username=600678&email=bobd%40testdomain.com
        Pragma no-cache
        Server Apache/2.2.22 (Unix) PHP/5.3.10
        Vary Accept-Encoding
        X-Powered-By PHP/5.3.10
        Production Server
        Response Headers
        Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0
        Connection close
        Content-Type text/html; charset=UTF-8
        Date Mon, 24 Sep 2012 11:48:12 GMT
        Expires Thu, 19 Nov 1981 08:52:00 GMT
        Pragma no-cache
        Server Apache
        Transfer-Encoding chunked
        X-Powered-By PHP/5.2.17

        Perhaps not relevant to my problem, but why is Connection close on the production server and keep-alive on the testing server?
          • 3749
          • 24,544 Posts
          I wish I could help, but I'm afraid I have no idea.


          ------------------------------------------------------------------------------------------
          PLEASE, PLEASE specify the version of MODX you are using.
          MODX info for everyone: http://bobsguides.com/modx.html
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting
            • 38357
            • 178 Posts
            Thanks Bob. Its very frustrating - the last thing I need to do to have everything up and running.
            It must be a setting somewhere as I have checked all the scripts very carefully. I have turned off friendly URL's and still it won't work. If I could find some way of seeing what the script is actually doing when it runs it might help :-( It certainly isn't sending anything to the database.
              • 38357
              • 178 Posts
              Solution found - cause of problem unknown.

              On my Development Server this call on the resource works, but will not work on the Production Server:
              [[!Register? 
              &submitVar=`registerbtn` 
              &activationResourceId=`64` 
              &submittedResourceId=`63` 
              &usergroups=`Member:Member` 
              &activationEmailTpl=`MylgnActivateEmailTpl` 
              &activationEmailSubject=`Please activate your account at [[++site_name]] ]] 
              
              [[$MylgnRegisterForm]]


              However, placing the call in the 'MylgnRegisterForm' chunk, making the
              !Register?
              call AFTER the form html and then calling the chunk in the resource with
              [[$MylgnRegisterForm]]
              works on the Production Server.

                • 27708 MODX Staff
                • 2,502 Posts
                Not that this will likely affect your testing but the example in the Register docs uses the old syntax for validation with the validation flags in the name values.

                name="email:required"


                You should now use the syntax shown in this example: http://rtfm.modx.com/display/ADDON/Register.Example+Form+1
                  Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub