Introduction
This product integrates Products.sqlpfgadapter into collective.megaphone.
For now, all it does is add “SQLPFGAdapter” to the addable types in a “Megaphone Action” (megaphone 2) or “Action Letter” (megaphone < 2).
In the future, the sql storage might be a step in the megaphone wizard, which this product could provide.
Compatibility
Requires Products.sqlpfgadapter >= 0.1a2.
Should work on Plone 3 and Plone 4, collective.megaphone 1.x and 2.x.
Tested on Plone 3.3.5 with collective.megaphone 2.0b1 and Products.sqlpfgadapter 0.1a2.
Changelog
1.0 (2011-01-10)
No functional change
0.1a1 (2010-09-22)
Initial release
Metadata
Release files for collective.megaphonesql 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 |
|---|---|---|---|---|
| collective.megaphonesql-1.0.tar.gz | 10.8 kB | Without provenance | Details for collective.megaphonesql-1.0.tar.gz |
Release files / collective.megaphonesql-1.0.tar.gz
| Download URL | collective.megaphonesql-1.0.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c3837dbc505cd1137e52b23a0a6b7920b4198a30693f67d3029dbb068943f19
|
|
BLAKE2b-256 checksum How to use checksums |
530f3aed2403527242217bc60c584a4c832fa87b313df4e65423480ba03b9d78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.megaphonesql 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.