This release is a pre-release and may not be stable for production use.
Introduction
Provide the DexterityCompoundDiff diff type for Products.CMFDiffTool, analogous to ATCompoudDiff.
This is a package to help enable content versioning for Dexterity content types. To enable versioning for a Dexterity content type you need to:
Install plone.app.versioningbehavior and use it on your content type.
Enable versioning for the type in the types control panel.
Install this package.
Go to the portal_diff tool ZMI page.
Add Compound Diff for Dexterity types for your content type. Field name can be anything, e.g: “any”.
You can enable versioning on Dexterity content types without this package, but then you’ll have to add the correct “diff type” for each field of your content type.
Changelog
0.1b4 (2012-03-07)
Added ChoiceDiff.
0.1b3 (2012-03-06)
Added BoolDiff.
0.1b2 (2012-02-22)
Provide inline diff for date, time and datetime fields.
Provide inline diff for file and lists of files fields.
Sort fields taking into account plone.directives.form` ordering directives.
0.1b1 (2011-07-12)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.dexteritydiff 0.1b4
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 | |
|---|---|---|---|---|
| collective.dexteritydiff-0.1b4.tar.gz | 10.4 kB | Without provenance | Details |
Release files / collective.dexteritydiff-0.1b4.tar.gz
| Download URL | collective.dexteritydiff-0.1b4.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b45a40e1423f0fa572a45380d47cac30fb5082f4d2c18167869e8fd5af0d3df0
|
|
BLAKE2b-256 checksum How to use checksums |
534316bb8e3e76a81146eedc03864f1e6e57c3303e36ae460919f1201d0de2aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.dexteritydiff 0.1b4
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.
