I have figured out how to determine if the url_conf was obtained from an internal link (which would be the only acceptable workflow) or through a url that the user typed into the address bar trying to subvert the workflow.
See the attached screen shot of the view. If the view goes through the except statement, I would redirect to an appropriate page. On Monday, October 13, 2014 9:58:28 AM UTC-4, Collin Anderson wrote: > > Hi Robert, > > I once had a 4-step ecommerce checkout, and at one point, I considered > using class based views for each step, and have a class method on each view > that runs form validation on the current data in the database to see if the > user is allowed to continue. It would then need to redirect back to itself > if it wasn't valid. > > In the end I decided to do some non DRY, but simple sanity checks in the > later views and redirect to a previous step if needed. > > Collin > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3839438f-ebf0-436d-9a0e-dde412605b2d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
