Add the following apps to your INSTALLED_APPS [https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-INSTALLED_APPS]. This includes django CMS itself as well as its dependencies and other highly default cms_page_media/ relative to MEDIA_ROOT [https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-MEDIA_ROOT]) is writeable by the user under which Django will be running. If you have opted com/etianen/django-reversion] and add it to INSTALLED_APPS [https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-INSTALLED_APPS]: 'reversion' You need to add the django CMS middlewares to your MIDDLEWARE_CLASSES

django CMS requires you to set the LANGUAGES [https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-LANGUAGES] setting. This should list all the languages you want your project to serve, and and must include the language in LANGUAGE_CODE [https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-LANGUAGE_CODE]. For example: LANGUAGES = [ ('en', 'English'), ('de', 'German'), ] default in a new Django project’s DATABASES [https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-DATABASES]. Note For deployment, you’ll need to use a production-ready database with Django

django CMS requires you to set the LANGUAGES [https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-LANGUAGES] setting. This should list all the languages you want your project to serve, and and must include the language in LANGUAGE_CODE [https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-LANGUAGE_CODE]. For example: LANGUAGES = [ ('en', 'English'), ('de', 'German'), ] default in a new Django project’s DATABASES [https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-DATABASES]. Note For deployment, you’ll need to use a production-ready database with Django

django CMS requires you to set the LANGUAGES [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-LANGUAGES] setting. This should list all the languages you want your project to serve, and and must include the language in LANGUAGE_CODE [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-LANGUAGE_CODE]. For example: LANGUAGES = [ ('en', 'English'), ('de', 'German'), ] default in a new Django project’s DATABASES [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-DATABASES]. Note For deployment, you’ll need to use a production-ready database with Django

django CMS requires you to set the LANGUAGES [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-LANGUAGES] setting. This should list all the languages you want your project to serve, and and must include the language in LANGUAGE_CODE [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-LANGUAGE_CODE]. For example: LANGUAGES = [ ('en', 'English'), ('de', 'German'), ] by default in a new Django project’s DATABASES [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-DATABASES]: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3',

django CMS requires you to set the LANGUAGES [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-LANGUAGES] setting. This should list all the languages you want your project to serve, and and must include the language in LANGUAGE_CODE [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-LANGUAGE_CODE]. For example: LANGUAGES = [ ('en', 'English'), ('de', 'German'), ] by default in a new Django project’s DATABASES [https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-DATABASES]. Note For deployment, you’ll need to use a production-ready database with Django

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages', ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your context_processors.auth', 'django.contrib.messages.context_processors.messages', ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages', ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your context_processors.auth', 'django.contrib.messages.context_processors.messages', ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session