migrations to apps Reversing migrations Historical models Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using different versions of available software Serializing Django objects Serializing data Deserializing data Serialization formats Natural keys Django settings The basics Designating the settings reporting Email reports Filtering error reports How to provide initial data for models Provide initial data with migrations Provide data with fixtures How to integrate Django with a legacy database Give

migrations to apps Reversing migrations Historical models Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using different versions of available software Serializing Django objects Serializing data Deserializing data Serialization formats Natural keys Django settings The basics Designating the settings reporting Email reports Filtering error reports How to provide initial data for models Provide initial data with migrations Provide data with fixtures How to integrate Django with a legacy database Give

migrations to apps Reversing migrations Historical models Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using different versions of available software Serializing Django objects Serializing data Deserializing data Serialization formats Natural keys Django settings The basics Designating the settings reporting Email reports Filtering error reports How to provide initial data for models Provide initial data with migrations Provide data with fixtures How to integrate Django with a legacy database Give

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them as _ class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)}, ) ]

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)}, ) ]

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)}, ) ]

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={ 'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={ 'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={ 'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)

accidentally run migrations on a django CMS version 3 database. This can lead to corruption since the data structures for the CMSPlugin models are different. Warning Do not add CMS_CONFIRM_VERSION4 = True django CMS version 3 project unless you know what you are doing. Just running migrations can lead to data loss. Warning To migrate a django CMS version 3 project to version 4 you can have a look at django CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them