% python manage.py migrate aldryn_newsblog
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/aldryn_newsblog/managers.py:31: RemovedInDjango18Warning: `RelatedManager.get_query_set` method should be renamed `get_queryset`.
class RelatedManager(ManagerMixin, TranslatableManager):
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/parler/forms.py:163: RemovedInDjango18Warning: Creating a ModelForm without either the 'fields' attribute or the 'exclude' attribute is deprecated - form ArticleAdminForm needs updating
return super(TranslatableModelFormMetaclass, mcs).__new__(mcs, name, bases, attrs)
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/parler/forms.py:163: RemovedInDjango18Warning: Creating a ModelForm without either the 'fields' attribute or the 'exclude' attribute is deprecated - form PersonForm needs updating
return super(TranslatableModelFormMetaclass, mcs).__new__(mcs, name, bases, attrs)
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/filer/fields/file.py:121: SyntaxWarning: FilerImageField can only be a ForeignKey to Image; filer.Image passed
warnings.warn(msg, SyntaxWarning)
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/filer/fields/multistorage_file.py:106: SyntaxWarning: MultiStorageFileField can handle only File objects;<function generate_filename_multistorage at 0x41fc0c8> passed
"%s passed" % upload_to, SyntaxWarning)
Operations to perform:
Apply all migrations: aldryn_newsblog
Running migrations:
Applying taggit.0001_initial...Traceback (most recent call last):
File "manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
utility.execute()
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 377, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/core/management/base.py", line 288, in run_from_argv
self.execute(*args, **options.__dict__)
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/core/management/base.py", line 338, in execute
output = self.handle(*args, **options)
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 161, in handle
executor.migrate(targets, plan, fake=options.get("fake", False))
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/db/migrations/executor.py", line 68, in migrate
self.apply_migration(migration, fake=fake)
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/db/migrations/executor.py", line 96, in apply_migration
if self.detect_soft_applied(migration):
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/db/migrations/executor.py", line 140, in detect_soft_applied
apps = project_state.render()
File "/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/django/db/migrations/state.py", line 75, in render
"for more" % new_unrendered_models
django.db.migrations.state.InvalidBasesError: Cannot resolve bases for [<ModelState: 'djangocms_text_ckeditor.Text'>]
This can happen if you are inheriting models from an app with migrations (e.g. contrib.auth)
in an app with no migrations; see https://docs.djangoproject.com/en/1.7/topics/migrations/#dependencies for more
I experimented with the contents of MIGRATION_MODULES, ultimately changing the contents to this:
This configuration enables the migration to complete successfully
(venv)octet :: quill_engage/django_testing/cms ‹master*› % python manage.py migrate aldryn_newsblog
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/aldryn_newsblog/managers.py:31: RemovedInDjango18Warning: `RelatedManager.get_query_set` method should be renamed `get_queryset`.
class RelatedManager(ManagerMixin, TranslatableManager):
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/parler/forms.py:163: RemovedInDjango18Warning: Creating a ModelForm without either the 'fields' attribute or the 'exclude' attribute is deprecated - form ArticleAdminForm needs updating
return super(TranslatableModelFormMetaclass, mcs).__new__(mcs, name, bases, attrs)
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/parler/forms.py:163: RemovedInDjango18Warning: Creating a ModelForm without either the 'fields' attribute or the 'exclude' attribute is deprecated - form PersonForm needs updating
return super(TranslatableModelFormMetaclass, mcs).__new__(mcs, name, bases, attrs)
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/filer/fields/file.py:121: SyntaxWarning: FilerImageField can only be a ForeignKey to Image; filer.Image passed
warnings.warn(msg, SyntaxWarning)
/home/mwilson/devel/ns/quill_engage/django_testing/venv/lib/python2.7/site-packages/filer/fields/multistorage_file.py:106: SyntaxWarning: MultiStorageFileField can handle only File objects;<function generate_filename_multistorage at 0x2adf0c8> passed
"%s passed" % upload_to, SyntaxWarning)
Operations to perform:
Apply all migrations: aldryn_newsblog
Running migrations:
Applying taggit.0001_initial... OK
Applying filer.0001_initial... OK
Applying aldryn_people.0001_initial... OK
Applying aldryn_categories.0001_initial... OK
Applying aldryn_newsblog.0001_initial... OK
Applying aldryn_newsblog.0002_newsblogconfig_template_prefix... OK
Applying aldryn_newsblog.0003_auto_20150422_1921... OK
To be honest, I've removed mention of MIGRATION MODELS from the instructions. These suggestions are (or should be) on the respective projects they affect.
I'm installing aldryn-newsblog into a new installation of djangocms and following the README closely.
When doing the initial migration my
MIGRATION_MODULES
setting is this:This produces:
I experimented with the contents of
MIGRATION_MODULES
, ultimately changing the contents to this:This configuration enables the migration to complete successfully
Could the README be incorrect?
Heres what I'm running in my virtualenv:
EDIT: also, here's my python version: