-
Notifications
You must be signed in to change notification settings - Fork 29
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
Comment and media count crashing admin #386
Comments
Follow-up - in case it helps, here's the exception environment copypasta:
|
Please try downgrading Django to version 1.8 (with latest patch). |
Hey @josokinas thanks for the suggestion. As I said above, this isn't a feature we use/need so I'm happier with the patch above than going through a downgrade. Only reporting here for posterity and in the off-chance I may be able to help the project. Do you know - is it a bug in Django 1.9 or in GeoKey? Could this be something relevant to #379 |
Difficult to tell without replicating the situation. If changing Django version fixes the problem - most likely there's either bug in Django, or some change which was not reflected on GeoKey. Replicating with a test case would be ideal, as it could help to solve the issue. |
OK, I'll try and look into downgrading to 1.8 as soon as I can, and report back with results. |
Just to report this has been working for me on since pulling in later commits in this repo, so I guess this can be closed (original cause still unknown). |
@edwardgalligan I think with latest GeoKey update the issue should be solved as it now supports later Django version. |
I'm receiving this error in the GeoKey admin when visiting the main project overview page:
The issue appears to be with the following lines so I've put in place this temporary fix for now:
It's not really a feature I'd use/rely on, but I thought it would be worth reporting as a curiosity. Also worth noting, this crash does not occur on projects with 0 contributions. It also does not seem to affect the contribution count, only the comment and media count, so it's likely something related to joins on foreign keys with those tables.
I'll submit a PR if I can figure out the problem, but I'm not very familiar with Django so I've not been able to solve it sofar.
The text was updated successfully, but these errors were encountered: