You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2019. It is now read-only.
If you try to run the dumpdata command and have aldryn_blog in your INSTALLED_APPS you'll get the following error:
CommandError: Unable to serialize database: relation "aldryn_blog_latestentriesplugin" does not exist
LINE 1: ...n_blog_latestentriesplugin"."latest_entries" FROM "aldryn_bl...
According to the warnings raised by DjangoCMS, support for the cmsplugin_ table naming thing will be dropped in DjangoCMS 3.1. I guess creating a migration to rename this table would make sense, as it would not only fix the dumpdata command, but also remove the warnings. FYI the table cmsplugin_authorsplugin is also affected.
The text was updated successfully, but these errors were encountered:
If you try to run the
dumpdata
command and havealdryn_blog
in yourINSTALLED_APPS
you'll get the following error:I guess that's because, according to the migrations, the table was created under the name
cmsplugin_latestentriesplugin
(see https://github.com/aldryn/aldryn-blog/blob/master/aldryn_blog/migrations/0001_initial.py). For some reason thedb_table
attribute of the frozenlatestentriesplugin
model disappeared in migration 13 (https://github.com/aldryn/aldryn-blog/blob/master/aldryn_blog/migrations/0013_auto__add_category__add_categorytranslation__add_unique_categorytransl.py).According to the warnings raised by DjangoCMS, support for the
cmsplugin_
table naming thing will be dropped in DjangoCMS 3.1. I guess creating a migration to rename this table would make sense, as it would not only fix thedumpdata
command, but also remove the warnings. FYI the tablecmsplugin_authorsplugin
is also affected.The text was updated successfully, but these errors were encountered: