plone.app.themeeditor 1.0a1

Theme Editor for Plone, Customize your theme resources through the web

Overview

The theme editor makes it possible to customize most aspects of a plone theme from a single location. After installation a new entry is added to the Plone “site setup” control panel called “Theme Editor.”

Using the themeeditor

1. Log into your Plone site as a Manager

2. Navigate to Site Setup

3. Select Theme Editor

Reporting Issues

Visit https://dev.plone.org/plone and submit a ticket related to Theme Editor

Installation

If you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this:

• Add plone.app.themeeditor to the list of eggs to install, e.g.:

  [buildout]
  ...
  eggs =
      ...
      plone.app.themeeditor

• Tell the plone.recipe.zope2instance recipe to install a ZCML slug:

  [instance]
  recipe = plone.recipe.zope2instance
  ...
  zcml =
      plone.app.themeeditor

• Re-run buildout, e.g. with:

  $ ./bin/buildout

Plone 3 notes

You will need to pin newer versions of plone.app.customerize and plone.app.jquerytools as shown below:

[buildout]
...
versions = versions

[versions]
plone.app.jquerytools = 1.1.2
plone.app.customerize = 1.2

Important: the versions noted here were correct at the time of release (Plone 3.3.5). If you are using a newer version of Plone 3.x which requires a newer version of plone.app.jquerytools or plone.app.customerize there is no need to pin them in the version section.

Changelog

1.0a1 (unreleased)

• removed [plone3] extra from setup.py [davisagli]

• fix the windmill test replaced an xpath selector with a jquery selector [davisagli]

• more i18n fixes [davisagli]

• fix test assertions re translated strings; add a missing translation [davisagli]

• removed plone.app.z3cform include from browser/configure.zcml [pigeonflight]

• removed all patch related code [pigeonflight]

• added an export form view @@plone.app.themeeditor.export currently only writes a generic zopeskel theme to a temporary directory [pigeonflight]

• dropped dependency plone.app.z3cform and collective.monkeypatcher will introduce this when we start working on export via zopeskel [pigeonflight]

• removed browser/export.py (will work on this in the zopeskel branch [pigeonflight]

• removed the use of collective monkey patcher [pigeonflight]

• extended the ‘extras_require’ to included a [plone3] section [pigeonflight]

• added new README information and a docs/INSTALL.txt explaining how to install noting the use of the [plone3] extra for Plone 3. [pigeonflight]

• Renamed to plone.app.themeeditor (was plone.app.skineditor) [pigeonflight]

• Added a link to the themeeditor in site actions via actions.xml [pigeonflight]

• Adjusted the html in console.pt as it did not validate (a tag should not contain dt tag) [pigeonflight]

• updated css to work with the new structure of console.pt [pigeonflight]

• replaced the use of p tag with span for the resource descriptions p tags are not allowed within dd or dt tags [pigeonflight]

• appended a number from the tal repeat to the end of each resource id to ensure that all resource items get a unique id [pigeonflight]

• fixed code on zopeview.py, portlet.py and viewlet.py so that it works with older versions of customerize (i.e. initial fixes towards Plone 3 compatibility) [pigeonflight]

• patched plone.app.customerize for performance if the version is older 1.1.3 used collective.monkeypatcher (this should improve performance of theme editor on Plone 3) [pigeonflight]

• using collective.monkeypatcher preconditions parameter didn’t seem to work used a zcml:condition instead to select for Plone 3 and apply the patch [pigeonflight]