You need a whole special load of stuff to run Plone or Zope scripts for the command line. These centre around getting hold of the portal object from which everything else is available, setting a fake request object so you can traverse around the site and setting a user so you have permission to do whatever it is you want to do. Then at the end you have to commit your transaction and sync the zeoclients.

The move from Plone 2.5 to 3.x meant you have to use a different way of allowing your site users to remain logged in.

You can change the code in the usual viewlet way, and change the items displayed and the text/link used via the ZMI

Sometimes you get TraversalErrors in the error log, which don't appear to show up on the site. Here's why...

In Plone 2.5x and 3.x, this is how to set up RSS

You ought to be able to this via UML/AGX, but the method doesn't seem to work. Here's how it actually works, and what ought to happen with AGX

Strange things happen with CacheFu when you try to start a cluster with references to a missing product

If something goes wrong with a zeocluster, you need to start it in the foreground so you can see what is going wrong

Symptom: a zeo server will not start. Checking log shows above error. Cause: Corrupt persistent zeo cache file.

Heading fonts in slideshows are horribly blocky in IE, and all text can be affected.