fix: Mention DEFAULT_AUTO_FIELD in manual install section

django-cms · fsbraun · May 9, 2023 · Feb 27, 2023 · Mar 2, 2023 · Mar 8, 2023
commit 71b6ca8276bf3ccc3f7a70cfdbf216ad80ced95c
diff --git a/docs/introduction/01-install.rst b/docs/introduction/01-install.rst
@@ -247,6 +247,15 @@ You can use SQLite, which is included in Python and doesn't need to be installed
 
     Refer to :setting:`Django's DATABASES setting documentation <django:DATABASES>` for the appropriate configuration for your chosen database backend.
 
+Disable BigAutoField
+--------------------
+
+Since Django 3.2 `django-admin startproject` command creates `setting.py` with enhancement for DB autoincrement primary keys `DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'`. Django CMS was build against Django defaults, so you should remove this setting to get default behaviour which is equal to setting `DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'`.
+
+.. info::
+
+    If you keep `DEFAULT_AUTO_FIELD` in `settings.py` as was created by `django-admin startproject` you will get error of missing migrations in most django CMS related models (packages installed via pip), in minimal install of django CMS applications `cms` and `menus` are reporting missing migrations.
+
 Confirming that you are not migrating a version 3 project
 ---------------------------------------------------------
 
@@ -265,7 +274,7 @@ This is to ensure that you do not accidentally run migrations on a django CMS ve
     To migrate a django CMS version 3 project to version 4 you can have a look at `django CMS 4 migration <https://github.com/Aiky30/djangocms-4-migration>`_. This is a third party project supposed to assist the migration from v3 to v4. It is not (yet) officially supported.
 
 Database tables
----------------
+===============
 
 Now run migrations to create database tables for the new applications::