Skip to main content

collective.base64imagepatch

The current package collective.base64imagepatch is an add on for the CMS Plone. It injects eventhandlers for Contenttype creation and modification to assure that no inline base64 encoded image is stored in an RichTextField.

collective.base64imagepatch Installation

Dependencies

There are two soft dependencies on the underlaying Content-Types-Frameworks of Plone:

  • Archetypes

  • Dexterity

None of those must be included seperately in the buildout, as they are already part of Plone.

Installation via zc.buildout

If you are using zc.buildout to manage your Zope/Plone Instances, you can do this:

  • Add collective.base64imagepatch to the list of eggs to install, e.g.:

[buildout]
...
eggs =
    ...
    collective.base64imagepatch
    ...
  • Re-run buildout, e.g. with:

$ ./bin/buildout

The patch is installed and works directly on next startup.

Note: The patch will not show up in any install listing.

To run the patch on existing content call patch_all view on any Plone object for just this Plone Site Instance or any Zope Root Object for all Plone Sites. cmf.ManagePortal Permissions required.

Credits

  • Contributers:

  • Alexander Loechel

  • Maurits van Rees

Changelog

0.13 (2021-04-28)

  • When adding image fails, try the parent container once. [maurits]

  • Fixed patch_all to run patch on objects, not brains. [maurits]

  • BeautifulSoup: always use lxml. [maurits]

  • Fixed for Dexterity on Plone 4.3. [maurits]

0.12 (2013-11-05)

  • update patch_all to fix errors on patch_all view where String Formating has failed due to syntax errors

0.11 (2013-07-04)

  • updated setup.py for Homepage and fixed History

  • updated setup.py so that beautifulsoup4 is a dependency that is installed

  • remove soft dependency for BeautifulSoup 3 and usage as beautifulsoup4 could be used in parallel

  • refactor beautifulsoup calls so that it works with all versions of beautifulsoup4 (checked with 4.0.1 4.1.0 4.1.3 4.2.0 4.2.1)

0.10 (2013-07-02)

  • Fixed getSite import and interface for zcml dependency on Plone 4.3

0.9 (2013-06-25)

  • Initial release

Metadata

Release files for collective.base64imagepatch 0.13

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for collective.base64imagepatch 0.13
File Size Uploaded Provenance
collective.base64imagepatch-0.13.tar.gz 15.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for collective.base64imagepatch 0.13
File Interpreter ABI Platform
collective.base64imagepatch-0.13-py2.py3-none-any.whl Python 3, Python 2 none any Details

Total release size: 25.2 kB

Release files / collective.base64imagepatch-0.13.tar.gz

Download URL collective.base64imagepatch-0.13.tar.gz
Size 15.2 kB
Tags Source
SHA-256 checksum
How to use checksums
6d91f55b66a62b4feeeab9170cc8c69b36df8173becdfe35825f00952446b8a8
BLAKE2b-256 checksum
How to use checksums
5fd03822daa11ed34b7e09d88972e62dad3f5a9cd9114eb3e05950cd1982f084
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/42.0.2 requests-toolbelt/0.8.0 tqdm/4.19.6 CPython/2.7.17

Release files / collective.base64imagepatch-0.13-py2.py3-none-any.whl

Download URL collective.base64imagepatch-0.13-py2.py3-none-any.whl
Size 10.0 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
835de1a5c67cee331f2817f467f82f51ab8c72b311b1f34553af171284aac29b
BLAKE2b-256 checksum
How to use checksums
239781eed9cbe5bc226cf353f9e298b33781d1d2408ddc3896221b2540ef94ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/42.0.2 requests-toolbelt/0.8.0 tqdm/4.19.6 CPython/2.7.17

Security for collective.base64imagepatch 0.13

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page