That's what I have. The problem is that you then have to restrict access on every page of your site to those who've accepted the EULA. What I would rather do is create a profile and only allow access to the EULA acceptance page once the person is registered and until they accept the EULA. I'm just having a hard time conceptualizing a way to do this code-wise.
On May 2, 5:41 pm, "Jonathan D. Baker" <[email protected]> wrote: > You could store the Eula as a boolean field on a user profile model and > manage it that way. > > Sent from my iPhone > > On May 2, 2012, at 3:34 PM, BGMaster <[email protected]> wrote: > > > > > > > > > Hi, > > > I'm trying to implement acceptance of a EULA into my site registration > > form. The EULA acceptance is on a separate page from the rest of the > > registration form. I'm trying to figure out a way to prevent the user > > from accessing the rest of the site without accepting the EULA. Every > > path I go down seems to end up being very hackish. Has anyone done a > > EULA in a separate view/page from the rest of the site registration? > > What method did you use? > > > Thanks > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
