Plone 3 Theming Errata
Below is the list of ongoing errata from the Theming for Plone 3 book by Veda Williams. These errata are also being relayed to Packt Publishing so that they will hopefully be resolved in upcoming printings / ebooks. Any additional errata can be submitted to veda@groundwire.org and are appreciated.
Thanks to Scott Paley, Feneric, Jeff Pittman and Walt Martin for spotting these.
General comments:
Where I have said "mynewtheme", change that to "mytheme".
Chapter 2:
Page 39, Text Editors, TextMate
TextMate can be purchased for 39 Euros, or around $57 USD.
Chapter 3:
Page 55, Subversion for version control
The Macintosh equivalent of TortoiseSVN is SCPlugin, and can be found at http://scplugin.tigris.org.
Chapter 4:
There's an important errata in Chapter 4 where you create the Plone theme. It reads:
$ paster create -t plone3_theme
It should read:
$ paster create -t plone3_theme plonetheme.mytheme
You could optionally specify plonetheme.mytheme after the initial syntax here, too:
$ paster create -t plone3_theme
The real point here is that "My Theme" is not a valid package name, and buildout will not pick it up if there are spaces in the name. You need to create a package name that is one word. We use the plonetheme namespace here, too, out of convention.
Also, where it says:
Enter project name: My Theme
It should read:
Enter project name: plonetheme.mytheme
Chapter 4
Page 72, Putting your site into debug mode
In the path given, it should be portal_css, not portal/css.
Chapter 5
Page 80, Install Your Theme Product
Replace the semi-colon with a colon here: http://localhost:8080/mysite.
Page 80, Install Your Theme Product
Where it says to modify mytheme.css in skins/plonetheme_mynewtheme_styles, you should actually be modifying main.css in the browser/ folder.
Page 95, Install Your Theme Product
Where it mentions editing the mytheme.css file found in the skins/plonetheme_mytheme_styles file, you actually want to modify the main.css file located in the browser/ folder of your theme product instead. Make sure you have your site's portal_css in debug mode (outlined in the next section).
Page 96, General Guidelines During Development
"Uninstallation requires that a theme to have an uninstall profile written for it." Need to remove the word "to".
Page 99, Changing base_properties
Where it says: “The actual name of the base proptery sheet on the filesystem is base_properties.props, and it can be found in parts/plone/CMFPlone/skins/plone_styles.”
The path should be: src/plonetheme.mytheme/plonetheme/mytheme/skins/plonetheme_mytheme_styles
Page 104, Common conventions for using stylesheets in Plone
The paragraph starting "when a new Plone" is duplicated. Ignore the first place where it appears.
Page 107, Starting with CSS in the ZMI
The path in your buildout that you drill down to should be:
buildout-cache/eggs/Plone [some version number]/Products/CMFPlone/skins/plone_styles
Page 108, Creating a theme-specific stylesheet in your filesystem product
The path to the stylesheet should be:
skins/plonetheme_mytheme_styles
Also, to clarify, the cssregistry.xml file is located in profiles/default/.
Page 109, Moving portal_actions configurations into a filesystem product
After the sentence that states that you should import your generic setup step for your theme product into your website, there should be a sentence reading: "You can import this step by clicking on the Import tab and by choosing your theme product's profile from the dropdown list at the top of the page."
Chapter 6
Page 121, Browser Pages
The code in this section does not work -- at all. I'm working on getting it fixed and will have revised code soon. My apologies. In lieu of reading this section, please take a look at the following links:
http://worldcookery.com/files/ploneconf05-five/step3.html
http://plone.org/documentation/tutorial/customization-for-developers/zope-3-browser-views