TakeAction, content as actions
Introduction
This is a simple tool that provides specific content as actions. Simply put the paths in the content_paths field (absolute or relative to the portal), give the action a category, and use the actions anywhere in your skin.
As an added bonus, translatable content (such as LinguaPlone content), will automatically result in translated actions pointing at the correct translation.
Installation
Choose the ‘takeaction’ profile in the portal_setup tool, and import.
License
GNU GPL, see LICENSE.txt
Credits
TakeAction was developed by Jarn for Mnemonic, March 2007
- Design and development::
Jarn (Martijn Pieters)
Changelog for takeaction
1.0 (2011-02-16)
Updated to support Plone 4.0 [mj]
0.4 (2008-11-05)
Converted takeaction to an egg in the Products namespace. [mj]
0.3 (2007-08-22)
Use the (original) object id in the action id to make CSS styling easier and more predictable. Make sure the ids remain unique. [fschulze, mj]
0.2 (2007-04-03)
Deal with missing translations; return the language neutral version if available, otherwise skip the item altogether [wichert, mj]
0.1 (2007-03-29)
Initial release [mj]
Release files for Products.takeaction 1.0
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 |
|---|---|---|---|---|
| Products.takeaction-1.0.zip | 33.6 kB | Without provenance | Details for Products.takeaction-1.0.zip |
Release files / Products.takeaction-1.0.zip
| Download URL | Products.takeaction-1.0.zip |
|---|---|
| Size | 33.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
daf3486e695c1f81b7fb1a14c31635c8fd2d7ae44505f3f3bd151b7d3cc50e9a
|
|
BLAKE2b-256 checksum How to use checksums |
627e9c8b447788f69f96b6479a7411cae27ba23663b205a6c286739b774de7b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.takeaction 1.0
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.
