Introduction
This is a Django CMS plugin for incorporating photologue galleries.
Installation
First, you must install Django CMS and photologue which require Django and a few other libraries such as PIL. For full details, see the installation instructions for those packages.
Install cmsplugin-phlog to your environment with a tool such as PIP, setuptools, or buildout.
Add cmsplugin_phlog to the INSTALLED_APPS list in your project’s settings.py and run the syncdb command on your manage.py.
What’s Inside
In order to facilitate ordering of the galleries on display, there is a new photologue gallery with ordering support called OrderedGallery. This model can be linked using a CMS plugin to display photos on your page.
The default rendering of the gallery plugin is an unordered list of images. This can be overridden by placing a template in your project’s template folder at cms/plugins/phlog/gallery.html to override all rendering or at cms/plugins/phloge/{{ placeholder }}-gallery.html to override the template for a single placeholder (by name).
0.3.1 (2013/06/26)
Added proper ordering to gallery rendering
0.3 (2013/06/07)
Added copy relations to plugin for CMS publishing support
Fixed JS locations
Some upgrades and added some logging
0.2.4.2 (2013/04/08)
Repackage to get static files and templates
0.2.4.1 (2013/03/14)
Fixed an import error
Fixed a typo bug
0.2.4 (2013/03/13)
Updated to use static files app
Updated widget for new statics
0.2.3 (2012/01/11)
Added width and height attributes to Phlog Galleries
0.2.2 (2011/12/01)
Fixed a bug when a phlog photo plugin is added without a photo
0.2.1 (2011/10/14)
Fixed a bug with the rendered order of Phlog Galleries
0.2 (2011/08/04)
Deprecated 0.1 gallery
Added a gallery plugin that allows for other plugins to be added as items in the gallery
Added a Photo plugin for adding photologue photos to a page (and not the site wide photo manager)
Added South integration
0.1 (2011/05/11)
Ordered Photologue gallery added
CMS Plugin for ordered photologue gallery added
Admin configuration of new ordered gallery
1 maintainer
Metadata
1 maintainer
Release files for cmsplugin-phlog 0.3.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 |
|---|---|---|---|---|
| cmsplugin-phlog-0.3.1.tar.gz | 17.6 kB | Without provenance | Details for cmsplugin-phlog-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cmsplugin_phlog-0.3.1-py2.7.egg | Legacy Egg format | - | - | Details for cmsplugin_phlog-0.3.1-py2.7.egg |
Total release size: 59.8 kB
Release files / cmsplugin-phlog-0.3.1.tar.gz
| Download URL | cmsplugin-phlog-0.3.1.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ebc9d5b964bc5c08a00a8bc96e6b83d399a4dca51cd872e5741bd5b393bf445
|
|
BLAKE2b-256 checksum How to use checksums |
82768002d7d76d2acb2d933657c58c32353be5eecb34e253adaaf2e6962c25fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / cmsplugin_phlog-0.3.1-py2.7.egg
| Download URL | cmsplugin_phlog-0.3.1-py2.7.egg |
|---|---|
| Size | 42.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
0f565b861b330df22ad15ef845276fe9a0e1c645d28e67cc15481844e3017eef
|
|
BLAKE2b-256 checksum How to use checksums |
0bb29c30ef0b216639fba6ecadfbb8762c771893bce93403f4145d136c54e4a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cmsplugin-phlog 0.3.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.
