[PATCH] Resolve removed 'AUTH_PROFILE_MODULE' setting

[Stephen Finucane]

> Hello Damien,
> 
> Am 19.11.2014 um 15:26 schrieb Damien Lespiau:
> >> There are three changes necessary:
> >>
> >>  * Replace profile model's 'ForeignKey' with a 'OneToOneField'
> > 
> > I take that it doesn't actually change the DB schema and thus is safe to
> > deploy on existing live instances?
> 
> I take a quote from the website Stephen was pointing:
> 
> > In this step we change the ForeignKey to Django's User model to a
> > OneToOneField. Again, this does not affect the database schema.

This was my assumption. It appeared to work "out of the box" for me. Could you suggest a way to verify that this is indeed the case?

> 
> As far as I could testing (on a fresh new setup) the patch Stephen was
> posting is working. But I think there a some more changes needed to let
> patchwork play with a current Django 1.7 version.
> But my experience with Django and Python is more pure, I can't solve the
> issues.
> 
> I have setup one project but i got the following error output if I will
> now open http://localhost/patchwork
> 
> > FieldError at /project/burp.com/list/
> > 
> > Cannot resolve keyword 'userprofile' into field. Choices are: bundle, date_joined, email, emailconfirmation, first_name, groups, id, is_active, is_staff, is_superuser, last_login, last_name, logentry, password, patch, person, profile, user_permissions, username
> > 
> > Request Method: 	GET
> > Request URL: 	http://localhost/patchwork/project/burp.com/list/
> > Django Version: 	1.7.1
> > Exception Type: 	FieldError
> > Exception Value: 	
> > 
> > Cannot resolve keyword 'userprofile' into field. Choices are: bundle, date_joined, email, emailconfirmation, first_name, groups, id, is_active, is_staff, is_superuser, last_login, last_name, logentry, password, patch, person, profile, user_permissions, username
> > 
> > Exception Location: 	/usr/lib/python2.7/dist-packages/django/db/models/sql/query.py in raise_field_error, line 1389
> > Python Executable: 	/usr/bin/python
> > Python Version: 	2.7.8
> > Python Path: 	
> > 
> > ['/usr/lib/python2.7',
> >  '/usr/lib/python2.7/plat-x86_64-linux-gnu',
> >  '/usr/lib/python2.7/lib-tk',
> >  '/usr/lib/python2.7/lib-old',
> >  '/usr/lib/python2.7/lib-dynload',
> >  '/usr/local/lib/python2.7/dist-packages',
> >  '/usr/lib/python2.7/dist-packages',
> >  '/usr/lib/python2.7/dist-packages/PILcompat',
> >  '/usr/lib/python2.7/dist-packages/gst-0.10',
> >  '/usr/lib/python2.7/dist-packages/gtk-2.0',
> >  '/usr/lib/pymodules/python2.7',
> >  '/usr/share/patchwork/wsgi/..',
> >  '/usr/share/patchwork/wsgi/../apps']
> > 
> > Server time: 	Thu, 20 Nov 2014 04:00:32 +1100
> 
> The rest is working fine, but I don't know what's going wrong here.

This is a little worrying. Carsten - which version of the patch did you use (I made a mistake and resubmitted the patch with fixes. This sounds like something the first patch could have caused). If you used "v1", try "v2". If you used "v2", could you send a screenshot of the error page with debugging enabled so I can try to reproduce the issue and see what I've missed. I'm not sure if it's related to this patch but it would be good to iron out any Django 1.7 bugs while we're at it.

Stephen

> 
> Regards
> Carsten
> _______________________________________________
> Patchwork mailing list
> Patchwork at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/patchwork
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20141119/c42bdf3f/attachment.html>