Introduction
This product contains a set of portlets aimed at blogging, but useable also for other situtations.
It requires Plone 4.
The development of collective.blog.portlets was sponsored by the Bergen Public Library - http://www.nettbiblioteket.no
Portlets
The portlets so far is:
Monthly archive portlet: A portlet that shows a monthly archive view of all content in a folder with number of items per month and a customizable link to an archive view.
Last posts portlet: Lists the last X documents (sorted by effective date).
Installation is done in the usual manner: Add collective.blog.portlets to your buildout, and install through QuickInstaller or portal_setup. You can then add portlets in the usual manner.
Settings
collective.blog.view has only one settings, locate in portal_properties.site_properties.
blog_types: This lines property will be used to contain the portal_types that are considered entries in the blog. If it does not exist, it will default to Document, News Item and File.
This product will never use doctests to test anything besides documentation.
Changelog
1.6 (2014-04-18)
Added a depth setting for the Archive portlet, so you can have subfolders. [regebro]
1.5 (2013-10-19)
Fixed bugs which came around after install PloneHotFix20130618. [erral, reebalasz]
Added Dutch translations. [jladage]
This version has been tested with Plone 4.1.6, 4.2.6 and 4.3.2.
1.4 (2013-05-27)
Updated Spanish translation [macagua]
Added improvements about i18n [macagua]
Don’t require cmf.ManagePortal to add and edit portlets [erral]
Update translations files [erral]
Add portlet header field [erral]
Merged zedr-plone4.1 branch: includes i18n work and conversion of i18n folder into locales folder [erral]
Merged erral-portlet-improvements branch: it adds an option to show the dates in reversed order and reuses Plone i18n machinery for month names [erral]
Added French translation. [sdemagny]
Added Portugese translaton [lccruz]
Updated Italian translation [cekk]
This version has been tested with Plone 4.0.10, 4.1.6, 4.2.5 and 4.3.
1.3 (2012-04-17)
Sort months in archive properly. [jbaldivieso]
Spanish and Basque translations. [erral]
This version tested with Plone 4.0.10, 4.1.4 and 4.2b2.
1.2 (2010-06-30)
The virtual hosting fix broke something else. Fixed that too. [regebro]
Changed “Oppføringer” to “Innlegg” in the norwegian translation. [regebro]
This version has been tested with Plone 3.3.4 and Plone 4.0b3.
1.1 (2010-06-30)
The url to the archive view didn’t work under virtual hosting. [regebro]
The portlets now also filter on content types. [regebro]
This version has been tested with Plone 3.3.4 and Plone 4.0b3.
1.0 (2010-06-05)
Initial release
This version has been tested with Plone 3.3.4 and Plone 4.0b3.
Metadata
Release files for collective.blog.portlets 1.6
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 |
|---|---|---|---|---|
| collective.blog.portlets-1.6.zip | 47.4 kB | Without provenance | Details for collective.blog.portlets-1.6.zip |
Release files / collective.blog.portlets-1.6.zip
| Download URL | collective.blog.portlets-1.6.zip |
|---|---|
| Size | 47.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5f7ec2c15edfae2787bb9d1ad6c1d9fd2300dca6f02feae6c12ce178b2aa94f
|
|
BLAKE2b-256 checksum How to use checksums |
9c9f4347a3dbe176e8d68c5807f65a4578766651861c9250840fbee95f803ca9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.blog.portlets 1.6
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.