Introduction
When copying and pasting an object in Plone the workflow state of the newly pasted object is set to the initial state. Sometimes you want to keep the original state. This is what zest.specialpaste does.
Use case
You use Plone to store some information about clients in a folder. You have created a standard folder with a few sub folders and several documents, images and files that you use as a template for new clients. For new clients some of these objects should already be published. You have set this up correctly in the template or sample folder. You copy this folder, go to a new location and use the ‘Special paste’ action from zest.specialpaste to paste the objects and let the review state of the new objects be the same as their originals.
Compatibility
Tested on Plone 4.0 and 4.1. Currently it does not work on Plone 3.3; that surprises me, so it might be fixable.
Installation
Add zest.specialpaste to the eggs of your buildout (and to the zcml too if you are on Plone 3.2 or earlier, but it does not work there currently). Rerun the buildout.
Install Zest Special Paste in the Add-on Products control panel. This adds a ‘Special paste’ action on objects and registers a browser layer that makes our @@special-paste browser view available.
Future ideas
We can add a form in between where you can specify what should be special for the paste. When selecting no options it should do the same as the standard paste action.
Allow keeping the original owner.
Take over local roles.
Make compatible with Plone 3.3 as well.
Changelog
1.2 (2011-11-04)
Do less logging as this can be overly verbose or warn about things that in practice occur for very normal reasons. [maurits]
Fix paste error when copying a folder that has a sub folder that has content. [maurits]
1.1 (2011-11-02)
Added MANIFEST.in file so .mo files are included when run with zest.releaser. [maurits]
1.0 (2011-11-02)
Initial release
4 maintainers
Metadata
4 maintainers
Release files for zest.specialpaste 1.2
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 |
|---|---|---|---|---|
| zest.specialpaste-1.2.zip | 32.3 kB | Without provenance | Details for zest.specialpaste-1.2.zip |
Release files / zest.specialpaste-1.2.zip
| Download URL | zest.specialpaste-1.2.zip |
|---|---|
| Size | 32.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b55c97c3dcc1a8531913b08b960df3d6db228a5e928449a2e566515039216fa
|
|
BLAKE2b-256 checksum How to use checksums |
0450c07a60450dfc6642b56ec45a3c812e7a7eb9a4a30dded20ff2b3acd69ee6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zest.specialpaste 1.2
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.
