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
1.1 drops support for Django 1.7? #115
Comments
can you paste a full traceback please? |
It's a 350kb email, not that helpful ;-) I'll check if I can trim it in a dev environment |
OK, at this point all we know is that it breaks in the django template constance/templates/admin/constance/change_list.html, at line 63 However, it seems to be working on a vanilla django install, so the error is probably in the interaction with some other apps and/or ordering. I'll write more if I find anything. |
Hi, We've traced the problem to the template context processor: If we replace this to for instance: everything works like expected. |
The context processor hasn't changed for quite a while so I'm not sure what I can do from here. A full traceback is the only way I can help debug this. |
Here's the full traceback. I doubt it will be helpful as the error has somehow to do with the value of config as it's passed to the template and the trace only show what parts of Django blow up.
|
Aha, thanks, so it happens while rendering the list of config values. I have an idea which change triggered that. |
1.1.1 is out with the fix. Thanks! |
Thanks, we'll test it on Monday :) |
Sure, thanks for using constance ;) |
Just a heads up, on Django 1.8.1 I had to revert to version 1.1 instead of 1.1.1. I was getting this error, but I goes away on 1.1. Added context processor |
@adamrt Huh, what error? |
Hey sorry for not being more specific. I was getting the error for this issue report that has been closed.
I found this closed issue report and reverted to 1.1 from 1.1.1 since I was already on 1.1.1 and the issue was fixed. I am running Grappelli though which causes an error with boolean fields being required as well, so that could be my root issue. I am going to do some more digging though to see if I could provide more information. |
I got this too, it's certainly from Grappelli. I get it when I have Grappelli and constance.context_processors.config enabled. If I disable the context processor the error goes away but the constance settings don't show in admin. |
If someone facing that problem because of |
The doc claims that 1.1 adds support for Django 1.8 and 1.9, while <=1.6 are not supported any more. That's fine, except that 1.7(.10) support also seems to be gone. When clicking on the config in django admin, one gets:
TypeError at /admin/constance/config/
object of type 'Config' has no len()
...
Exception Location: .../python2.7/site-packages/django/utils/functional.py in inner, line 225
This is while using pyhon 2.7. The net result is that one has to upgrade constance exactly at the time of a django upgrade, which is suboptimal. Is this really the case?
The text was updated successfully, but these errors were encountered: