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

Django 1.5 causes "TypeError: __init__() got an unexpected keyword argument 'verify_exists'" #11

Closed gruntfarm closed 11 years ago

gruntfarm commented 11 years ago

When doing syncdb with Django 1.5 this error is triggered:

...lib/python2.7/site-packages/zinnia/models/entry.py:496: RuntimeWarning: cmsplugin_zinnia.placeholder.EntryPlaceholder cannot be imported RuntimeWarning)

TypeError: init() got an unexpected keyword argument 'verify_exists'

Apparently django.db.models.fields.URLField.verify_exists parameter has been removed from Django 1.5 due to some security and performance issues. More about that here: http://stackoverflow.com/questions/10884053/why-do-i-get-this-error-when-i-run-python-manage-py-syncdb-all

Is there a way to get around this without downgrading Django?

Fantomas42 commented 11 years ago

Hi gruntfarm,

this issue seems related to django-cms. No URLField are used in cmsplugin-zinnia, so I will close the issue.

Regards

gruntfarm commented 11 years ago

Thanks for pointing me in the right direction. Django-cms indeed was the culprit. I rolled back to Django 1.4.1 and waited until they removed the verify_exists from the /plugins/link/models.py file, which they did recently.

I then tried to upgrade both Django and django-cms to the latest versions only to find that verify_exists error was still appearing when trying to sync the database. I found out that django_bitly plugin has the verify_exists parameter as well.. so I will notify the developer of that plugin that django-bitly doesn't work with django versions 1.5. and 1.5.1