Take a look at django-registration app. With slight modification it should
satisfy your requirements.

For URL encryption, you can generate some sort of UUID and save in your
database that such UUID corresponds to given profile PK. django-registration
uses such urls for email confirmation.

On Mon, May 9, 2011 at 3:24 PM, ALJ <astley.lejas...@gmail.com> wrote:

> I have a form that I use to collect contact information from
> unregistered users. When they submit the form I want to redirect to a
> confirmation page (as the Django documentation suggests). However,
> instead of a generic page, I wanted to include the information that
> they have submitted and the contact details of the person for their
> area. I was also thinking that I could include the current status of
> their enquiry. Therefore they could perhaps use the same link to come
> back to check the status of their query.
>
> Given that, is there a best practice pattern for handling this
> situation? I have a quick demo where the URL is:
>
> http://www.mydomain.com/contact/confirmation/1234
>
> ... where '1234' is the pk for the query. Obviously I would want to
> encrypt the pk in this case, otherwise someone could just use the pk
> to trawl through the database.
>
> Are there any default ways of encrypting django urls?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to