[EMAIL PROTECTED] wrote:
> I considered this before, but with the configuration of the lan of my
> client if I try to access the public IP from a machine of the lan I get
> the router's configuration web page. And they don't allow me to
> reconfigure this.
In which case, I think you should be ab
[EMAIL PROTECTED] wrote:
> As we haven't a domain name I set the SESSION_COOKIE_DOMAIN to the
> public IP of the site. Well this works great from Internet, but when I
> try to access the admin site from the lan of my client I couldn't log
> in. If I change the SESSION_COOKIE_DOMAIN it works into
I ran into this problem as well. I believe the source of the problem is
here:
> File
> "/usr/lib/python2.3/site-packages/Django-0.95-py2.3.egg/django/contrib/auth/decorators.py"
> in _dec
> 18. _checklogin.__name__ = view_func.__name__
If "readonly attribute" is to be believed, then I *think* __
> the import statement worked fine but not the create_user:
> AttributeError: type object 'User' has no attribute 'create_user'
Whoops, that should be User.objects.create_user()
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
Yes, you missed something, but you aren't the first! If you have
django.contrib.auth in your INSTALLED_APPS (should be there by default,
I think), and ran manage.py syncdb, then it should have prompted you
for a superuser account username and password.
If you did that, but don't remember what you
Another approach is to use signals. In models.py
from django.dispatch import dispatcher
from django.contrib.auth.models import User
def user_save(instance):
if not instance.password.startswith('sha1$'):
instance.set_password(instance.password)
return
dispatcher.connect(user_save,
6 matches
Mail list logo
