plone.app.themeeditor 1.0a3

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

Known Bugs

The zcml slug is needed even with Plone 3.3.x and 4.x, the plone.app.themeeditor profile does not show as being installable otherwise. This is considered a bug and will be fixed in a future release.

Export is buggy with zeo - The export feature is still experimental, when used with a zeo based instance it is known to work the first time and then fail after that.

Version Notes

Plone 4.0.5 to 4.1b1

Add zope.schema = 3.6.0 to the version section of your buildout.cfg file

[buildout]
...
versions = versions

[versions]
zope.schema = 3.6.0

Plone Versions between 3.x up to 3.3.5

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

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

versions = versions

[versions]
zope.schema = 3.6.0
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). It is likely that newer versions of Plone 3 will adopt the versions of plone.app.jquerytools and plone.app.customerize listed above. If your version of plone requires a newer version of plone.app.jquerytools or plone.app.customerize there is no need to pin them in the [versions] section.

Plone Versions between 3.1.x and 3.2.x

Versions of Plone before 3.3 do not use z3c.autoinclude so it is necessary to add a zcml entry in buildout

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

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

1.0a3

• Add french translation [toutpt]

• Fixed broken export for resources that were identified as ‘zopeview’ [pigeonflight]

1.0a2

• fixed an error that was causing exports to work only once in a single session [pigeonflight]

• created a templates directory and moved all the .tmpl template from the browser directory to the templates directory, updated the browser/export.py form code to grab templates from the new location [pigeonflight]

• fixed the popup export form (removed formselector in themeeditor.js) so that the theme actually downloads [pigeonflight]

• added validator to checks to see that themes are named with proper dotted named [pigeonflight]

• ensure that themeeditor doesn’t break if the active theme declares nonexistent filesystem skin folders [pigeonflight]

• removed redundant export.py file [pigeonflight]

• update tests including a windmill based test of the exporter [pigeonflight]

• the export form now shows up in a popup window with instructions [pigeonflight]

• updated the TODO.txt [pigeonflight]

• added an export button to the UI [pigeonflight]

• bumped version [pigeonflight]

• the exporter now “cleans up” after itself and removes temp files [pigeonflight]

• refactored the way the jbot.zcml file is generated [pigeonflight]

• the export view now generates a theme egg as a downloadable tarball [pigeonflight]

• @@plone.app.themeeditor.export now writes jbot templates and directory view resources [pigeonflight]

• The themes that are generated now have z3c.autoinclude in their setup.py and lists

• setup.py generated from export now writes the author and author_email [pigeonflight]

• added utils.py (borrowed from qPloneSkinDump product) for writing cmfskins resources [pigeonflight]

1.0a1

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