This release is a pre-release and may not be stable for production use.
Introduction
This addon is integration of different Plone addons to provide a Blog Solution.
Dependencies
collective.wpadmin
collective.contentrules.yearmonth
collective.recaptcha
plone.formwidget.recaptcha
collective.configviews
How to use
You just have to add a folder in your website and call the @@cirb_blog_setup view to turn this folder into a blog.
Next you have to configure your collection query:
criteria: content type: Blog Entry
criteria: review state: published
sort on: effective date (reverse)
Credits
Companies
People
JeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>
Changelog
1.0a3 (2013-01-18)
fix get_localized_time issue when datetime is None (effective date)
remove collective.configviews from dependencies
Use archive-root-path-to-blog as rule id during the rule creation. Fix issue if you have multiple blog with same id. This can be the case if you use LinguaPlone with languages folder (/fr, /nl, …)
1.0a2 (2013-01-17)
fix setup view content rule creation (issue was on the target_root_folder)
1.0a1 (2013-01-16)
Initial release
Metadata
Release files for cirb.blog 1.0a3
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 |
|---|---|---|---|---|
| cirb.blog-1.0a3.zip | 70.2 kB | Without provenance | Details for cirb.blog-1.0a3.zip |
Release files / cirb.blog-1.0a3.zip
| Download URL | cirb.blog-1.0a3.zip |
|---|---|
| Size | 70.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4238f3f651e6b473e73717530d8bfb9e7f0ab8eec5dbdf418b8ddac14156267
|
|
BLAKE2b-256 checksum How to use checksums |
dacf9a93faaa9c756e4f675c1ee326d7b0acb9d91722a272566e93f95b3e9628
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cirb.blog 1.0a3
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.