Re: Encrpting urls to hide PKs

Why cant you do something like this to avoid exposing data if people are guessing primary keys if request.user == Users.objects.get(id=pk-url): Show data Else: raise 404 or redirect to home page The above requires a logged in a user but you get the idea of not allowing people to start

Re: Search Field on All Pages

Thanks for everyone's advice. My final solution will be to use template inheritance to have the same form across the site and to use the action="/search" to ensure I don't have to import a search function into every single view. Thanks again Wes On 8 August 2010 19:36, kostia wrote: > Yes, so

Re: Catching User's First Log in

Thanks for the advice. I'm going for boolean as I like the idea of flipping back on in the future for special events. Thanks Wes On 5 April 2010 21:06, Owen Nelson wrote: > > it does feel a little bit dirty to me. > Me too, that way leads to deciding something is a witch just because it > flo

Catching User's First Log in

Hi all, I'm trying to catch the first time someone logs in so I can present them with some options. I was wondering whether there is something readily available in Django for this or whether I'll need to go down the route of having a boolean field on a user table that becomes un-checked after they

Re: Table in models.py not being created during syncdb

Yep definitely in installed_apps. After several hours of playing I've changed my method of implementation to work around this issue. Thanks for everyone's help on this issue, really appreciated. Wes On 3 April 2010 18:16, Dennis Kaarsemaker wrote: > On wo, 2010-03-31 at 10:16 -0700, wchildsuk

Re: Table in models.py not being created during syncdb

Thanks but still no luck, it imports fine as expected. Also tried splitting it out to a separate models file but it failed to even pick that. Any other ideas? On 1 April 2010 08:35, Kenneth Gonsalves wrote: > On Thursday 01 Apr 2010 1:00:00 pm Wesley Childs wrote: > > I removed the

Re: Table in models.py not being created during syncdb

Hi, Thanks for the advice. I removed the sqlite db file, changed the table name to something more random and I still hit the same problem. Do you have any other ideas? Thanks Wes On 1 April 2010 00:42, Russell Keith-Magee wrote: > On Thu, Apr 1, 2010 at 1:16 AM, wchildsuk wrote: > > Hi, >