The proposal to merge lp:~widelands-dev/widelands-website/auto_one_to_one_ractivating into lp:widelands-website has been updated.
Description changed to: Another issue from the update to django 1.8: Formerly to django 1.8 entrys to the database of wlprofile and wlggz has been created on demand. For some reason i didn't checked this when working on the django 1.8 branch and thought the database entries got created during registering. The last django errors from today told me that there is something wrong: A user who registered in year 2010 tried to access his profile the first time, and django through the error. For this user i created the wlprofile and wlggz database entries by hand over the admin site. Comparing the amount of users and wlprofiles i found that we have over 4000 users while there are only a bit more than 2000 wlprofiles :-S This branch brings back the old behavior. I didn't know much about the code change, just get it from here: https://github.com/skorokithakis/django-annoying/issues/36 So the code may need a review from a more experienced user. This branch is tested here at home including normal registration over the registration app. I decided to move the relevant code to wl_utils because this code was used two times (wlprofile and wlggz). Additionally removed the code introduced by my misunderstanding. We should get this in as soon as possible. For more details, see: https://code.launchpad.net/~widelands-dev/widelands-website/auto_one_to_one_ractivating/+merge/310813 -- Your team Widelands Developers is requested to review the proposed merge of lp:~widelands-dev/widelands-website/auto_one_to_one_ractivating into lp:widelands-website. _______________________________________________ Mailing list: https://launchpad.net/~widelands-dev Post to : widelands-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~widelands-dev More help : https://help.launchpad.net/ListHelp
