Zikula Community

• dunx
  
  

  • Rank: Softmore
  • Registered: May 25, 2004
  • Last visit: Oct 21, 2009
  • Posts: 192

  Posted: Aug 22, 2004 - 02:57 AM

  I'm developing a new module - fully API and templated. It's going reasonably well.
  
  For those that haven't taken the plunge yet, the idea seems to be to have a series of stages in creating your functionality. One stage is made up of:
  1. A function to prep your form.
  2. The form itself.
  3. A function to deal with the data and redirect you to the next page.
  
  My module has a number of these strung together and I'm using Mark's recommendation of using session variables to pass key data between the stages. Specifically, a user selects a membership type, then fills in their details, then the data is saved and they are presented with a confirmation screen, before a bit more data is saved, they go through credit card processing, the data is tweaked again and they end up at a final "all done" screen.
  
  The issue I have is with darn users trying to go back to previous pages and/or refreshing the current page. It just seems to muck all my data about and I get various errors such as "you don't have Auth" because the authid used in the previous form is now no good.
  
  Is there a "right and propper" way to go about the coding of this sort of linked stage design? I'm assuming there's either some process I need to go through after/before each stage or some API functions that need calling to ensure data remains consistent throughout.
  
  I'll be away from my puter for a whole week (which I'm strangely looking forward to), but will catch up with the thread when I return. Cheers in advance.

  • 
  •  
• **unknown user**
  

  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 1097

  Posted: Aug 22, 2004 - 10:15 PM

  One of the only way to prevent this (and it's 50% ), is to have the pnVarCleanFromInput in your main form page (function to prep form) that gets the data if one goes back using a form button instead ot the "Previous Page" button of the browser...
  
  You put in hidden values the data a user entered and make a go back button (different form tag). The AuthID is then reset but valid for the next page when the user hit the submit and fields (or part of them) are already set with what the user entered the first time.
  
  That won't prevent the "Previous page" problem... but it will help.

  • 
  •  
• dunx
  
  

  • Rank: Softmore
  • Registered: May 25, 2004
  • Last visit: Oct 21, 2009
  • Posts: 192

  Posted: Aug 31, 2004 - 12:05 AM

  That's certainly an option, but not a very thorough one as you've pointed out.
  
  Are there no methods, when using pnRender, to make previous pages unavailable? There are some caching functions, but I'm not really clear on what they actually allow you to do, even after reading the Smarty documents.
  
  At the moment, it seems like I'll have to add a huge heap of defensive functionality to my coding to stop people messing up when using a browser's native validation during form data entry. Is there really no cleaner way?

  • 
  •  
• dunx
  
  

  • Rank: Softmore
  • Registered: May 25, 2004
  • Last visit: Oct 21, 2009
  • Posts: 192

  Posted: Sep 01, 2004 - 12:26 AM

  What about some of the caching commands? I suppose I need to test this all out, as nobody seems to know much about usability of module design :(

  • 
  •  
• **unknown user**
  

  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 1097

  Posted: Sep 01, 2004 - 09:09 PM

  Unless I'm wrong and some javascript geek or something alike has a solution, you'll never be able to prevent the browser's back button.
  :(

  • 
  •  
• dunx
  
  

  • Rank: Softmore
  • Registered: May 25, 2004
  • Last visit: Oct 21, 2009
  • Posts: 192

  Posted: Sep 01, 2004 - 11:20 PM

  It wasn't that. It was more a way of it causing chaos. Sometimes when you go back, you get a page expired message for example. That might help. I think I need to play a bit more. Will get back when I find a solution - whole or partial.

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.