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

    I have a form (snippet/external), with name and addresses fields, with a session, to remember the correct answers and reset the wrong ones, to try again.
    Now, in MODX, the code simply blocks once a correct answer is entered. It resets the others, keeps the correct and that's it. if you try in another browser will show you the same, form partly completed, locked at that state.

    I guess there's something wrong with the sessions ?
    I'm not a PHP guru or something. How can this be fixed ?

    Thanks ! [ed. note: modxvirtual last edited this post 13 years, 1 month ago.]
      • 4172
      • 5,888 Posts
      Are you probably calling your snippet cached?

      Another reason for issues may be, that your snippet is trying to use its own SESSION and not the SESSION started by MODX.
        -------------------------------

        you can buy me a beer, if you like MIGX

        http://webcmsolutions.de/migx.html

        Thanks!
        • 44285
        • 13 Posts
        Quote from: Bruno17 at Sep 15, 2013, 10:01 AM
        Are you probably calling your snippet cached?

        Another reason for issues may be, that your snippet is trying to use its own SESSION and not the SESSION started by MODX.

        yes, the snippet has it's own session

        how can that be fixed ?
          • 44285
          • 13 Posts
          I've found the answer here: https://forums.modx.com/thread/28909/un-cached-snippet-calls-in-revo

          Quote from: splittingred at Sep 30, 2009, 05:34 PM
          Any Tag in Revo (snippet, chunk, placeholder, tv, etc) can add a ! to the beginning to be uncached. Examples:

          [[!UncachedSnippet]]
          [[!$UncachedChunk]]
          [[!+UncachedPlaceholder]]
          [[!*UncachedTV]]
          [[!~UncachedLink]]
          [[!%UncachedLexiconEntry]]
          [[!++UncachedSetting]]
          

          No need for session_start(); neither. MODX seems to start it's own session.