templates 3.4. Creating your first CMS Page! 4. Using South with django CMS 4.1. Installation 4.2. Basic usage 4.3. More information about South 5. Configuration 5.1. Required Settings 5.2. Basic Customization higher release of 2.x). Django [http://www.djangoproject.com] 1.2.5 (or a 1.3.x release). South [http://south.aeracode.org/] 0.7.2 or higher PIL [http://www.pythonware.com/products/pil/] 1.1.6 or higher When installing the django CMS using pip, Django, django-mptt django-classy- tags, django-sekizai, south and html5lib will be installed automatically. 1.1.1. Recommended django-filer [https://github.c

Creating your first CMS page! 2.4. Troubleshooting 3. Using South with Django-CMS 3.1. Installation 3.2. Basic usage 3.3. More information about South 4. Configuration 4.1. Required Settings 4.2. Basic Customization release of 2.x). Django [http://www.djangoproject.com] 1.2.3 (or a higher release of 1.2). South [http://south.aeracode.org/] 0.7.2 or higher PIL [http://www.pythonware.com/products/pil/] 1.1.6 or higher install python2.6 python-setuptools python-imaging sudo easy_install pip sudo pip install django-cms south django-appmedia Additionally, you need the python driver for your selected database: sudo aptitude

Creating templates 1.4. Creating your first CMS Page! 2. Using South with django CMS 2.1. Installation 2.2. Basic usage 2.3. More information about South 3. Configuration 3.1. Required Settings 3.2. Basic Customization 5 (or a higher release of 2.x). Django [http://www.djangoproject.com] 1.4.5, 1.5 or higher South [http://south.aeracode.org/] 0.7.2 or higher django-classy-tags [https://github.com/ojii/django-classy-tags] When installing the django CMS using pip, Django, django-mptt django-classy- tags, django-sekizai, south and html5lib will be installed automatically. Recommended These packages are not required, but they

library https://python-pillow.github.io/ lxml (>= 3.1.0) http://lxml.de/ South (>= 1.0) (needed for Django 1.6) http://south.aeracode.org/ dateutil http://labix.org/python-dateutil libravatar (optional apt-get: apt-get install python-django translate-toolkit \ python-whoosh python-pil python-django-south python-libravatar \ python-babel Git mercurial python-social-auth # Optional for database backend repository: zypper install python-Django translate-toolkit \ python-Whoosh python-Pillow python-South python-python-social-auth \ python-babel Git mercurial For proper sorting of a unicode strings

library https://python-pillow.github.io/ lxml (>= 3.1.0) http://lxml.de/ South (>= 1.0) (needed for Django 1.6) http://south.aeracode.org/ dateutil http://labix.org/python-dateutil libravatar (optional apt-get: apt-get install python-django translate-toolkit \ python-whoosh python-pil python-django-south python-libravatar \ python-babel Git mercurial python-social-auth # Optional for database backend repository: zypper install python-Django translate-toolkit \ python-Whoosh python-Pillow python-South python-python-social-auth \ python-babel Git mercurial For proper sorting of a unicode strings

library https://python-pillow.github.io/ lxml (>= 3.1.0) http://lxml.de/ South (>= 1.0) (needed for Django < 1.7) http://south.aeracode.org/ dateutil http://labix.org/python-dateutil libravatar (optional apt-get: apt-get install python-django translate-toolkit \ python-whoosh python-pil python-django-south python-libravatar \ python-pyicu python-babel # Optional for database backend apt-get install zypper install python-Django python-icu translate-toolkit \ python-Whoosh python-Pillow python-South python-python-social-auth \ python-babel Requirements on OSX If your python was not installed

different between the two versions. Schema migrations are not affected as the migration systems (both South and Django) detects the different bases. Data migrations are a different story, though. If your data migration will always be executed on the “old” database schema and no conflict will exist. For South migrations add this: from distutils.version import LooseVersion import cms USES_TREEBEARD = LooseVersion(cms critical areas of the code explaining the behaviour appropriate test coverage Python 2/3 compatibility South and Django migrations (where applicable) The pull request description must briefly describe the feature

different between the two versions. Schema migrations are not affected as the migration systems (both South and Django) detects the different bases. Data migrations are a different story, though. If your data migration will always be executed on the “old” database schema and no conflict will exist. For South migrations add this: from distutils.version import LooseVersion import cms USES_TREEBEARD = LooseVersion(cms critical areas of the code explaining the behaviour appropriate test coverage Python 2/3 compatibility South and Django migrations (where applicable) The pull request description must briefly describe the feature

different between the two versions. Schema migrations are not affected as the migration systems (both South and Django) detects the different bases. Data migrations are a different story, though. If your data migration will always be executed on the “old” database schema and no conflict will exist. For South migrations add this: from distutils.version import LooseVersion import cms USES_TREEBEARD = LooseVersion(cms critical areas of the code explaining the behaviour appropriate test coverage Python 2/3 compatibility South and Django migrations (where applicable) The pull request description must briefly describe the feature

different between the two versions. Schema migrations are not affected as the migration systems (both South and Django) detects the different bases. Data migrations are a different story, though. If your data data migration will always be executed on the “old” database schema and no conflict will exist. For South migrations add this: from distutils.version import LooseVersion import cms USES_TREEBEARD = LooseVersion(cms critical areas of the code explaining the behaviour appropriate test coverage Python 2/3 compatibility South and Django migrations (where applicable) The pull request description must briefly describe the feature