Open rockyburt opened 12 years ago
Thanks for the report - I'll try and reproduce this in the next few days.
Hi Rocky,
I'm afraid I'm having trouble reproducing this with the current github master.
I've tried the following combinations:
@allow_lazy_user
decorator directly on a function-based view@allow_lazy_user
decorator a function-based view, applied in urls.py@allow_lazy_user
decorator directly on a class-based view in urls.pyEverything seemed to work as it should - I couldn't provoke the error.
You'll have to tell me a little more about your site, I'm afraid.
If you can get a small test case together for me to look at, which provokes the error, that'd be fantastic - even if it's a tarball of a demo site.
Incidentally, the small test site was SQLite - the larger, existing site was PostgreSQL.
I was setting up django-lazysignup 0.7.0 for the first time against a SQLite3 db. I'm running Django 1.3. I get an error when I access a view protected by allow_lazy_user. The code that hooks up allow_lazy_user is:
The error I get indicates a name collision which is practically impossible since the only user in the db is the admin user.