Introduction
Provides external methods to sync and create content from Adlib API
Features
Creates Object content type in a Plone site based on Adlib API data.
Synchronization of content from Adlib API with a Plone site.
Installation
If you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this: Add collective.adlibsyncmanager to the list of eggs to install, e.g.:
[buildout]
…
eggs =
…
collective.adlibsyncmanager
How to use method as a cron job?
Add to your buildout.cfg:
zope-conf-additional =
<clock-server>
method /SiteName/adlib_sync
period 60
user username-to-invoke-method-with
password password-for-user
host localhost
</clock-server>
Dependencies
collective.object
The following dependencies are not required unless the creation of pictures and translations is requested.
plone.namedfile
plone.app.multilingual
Todos
Get deleted records from API and update content
Create log document with every request result details
Send email after several failed API request attempts
Changelog
0.1 (2014-11-14)
Initial release
Metadata
Release files for collective.adlibsyncmanager 0.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 |
|---|---|---|---|---|
| collective.adlibsyncmanager-0.1.tar.gz | 23.6 kB | Without provenance | Details for collective.adlibsyncmanager-0.1.tar.gz |
Release files / collective.adlibsyncmanager-0.1.tar.gz
| Download URL | collective.adlibsyncmanager-0.1.tar.gz |
|---|---|
| Size | 23.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ead58c29cbe74e69152cb2d8bab9b08c8a51835c69e833add4cd7de0a63d0cb0
|
|
BLAKE2b-256 checksum How to use checksums |
ae4fbd5618e52b20607e18f2878d9dcb21f6452c697520fdcd506b0a20194e35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.adlibsyncmanager 0.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.