-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Django 1.4 no longer has 'message_set' #4
Comments
Thanks for finding this. There's a large range of admin issues with Mezzanine/Django 1.4 - I'm currently working through them, but at the moment it's unsupported. |
No worries, there a several crufty bits of Django that seem to have finished their deprecation cycle in 1.4 so I'm finding lots in different apps. I'm running a test of Mezz on 1.4 right now, so as I find any more I'll add issues (and if I figure out how to fix them I'll do a pull request). |
Thanks for your help. I've added a few issues I've found to Mezzanine's issues, and labeled them Django 1.4 If you find anything else please go ahead and add them there if they're missing. |
Closed by 4f4452e |
Request URL: http://127.0.0.1:8000/admin/media-library/mkdir/?ot=desc&dir=board&o=date
Django Version: 1.4c1
Exception Type: AttributeError
Exception Value:
'User' object has no attribute 'message_set'
seems to be related to http://code.google.com/p/django-filebrowser/issues/detail?id=338
temnoregg commented:
"It's because of 1.4 Django removed message_set methods
The Message model (in django.contrib.auth), its related manager in the User model (user.message_set), and the associated methods (user.message_set.create() and user.get_and_delete_messages()), which have been deprecated since the 1.2 release, will be removed. The messages framework should be used instead."
The text was updated successfully, but these errors were encountered: