I just updated to Mezzanine 4.1 from 4.0.1 and made the jump to Django 1.9.1 on python 3. I'm also using django_auth_ldap to authenticate users and create them automatically. This has always worked fine, but after the updates it doesn't seem to behave anymore. What happens now is that user accounts are created and added to the auth_user table in the DB, but nothing is added to the "core_sitepermission" table to say the user has access to the site. So when the user tries to log in to the admin site they are told they don't have permission. Users who previously had an account are still able to log in because they have entries in the site permissions. If I log in as the super user I'm able to edit the "broken" user, select the listed site under Site Permissions, and click Save. This adds the user to the site permissions table. Note that all I had to do was *select* the site to get it to add the permission.
Has anyone had anything like this happen to them? Any ideas where I should start looking in the source code to debug this? It's been a while since I've touched this site so I could be missing something obvious. Thanks. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
