Create content creation wizards Create admin for grouper models Extend Page & Title models Test your extensions Sharing functionality CMS application configuration How to use placeholders outside the CMS Placeholder question>" 4. Create the FAQ CMS app: In the apps’s cms_apps.py create the FaqConfig class. This extensions tells django CMS how to get the app config instances. 5. Add models to the admin interface: Its fields (e.g. adding an icon for every page) by using the extension models: cms.extensions.PageExtension and cms.extensions.PageContentExtension, respectively. Note Changed in version 4.1: In django CMS

Release 4.1.2 4. Create the FAQ CMS app: In the apps’s cms_apps.py create the FaqConfig class. This extensions tells django CMS how to get the app config instances. from django.core.exceptions import ObjectDoesNotExist fields (e.g. adding an icon for every page) by using the extension models: cms.extensions. PageExtension and cms.extensions.PageContentExtension, respectively. Note: Changed in version 4.1: In django CMS Django/Python compatibility table 123 django cms Documentation, Release 4.1.2 PageContent vs Page extensions The difference between a page extension and a page content extension is related to the difference

Release 4.1.1 4. Create the FAQ CMS app: In the apps’s cms_apps.py create the FaqConfig class. This extensions tells django CMS how to get the app config instances. from django.core.exceptions import ObjectDoesNotExist fields (e.g. adding an icon for every page) by using the extension models: cms.extensions. PageExtension and cms.extensions.PageContentExtension, respectively. Note: Changed in version 4.1: In django CMS Django/Python compatibility table 123 django cms Documentation, Release 4.1.1 PageContent vs Page extensions The difference between a page extension and a page content extension is related to the difference

content creation wizards Create admin for grouper models Extend Page & Page Content models Test your extensions Sharing functionality CMS application configuration How to use placeholders outside the CMS Placeholder question>" 4. Create the FAQ CMS app: In the apps’s cms_apps.py create the FaqConfig class. This extensions tells django CMS how to get the app config instances. 5. Add models to the admin interface: Its fields (e.g. adding an icon for every page) by using the extension models: cms.extensions.PageExtension and cms.extensions.PageContentExtension, respectively. Note Changed in version 4.1: In django CMS

configuration Working with templates Extending the page & title models Extending the Toolbar Testing Your Extensions Placeholders outside the CMS Caching Frontend editing for Page and Django models Sitemap Guide Page extensions Implement a basic extension Using extensions Complete toolbar API Extending the Toolbar Registering Adding items Modifying an existing toolbar Frontend Testing Your Extensions Testing commonly-used plugins. There are even more plugins available on the django CMS extensions page [http://www.django-cms.org/en/extensions/]. In addition, make sure you uncomment (enable) 'django.contrib.admin'

multiple languages Work with templates Extend Page & Title models Extend the Toolbar Test your extensions Use placeholders outside the CMS Manage caching Enable frontend editing for Page and Django models for every page) by using the extension models: cms.extensions.PageExtension and cms.extensions.TitleExtension, respectively. Title vs Page extensions The difference between a page extension and a title extension example The model To add a field to the Page model, create a class that inherits from cms.extensions.PageExtension. Your class should live in one of your applications’ models.py (or module). Note

multiple languages Work with templates Extend Page & Title models Extend the Toolbar Test your extensions Use placeholders outside the CMS Manage caching Enable frontend editing for Page and Django models for every page) by using the extension models: cms.extensions.PageExtension and cms.extensions.TitleExtension, respectively. Title vs Page extensions The difference between a page extension and a title extension example The model To add a field to the Page model, create a class that inherits from cms.extensions.PageExtension. Your class should live in one of your applications’ models.py (or module). Note

more detail in Some commonly-used plugins. There are even more plugins available on the django CMS extensions page. In addition, make sure you uncomment (enable) ’django.contrib.admin’ You may also wish to fields (e.g. adding an icon for every page) by using the extension models: cms.extensions.PageExtension and cms.extensions.TitleExtension, respectively. What’s the difference? The difference between a page add a field to the page model, create a class that inherits from cms.extensions.PageExtension. Make sure to import the cms.extensions.PageExtension model. Your class should live in one of your apps’ models

more detail in Some commonly-used plugins. There are even more plugins available on the django CMS extensions page. In addition, make sure you uncomment (enable) ’django.contrib.admin’ You may also wish fields (e.g. adding an icon for every page) by using the extension models: cms.extensions.PageExtension and cms.extensions.TitleExtension, respectively. What’s the difference? The difference between a add a field to the page model, create a class that inherits from cms.extensions.PageExtension. Make sure to import the cms.extensions.PageExtension model. Your class should live in one of your apps’ models

Customise navigation menus Create content creation wizards Extend Page & Title models Test your extensions Contributing Contribute a patch How to install django CMS by hand The easiest way to install for every page) by using the extension models: cms.extensions.PageExtension and cms.extensions.TitleExtension, respectively. Title vs Page extensions The difference between a page extension and a title extension example The model To add a field to the Page model, create a class that inherits from cms.extensions.PageExtension. Your class should live in one of your applications’ models.py (or module). Note