again. To add a Text or or other plugin elements to a placeholder: 1. switch to Structure mode 2. select the menu icon on the placeholder’s title bar 3. select a plugin type to add 10 Chapter 5. Table of standard polls app in our project. But we’ve not done anything django CMS specific yet. Creating a plugin If you’ve played around with the CMS for a little, you’ve probably already encountered CMS Plugins the project root called polls_plugin: python manage.py startapp polls_plugin So our workspace looks like this: env/ src/ # the django polls application is in here polls_plugin/ # the newly-created application

we’re ready to use it to being integrating Polls with django CMS. We’ll start by developing a Polls plugin. Note The project or the application? Earlier, we added new templates to the project. We could a separate package, a Polls/CMS Integration application in our project. Note Why not build the plugin code into the polls application package? This would certainly be possible, and in fact, if you were application it’s what we would recommend. For a third-party application such as Polls however, placing the plugin code into a separate package means we don’t have to modify or fork the original. Create a new package

and Content mode, add plugins, move them around and delete them again. To add a Text or or other plugin elements to a placeholder: 1. switch to Structure mode 10 Chapter 5. Table of contents django Documentation, Release 3.1.8.dev1 2. select the menu icon on the placeholder’s title bar 3. select a plugin type to add 5.1.2 Templates & Placeholders In this tutorial we’ll introduce Placeholders, and we’re standard polls app in our project. But we’ve not done anything django CMS specific yet. Creating a plugin If you’ve played around with the CMS for a little, you’ve probably already encountered CMS Plugins

Templatetags 3.3. Toolbar Templatetags 4. Command Line Interface 4.1. Informational commands 4.2. Plugin and apphook management commands 4.3. Moderation commands 4.4. MPTT repair command 5. Permissions Examples 1.1. My First Plugin 1.2. My First App (apphook) 1.3. My First Menu 2. Custom Plugins 2.1. Why would you need to write a plugin? 2.2. Overview 2.3. The simplest plugin 2.4. Troubleshooting 2.5 Navigation Modifiers 3.5. Custom Plugins 4. API References 4.1. cms.api 4.2. cms.constants 4.3. cms.plugin_base 4.4. menus.base 5. Placeholders outside the CMS 5.1. Quickstart 5.2. Adding content to a placeholder

CMS: Examples 1.1. My First Plugin 1.2. My First App (apphook) 1.3. My First Menu 2. Custom Plugins 2.1. Writing a custom plugin 2.2. Plugin Context Processors 2.3. Plugin Processors modules | index next Attach Menus 3.3. App-Hooks 3.4. Navigation Modifiers 3.5. Custom Plugins 4. API References 4.1. cms.plugin_base 4.2. menus.base 5. Placeholders outside the CMS 5.1. Quickstart 5.2. Adding content to a placeholder like the above) 1.1.3. On Microsoft Windows TODO. 1.2. Databases We recommend using PostgreSQL [http://www.postgresql.org/] or MySQL [http://www.mysql.com] with Django CMS. Installing and maintaining database

Informational commands 4.2. Plugin and apphook management commands 4.3. Moderator commands Extending the CMS 1. Extending the CMS: Examples index modules | next | 1.1. My First Plugin 1.2. My First App (apphook) (apphook) 1.3. My First Menu 2. Custom Plugins 2.1. Why would you need to write a plugin? 2.2. Overview 2.3. The simplest plugin 2.4. Storing configuration 2.5. Advanced 3. App Integration 3.1. Menus 3.2 App-Hooks 3.4. Navigation Modifiers 3.5. Custom Plugins 4. API References 4.1. cms.api 4.2. cms.plugin_base 4.3. menus.base 5. Placeholders outside the CMS 5.1. Quickstart 5.2. Adding content to a placeholder

recommended packages Pillow==2.0.0 django-filer==0.9.4 cmsplugin-filer==0.9.5 django-reversion==1.7 for Postgresql you would also add: psycopg2==2.5 and install libpq-dev (on Debian-based distro) for MySQL you that is needed for you to follow the Introductory Tutorial. 1.1.4 Databases We recommend using PostgreSQL or MySQL with django CMS. Installing and maintaining database systems is outside the scope of this MultiColumn Plugin. The possibilities for this are endless. Imagine: StylePlugin, 1.3. 2.4 release notes 9 django cms Documentation, Release 2.4.3-support TablePlugin, GalleryPlugin etc. The column plugin can

special extensions like hstore [http://peewee.readthedocs.org/en/latest/peewee/playhouse.html#postgresql-extensions-hstore-ltree] and full-text search [http://peewee.readthedocs.org/en/latest/peewee/playhouse BaseAdapter and its subclasses Playhouse, a collection of addons apsw, an advanced sqlite driver Postgresql Extensions (hstore, ltree) pwiz, a model generator Signal support Sqlite Extensions Swee’pea, syntactic class), otherwise peewee will fall back to a default sqlite database named “peewee.db”. Using with Postgresql Point models at an instance of PostgresqlDatabase. psql_db = peewee.PostgresqlDatabase('my_database'

class), otherwise peewee will fall back to a default sqlite database named “peewee.db”. Using with Postgresql Point models at an instance of PostgresqlDatabase. psql_db = PostgresqlDatabase(’my_database’ ’, user=’code’) class PostgresqlModel(Model): """A base model that will use our Postgresql database""" class Meta: database = psql_db class User(PostgresqlModel): username = CharField() # etc, etc introspection tool “pwiz” that comes with peewee. Usage: python pwiz.py my_postgresql_database It works with postgresql, mysql and sqlite: python pwiz.py test.db --engine=sqlite pwiz will generate

class), otherwise peewee will fall back to a default sqlite database named “peewee.db”. Using with Postgresql Point models at an instance of PostgresqlDatabase. psql_db = peewee.PostgresqlDatabase(’my_database’ tabase’, user=’code’) class PostgresqlModel(peewee.Model): """A base model that will use our Postgresql database""" class Meta: database = psql_db class Blog(PostgresqlModel): creator = peewee.CharField() introspection tool “pwiz” that comes with peewee. Usage: python pwiz.py my_postgresql_database It works with postgresql, mysql and sqlite: python pwiz.py test.db --engine=sqlite pwiz will generate