Django 1.8 + CMS error: django.db.utils.ProgrammingError: relation "cms_cmsplugin" does not exist

Question

I got the same error 3 times already, before I didn't find the solution in Google nor here, and I guess I'm not the only one who got it.

From a fresh installation, I install at the same time the django-cms plugin an many of its plugins.

After running

python manage.py makemigrations
python manage.py migrate

I get this error: django.db.utils.ProgrammingError: relation "cms_cmsplugin" does not exist

Answer 1

Well, what I do is to remove all cms plugins except 'cms' itself, run python manage.py migrate add again all plugins and alter, again, python manage.py migrate

It seems that Django tries to create the tables for the plugins before the 'cms' app's one

As you see it's not a big deal if you just know it.

Usually people will install them one by one, but if you do it with pip from requirements.txt or similar, you will face this.

Answer 2

Yeah I resolved this issue....the main thing was that i was using django 1.7 and by default it was trying to run south migrations so in order to resolve that i just added this to MIGRATION_MODULE under the settings.py: 'djangocms_text_ckeditor': 'djangocms_text_ckeditor.migrations_django',

This will explicitly tell the framework to run migrations instead of south migrations. Since the main issue was djangocms_text_ckeditor's table was not getting created under the db

Answer 3

I'm not familiar with the specific issue, but sometimes going to migrations folder in your app

(app->migrations) and deleting all the files except the __init__ files and running python manage.py migrate helped me.

Answer 4

I just comment all of my custom django cms plugins in my django settings and migrate. Then uncomment them and migrate again.

# setting.py
INSTALLED_APPS = (
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.admin',
    'django.contrib.sites',
    ...
    # 'MY_DJANGO_CMS_PLUGIN',
)

After that run

python manage.py migrate

And uncomment MY_DJANGO_CMS_PLUGIN, and run migrate again.

Answer 5

As this seems to be top answer when searching for django.db.utils.programmingerror: relation "x" does not exist..

We encountered this issue in our DevOps pipeline, and were able to resolve it by listing the migrations with python manage.py showmigrations immediately before the problem task.

Possible it's refreshing on re-examining the database..

https://docs.djangoproject.com/en/4.1/ref/django-admin/#django-admin-showmigrations