Skip to main content

A Plone content rules action that creates a chronological archive.

Project description

sc.contentrules.groupbydate

Overview

sc.contentrules.groupbydate is a very basic content rule action used to organize content under a chronological-based hierarchy on a web site upon publication.

Base use case

A news portal with a few dozen new content items per day needs to organize its information in a chronological, yet human-readable, hierarchy.

To do so this package is installed in a Plone Site and a new content rule is created. This content rule will be triggered by the publication of an News Item and will initialize a ‘’’Move an item to a date-based folder structure’’’.

This action has a target (/news) and a structure (‘ymd’), so as our News Item, with id hello-world, is published on the site, it will be moved to a a new folder structure under /news. Supposing it’s December 19th, 2008, the item will end in /news/2009/12/19/hello-world.

Requirements

Installation

To enable this product,on a buildout based installation:

  1. Edit your buildout.cfg and add sc.contentrules.groupbydate to the list of eggs to install

    [buildout]
    ...
    eggs =
        sc.contentrules.groupbydate
  2. Tell the plone.recipe.zope2instance recipe to install a ZCML slug:

    [instance]
    ...
    zcml =
        ...
        sc.contentrules.groupbydate

If another package depends on the sc.contentrules.groupbydate egg or includes its zcml directly you do not need to specify anything in the buildout configuration: buildout will detect this automatically.

After updating the configuration you need to run the ‘’bin/buildout’’, which will take care of updating your system.

Sponsoring

Development of this product was sponsored by Simples Consultoria.

Credits

  • Erico Andrei (erico at simplesconsultoria dot com dot br)

Changelog

trunk (unreleased)

  • Allow relative paths as base_folder [erico_andrei]

  • Allow inputing of strftime formatting for structure field [erico_andrei]

  • Add dependency of placeful workflow as we need it to avoid publishing content in an unpublished structure [erico_andrei]

0.5 (2009-07-28)

  • Very earlier i18n support [erico_andrei]

  • Initial release

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

sc.contentrules.groupbydate-1.0.tar.gz (19.3 kB view details)

Uploaded Source

Built Distribution

sc.contentrules.groupbydate-1.0-py2.4.egg (38.1 kB view details)

Uploaded Source

File details

Details for the file sc.contentrules.groupbydate-1.0.tar.gz.

File metadata

File hashes

Hashes for sc.contentrules.groupbydate-1.0.tar.gz
Algorithm Hash digest
SHA256 674859cebbbdf25dd65f7b06df6d8df2e14f420995ad544d29d6e6afd8ea5ada
MD5 68d71868dfdb7704b228e81c4f89908c
BLAKE2b-256 12d444dc677ffd6b2b0903770d13225fc42b47750c9973846cab5b11ea1ec674

See more details on using hashes here.

File details

Details for the file sc.contentrules.groupbydate-1.0-py2.4.egg.

File metadata

File hashes

Hashes for sc.contentrules.groupbydate-1.0-py2.4.egg
Algorithm Hash digest
SHA256 e8e5630e53ba713f0d67b11c9f7f52aa6b802ba12f3fb33bb04dae8467dba352
MD5 f2ee929755c904943196d49b96a49d8c
BLAKE2b-256 4c7b9e2a2b7dc13f27d00154ee6facfa2d2c7364545c4ac497cbb910ad422f66

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page