Skip to main content

This package adds a custom content rule that takes the target folder's translations into account

Project description

Introduction

The normal Plone ‘move’ and ‘copy’ content rules do not take translations of the specified target folder into account. Instead, all objects, regardless of their language, are moved/copied to the single specified folder.

This product provides two custom Plone Content Rules.

  • LinguaMove

  • LinguaCopy

The purpose of which is to move or copy objects to the correct language version (translation) of the specified target folder.

Changelog

0.5 (2012-09-17)

  • Include CMFCore’s permissions.zcml. [thomasw]

0.4 (2009-10-09)

  • Plone4 compliance

  • Fixed a bug with objects added that have no language set (jcbrand)

0.3 (2009-10-06)

  • Fixed a bug where non-lingua actions also invoke the Lingua Executioner (jcbrand)

  • Use the UberSelectionWidget (jcbrand)

0.1 (unreleased)

  • 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

collective.contentrules.linguatarget-0.5.zip (14.9 kB view details)

Uploaded Source

File details

Details for the file collective.contentrules.linguatarget-0.5.zip.

File metadata

File hashes

Hashes for collective.contentrules.linguatarget-0.5.zip
Algorithm Hash digest
SHA256 9c62e2eedc7e56ef58ab14d033e9b7176854bce4d4ddd16c7b614329bcb488ea
MD5 16b87a32712fdab274b6409f475d61e7
BLAKE2b-256 e1da67434638014f7dad644eec3312c671a3145dcf2ead6d99382a9904dd7f17

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