django-cms-themes
=================
A django app that lets you load theme packs that are bundled templates, and
select which theme a site should use.
Dependencies
============
- django (tested with 1.3)
- django-cms (tested with 2.2)
Getting Started
=============
To get started simply install using ``pip``:
::
pip install django-cms-themes
Add ``'cms_themes',`` to your installed apps and ``syncdb`` (or migrate, if
you have south installed).
Your installed apps should look something like this:
::
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.admin',
'cms',
'cms_themes',
)
Per the django-cms quickstart guide, you should have a setting in your
settings file called PROJECT_PATH that points to the root of your project, i.e.
``PROJECT_PATH = os.path.abspath(os.path.dirname(__file__))``
If not, it will be assumed that your themes will live just beneath the ``MEDIA_ROOT``.
Usage
=============
All usage is done through the admin.
Simply create a new Theme record and upload a theme tarball (tar.gz) file from
http://www.djangocmsthemes.com. All templates from themes uploaded should now
show up in your Templates drop down on a django cms page.
=================
A django app that lets you load theme packs that are bundled templates, and
select which theme a site should use.
Dependencies
============
- django (tested with 1.3)
- django-cms (tested with 2.2)
Getting Started
=============
To get started simply install using ``pip``:
::
pip install django-cms-themes
Add ``'cms_themes',`` to your installed apps and ``syncdb`` (or migrate, if
you have south installed).
Your installed apps should look something like this:
::
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.admin',
'cms',
'cms_themes',
)
Per the django-cms quickstart guide, you should have a setting in your
settings file called PROJECT_PATH that points to the root of your project, i.e.
``PROJECT_PATH = os.path.abspath(os.path.dirname(__file__))``
If not, it will be assumed that your themes will live just beneath the ``MEDIA_ROOT``.
Usage
=============
All usage is done through the admin.
Simply create a new Theme record and upload a theme tarball (tar.gz) file from
http://www.djangocmsthemes.com. All templates from themes uploaded should now
show up in your Templates drop down on a django cms page.
Metadata
Release files for django-cms-themes 1.0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-cms-themes-1.0.11.tar.gz | 8.0 kB | Without provenance | Details |
Release files / django-cms-themes-1.0.11.tar.gz
| Download URL | django-cms-themes-1.0.11.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3196e1f9a52d546e06a2b12abdf9b258ce23318c06d7ee0b1205a87f6ddd649f
|
|
BLAKE2b-256 checksum How to use checksums |
0c9f8a59523b55717263721abf5688803868bd821337fa081549af21c9e7cef4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-cms-themes 1.0.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.