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


Release history Release notifications

This version
History Node

0.5

History Node

0.4

History Node

0.3

History Node

0.1

Download files

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

Filename, size & hash SHA256 hash help File type Python version Upload date
collective.contentrules.linguatarget-0.5.zip (14.9 kB) Copy SHA256 hash SHA256 Source None Sep 17, 2012

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging CloudAMQP CloudAMQP RabbitMQ AWS AWS Cloud computing Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page