Override core Plone packages#
Plone includes a few hundred Python packages. Sometimes you will need to override one or more package versions to fix a bug.
Buildout#
Use the following instructions if you installed Plone with Buildout.
Override a core Plone package#
Update the file buildout.cfg
.
This example uses plone.api
.
[buildout]
extends =
https://dist.plone.org/release/6-latest/versions.cfg
parts =
instance
[instance]
recipe = plone.recipe.zope2instance
user = admin:admin
http-address = 8080
eggs =
Plone
[versions]
plone.api = 2.0.0a3
Note
The version pins specified in the [versions]
section will take precedence over the pins inherited from https://dist.plone.org/release/6-latest/versions.cfg
.
To actually download and install the new package version, run the following command.
bin/buildout
Then restart your instance.
See also
Install a core Plone package from source#
A core Plone package can be installed from a source control system such as GitHub.
Update the file buildout.cfg
.
This example uses plone.restapi
.
[buildout]
extends =
https://dist.plone.org/release/6-latest/versions.cfg
extensions = mr.developer
auto-checkout =
plone.restapi
parts =
instance
[instance]
recipe = plone.recipe.zope2instance
user = admin:admin
http-address = 8080
eggs =
Plone
[sources]
plone.restapi = git https://github.com/plone/plone.restapi.git
[versions]
plone.restapi =
Tip
Setting an empty version ensures that the copy of plone.restapi
from source control will be used, instead of the version pin inherited from https://dist.plone.org/release/6-latest/versions.cfg.
To actually download and install the new add-on, run the following command.
bin/buildout
Then restart your instance.
See also
See also
This approach uses the mr.developer
Buildout extension.