collective.base64imagepatch 0.10

collective.base64imagepatch Installation

Dependencies

There is a hard dependency for one of these BeautifulSoup packages: * beautifulsoup4 (new version) * BeautifulSoup (old depricated version, but usable if already installed or beautifulsoup4 would cause any version conflicts) One of those both packages have to be installed. As zc.buildout did not allow optional requires statements you have to include it into your dependency-list

There are two soft dependencies on the underlaying Content-Types-Frameworks of Plone. * Archetypes * Dexterity None of those must be included seperatly 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
    beautifulsoup4 or BeautifulSoup
    ...

• 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 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.

0.10 (unreleased)

• Nothing changed yet.

0.9 (2013-06-25)

• Initial release