Personal tools
You are here: Home How to Install Premium Plone Themes on Plone 4

How to Install Premium Plone Themes on Plone 4

— filed under:

The following are general instructions for premium themes installation on Plone 4. There is INSTALL.txt file in every theme's /docs directory with the exact installation instructions for every theme.

In this article we use quintagroup.theme.themename as an example theme name

After you competed buying process for any of Quintagroup Premium Themes on 2CheckOut, Inc., you will receive a zip archive of  theme product source - quintagroup.theme.themename-version.zip,

To install this theme on your Plone 4 site:

  1. Unpack source archive quintagroup.theme.themename-version.zip into your instance's src directory
  2. Open buildout.cfg file in the root of your instance
  3. Add reference to the theme products location (to src directory) under [buildout]:
    [buildout]
    parts = 
    .....
    develop = src/quintagroup.theme.themename
  4. Add quintagroup.theme.themename to the list of eggs to install and tell the plone.recipe.zope2instance recipe to install a ZCML slug:
    [instance]
    recipe = plone.recipe.zope2instance
    ...
    eggs =
           ...
           quintagroup.theme.themename
    zcml =
           ....
           quintagroup.theme.themename
  5. Re-run buildout with the following command in the terminal::
    ./bin/buildout
  6. Restart the Zope server, for example, with the following command in the terminal:
    ./bin/instance restart
  7. On your Plone site go to Site Setup -> Add-ons
  8. Select the theme among products available for installation and press 'Activate'.

Important Note

In case you get zope-schema-related version conflict (Error: There is a version conflict. We already have: zope.schema 3.5.4 but z3c.form 2.4.2 requires 'zope.schema>=3.6.0) during buildout re-run, please add the following address to the list of extends in your buildout.cfg file:

[buildout]
...
extends =
...
http://good-py.appspot.com/release/plone.app.registry/1.0b2

This should resolve the version conflict. This conflict usually appears for themes that use Products.Carousel as their dependency.

Document Actions