search

django-blog-zinnia / cmsplugin-zinnia

Bridge between django-blog-zinnia and django-cms
BSD 3-Clause "New" or "Revised" License
53 stars 46 forks source link

cmsplugin_zinnia.placeholder.EntryPlaceholder cannot be imported with django-reversion 1.8.0 #23

Closed robertour closed 10 years ago

robertour commented 10 years ago

I am not sure if I should report this here (or in django-reversion), but I guess people with the same problem with the same problem will end here. Anyway, my apologizes if I am reporting this in the wrong place.

I upgraded django-blog-zinnia (0.13) and cmsplugin-zinnia (0.5.1) and starting to struggle with this problem:

ImproperlyConfigured: cmsplugin_zinnia.placeholder.EntryPlaceholder cannot be imported.

Not sure how (I think it was because I run pip install django-blog-zinnia --upgrade), I ended upgrading many other packages, and started to get the above errors.

I finally figure out that it was django-reversion version 1.8. I downgraded to version 1.7.1 and I get rid off the error.

Fantomas42 commented 10 years ago

Hello,

I've never used django-reversion but your report seems indicating that the issue is coming from django-reversion no ?

If so open a ticket on his issue tracker.

Regards

bittner commented 10 years ago

I've had the same issue. In my case it looks like this is due to a conflict of the packages django-tagging and tagging. The latter was hiding the former package (both go with import tagging).

The problem arises for me, because I use emencia.django.newsletter, which has a dependency on tagging. Zinnia and the cmsplugin, however, need django-tagging. -- I can post more info on the case if requested.

bittner commented 10 years ago

Just for sake of completeness: Everyone having this or a similar problem, run python manage.py syncdb --traceback for a full stack trace that helps with tracking down where things could have possibly gone wrong.

bittner commented 10 years ago

Well, obviously true: The main culprit is really django-reversion>=1.8.0. See django-cms PR https://github.com/divio/django-cms/pull/2308.

The issue is fixed in django-cms branch support/2.4.x (https://github.com/divio/django-cms/commit/af9144db818736dd50036178bf6f00565cfbaa1d) but no new release has been issued yet, as of today. The latest code from the support branch works even with django-reversion==1.8.0. Install with, e.g.

pip install git+https://github.com/divio/django-cms.git@support/2.4.x#egg=django-cms-support_2.4.x
robertour commented 10 years ago

Thanks for the update!