Introduction
Description
This package will add links on Images to edit them on external webservices. It works for:
Archetypes image fields
ATImages
The activation of those services is controlled by settings in a specific control panel on the plone site setup.
Currently, we support only pixlr, fotoflexer and aviary.
You can view a Demo.
Note that we integrate plone.protect to ensure a minimum level of security against CSRF attacks.
Credits
Companies
Contributors
Repository
collective.externalimageeditor Installation
To install collective.externalimageeditor into the global Python environment (or a workingenv), using a traditional Zope 2 instance, you can do this:
When you’re reading this you have probably already run
``easy_install collective.externalimageeditor``.Find out how to install setuptools (and EasyInstall) here: http://peak.telecommunity.com/DevCenter/EasyInstall
If you are using Zope 2.9 (not 2.10), get pythonproducts and install it via:
python setup.py install --home /path/to/instanceinto your Zope instance.
Create a file called collective.externalimageeditor-configure.zcml in the /path/to/instance/etc/package-includes directory. The file should only contain this:
<include package="collective.externalimageeditor" />
Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this:
Add collective.externalimageeditor to the list of eggs to install, e.g.:
[buildout] ... eggs = ... collective.externalimageeditorTell the plone.recipe.zope2instance recipe to install a ZCML slug:
[instance] recipe = plone.recipe.zope2instance ... zcml = collective.externalimageeditorRe-run buildout, e.g. with:
$ ./bin/buildout
You can skip the ZCML slug if you are going to explicitly include the package from another package’s configure.zcml file.
Changelog
1.6 (2012-02-13)
1.5 (2012-02-09)
Remove dexterity useless dependency [kiorky]
Integrate aviary and fotoflexer [kiorky]
Integrate plone.protect [kiorky]
Add support for archetypes image fields [kiorky]
1.0 (2012-02-01)
Initial release [kiorky]
Metadata
Release files for collective.externalimageeditor 1.6
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.externalimageeditor-1.6.zip | 162.2 kB | Without provenance | Details for collective.externalimageeditor-1.6.zip |
Release files / collective.externalimageeditor-1.6.zip
| Download URL | collective.externalimageeditor-1.6.zip |
|---|---|
| Size | 162.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c67d94d9295753362e61db1cbc24ba00cdf3e46bd9afbd3547a371bca4ae7fe0
|
|
BLAKE2b-256 checksum How to use checksums |
004547bfe7c809b423f5cb92a02b3dc280a2107e1d9287ec5a9fba3a36d862e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.externalimageeditor 1.6
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.