Integrate django CMS with Oscar
djangocms-oscar eases integration between the content management system django CMS and the e-commerce framework Oscar.
It is in an early stage, so use at your own risk.
Features
base.html template which means that the django CMS toolbar works both on CMS pages and Oscar views
Ships with default CMS templates that share the look with Oscar’s sandbox pages
Oscar’s “Browse store” dropdown includes CMS pages
A “Featured product” CMS plugin to be able to add individual products on CMS pages
Tested with
django-cms 3.0.2
django-oscar >=0.7.1, <0.8
Django 1.5.8
Python 2.7
NOTE: Currently, django CMS does not play well with the new @atomic decorator introduced in Django 1.6. Use django CMS from the master branch, or wait for the next release.
Installation
Grabbing the integration
The latest release will be on PyPi, so you can just pip install djangocms-oscar. Or grab it from the master branch if you prefer the bleeding edge.
Adding django CMS to an Oscar project
If you have a working Oscar project and want to add django CMS, follow the instructions on integrating django CMS.
You should also add at least one plugin to be able to set content. This probably want to add djangocms-text-ckeditor to be able to include text.
Adding Oscar to a django CMS project
If you have a working django CMS project and want to integrate Oscar, follow the instructions on getting started with Oscar.
URLs
There’s two options to include Oscar’s URLs.
This integration comes with an app hook for django CMS. So you can just let django CMS take care of URL handling by adding Oscar to a CMS page.
If you prefer to hard-wire Oscar’s URLs into your project’s urls.py, make sure that django CMS’s URLs come after Oscar’s.urls:
urlplatterns = [
...
(r'^shop/', include(shop.urls)),
(r'^', include('cms.urls')),
...
]
Setting up the integration
To get started using djangocms-oscar:
install it with pip:
$ pip install djangocms-oscar
add the plugins to INSTALLED_APPS:
INSTALLED_APPS = ( ... 'djangocms_oscar', ... )To use the supplied templates, they need to be loaded before Oscar’s:
from oscar import OSCAR_MAIN_TEMPLATE_DIR from djangocms_oscar import OSCAR_CMS_TEMPLATE_DIR TEMPLATE_DIRS = ( location('templates'), OSCAR_CMS_TEMPLATE_DIR, OSCAR_MAIN_TEMPLATE_DIR, )Run syncdb or migrate if you’re using South.
Optional settings
Besides customised Oscar templates, djangocms-oscar comes with a set of CMS templates that are based on Oscar’s default templates. They’re a good starting point and can be used like this:
# settings.py
CMS_TEMPLATES = (
('djangocms_oscar/full_width.html', 'Full width (no sidebars)'),
('djangocms_oscar/with_sidebar.html', 'Two column (left-hand sidebar)'),
)
If you want Oscar’s homepage to be controlled by django CMS, set it like this:
# settings.py
from django.core.urlresolvers import reverse_lazy
OSCAR_HOMEPAGE = reverse_lazy('pages-root')
Metadata
Release files for djangocms-oscar 0.1
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 | Actions |
|---|---|---|---|---|
| djangocms-oscar-0.1.tar.gz | 6.4 kB | Without provenance | Details for djangocms-oscar-0.1.tar.gz |
Release files / djangocms-oscar-0.1.tar.gz
| Download URL | djangocms-oscar-0.1.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4eaffa8d7cae02a284ff3ee67bad5b59e738868d421c5466e10184810e38dfde
|
|
BLAKE2b-256 checksum How to use checksums |
2fcca7655771714161cdedcb4976d067e04d78a2487121ebe25d8a0e0a563b27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for djangocms-oscar 0.1
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.