PUPUT_USERNAME_FIELD

[robslotboom]

get_entries() in puput.models BlogPage raises an error.

def get_entries(self):
    field_name = 'owner__%s' % getattr(settings, 'PUPUT_USERNAME_FIELD', 'username')
    return EntryPage.objects.descendant_of(self).live().order_by('-date')#.select_related(field_name)

This results in select_related('owner__username') which is wrong and shoud be
select_related('owner')

[marctc]

Did you extend the default Django User model? Did you remove the username field in that custom User model?
If the above questions have an affirmative answer you should set PUPUT_USERNAME_FIELD with a proper username field.

[robslotboom]

Did you extend the default Django User model?
Yes

Did you remove the username field in that custom User model?
No

If the above questions have an affirmative answer you should set PUPUT_USERNAME_FIELD with a proper username field.

Are you absolutely sure?
In my opinion select_related('owner__username') is pointing to a non FK-field.

Ir raises:

django.core.exceptions.FieldError: Non-relational field given in select_related: 'username'. Choices are: user_profiles, userprofile

[marctc]

What Django version are you using?

[robslotboom]

1.10.1

[marctc]

Hi @robslotboom. I did some tests and I could reproduce the error. I'll fix it ASAP.

Thanks!

[robslotboom]

Hi Marc,

You are welcome.
And thank you for the nice app you made.

Best regards,

Robert Slotboom

Op 28 sep. 2016, om 12:20 heeft Marc Tudurí notifications@github.com het volgende geschreven:

Hi @robslotboom. I do some tests and I could reproduce the error. I'll fix it ASAP.

Thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[lgellert]

I just ran into the same exact error as @robslotboom.

[marctc]

It seems that Puput is not fully compatible with Django 1.10 right now. I'll fix it ASAP.

thanks

[marctc]

Fixed in the last commit