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 watch_models allows the frontend editor to redirect the user to the model instance get_absolute_url whenever an instance of this model is created or saved through the frontend editor (see Detecting URL changes

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 watch_models allows the frontend editor to redirect the user to the model instance get_absolute_url whenever an instance of this model is created or saved through the frontend editor (see Detecting URL changes

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 the plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface render_template Minimally-required applications and settings Open the new project’s settings.py file in your text editor. INSTALLED_APPS You will need to add the following to its list of INSTALLED_APPS: 'django.contrib

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 Minimally-required applications and settings Open the new project’s settings.py file in your text editor. INSTALLED_APPS You will need to add the following to its list of INSTALLED_APPS: 'django.contrib

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 Minimally-required applications and settings Open the new project’s settings.py file in your text editor. INSTALLED_APPS You will need to add the following to its list of INSTALLED_APPS: 'django.contrib

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 Minimally-required applications and settings Open the new project’s settings.py file in your text editor. INSTALLED_APPS You will need to add the following to its list of INSTALLED_APPS: 'django.contrib

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 the plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface render_template Minimally-required applications and settings Open the new project’s settings.py file in your text editor. 4.1. Django/Python compatibility table 31 django cms Documentation, Release 3.9.0 INSTALLED_APPS

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 the plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface render_template Minimally-required applications and settings Open the new project’s settings.py file in your text editor. INSTALLED_APPS You will need to add the following to its list of INSTALLED_APPS: 'django.contrib

(Step 4) The page we just created is just a draft and needs to be published once you finish. As an editor, only you can see and edit your drafts, other visitors to your site will only see your published 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 the plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface render_template

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 watch_models allows the frontend editor to redirect the user to the model instance get_absolute_url whenever an instance of this model is created or saved through the frontend editor (see Detecting URL changes