Note: This package has been refactored.. The content types in this package will be a part of Products.MegamanicEditContentTypes. If you pin GrailTact and MegamanicEdit to 1.4.1 in the buildout they should continue working well if you have existing content. If you want to upgrade you’ll need to write a migration between GrailTact’s content types and Products.MegamanicEditContentTypes.
A complete contact system, supporting the most popular standards and services. To add to your Plone instance, add the following to the buildout configuration:
- zcml =
GrailTact.GrailTact
- eggs =
Plone GrailTact
And install GrailTact, MegamanicEdit and VariousDisplayWidgets through the Plone control panel.
1.4.1
Added dependencies
Metadata
Release files for GrailTact 1.4.1
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 |
|---|---|---|---|---|
| GrailTact-1.4.1.tar.gz | 20.5 kB | Without provenance | Details for GrailTact-1.4.1.tar.gz |
Release files / GrailTact-1.4.1.tar.gz
| Download URL | GrailTact-1.4.1.tar.gz |
|---|---|
| Size | 20.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec2fdc6055d2cf17344ec386367e9466645fa463c706e5b147b99884038a2bd3
|
|
BLAKE2b-256 checksum How to use checksums |
72ef8eee8e94b1105d8fad63921d4d7d3ef2b40adb0eaaae4d37c340341862d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for GrailTact 1.4.1
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.