widelands-dev team mailing list archive
-
widelands-dev team
-
Mailing list archive
-
Message #07833
Re: [Merge] lp:~widelands-dev/widelands-website/django1_8 into lp:widelands-website
Ah, and some information about the setting ATUTH_PROFILE_MODULE:
http://bazaar.launchpad.net/~widelands-dev/widelands-website/django1_8/view/head:/settings.py#L174
I understand this isn't used anymore (see the link in comment). We have an extended user profile, and have to link our wlprofile with the Django user model by ourself. This is made in
http://bazaar.launchpad.net/~widelands-dev/widelands-website/django1_8/revision/434#mainpage/views.py
wlprofile uses a special field called AutoOneToOneField:
http://bazaar.launchpad.net/~widelands-dev/widelands-website/django1_8/view/head:/wlprofile/fields.py#L25
I 'believe' it should automatically create the linking of the models
wlprofile <-> django user
Nevertheless it does not do this (anymore?). So this a bit unclear to me, but current implementation works, except creating a user over the admin page: If one creates a user over admin_auth-profile he has to link it afterwards by hand in wlprofile-profile. But a user should never be made with the admin page.
That's all a bit complicated... feel free to ask :-)
--
https://code.launchpad.net/~widelands-dev/widelands-website/django1_8/+merge/298561
Your team Widelands Developers is requested to review the proposed merge of lp:~widelands-dev/widelands-website/django1_8 into lp:widelands-website.
References