This is pretty trivial (and trivial to fix), but I’m chronicling it for my knowledge as much as anyone else’s. The issue is that a given Python egg is missing some form of files, most commonly the ‘docs’ directory in my experience, because the build wasn’t configured correctly.
Continue reading »
Update: You should check out wildcard.fixpersistentutilities – it’s a fantastic solution to problems like this. Many thanks to Nathan Van Gheem, the author of the add on. Check out the link and see how to install it (temporarily) on your Plone instance that needs its site manager cleaned up.
Leftovers are typically useful when they’re in your fridge at home. They mean you don’t have to mess around making lunch for the next day for work, and can just grab them, and walk right out the door. Now, leftovers in the zope.component SiteManager aren’t so nice, especially when some Plone products fail to remove what they’ve registered. The consequences of this are that you’ve got references left which will break things when you uninstall/remove the physical eggs/files. These leftovers would be ones would be mutated food that comes to kill you after you’ve thrown it in the bin, assuming we follow the same analogy. But how to fix them?
Continue reading »
These titles of my posts just keep getting longer and longer. For those of you paying close attention (I know who you are), this is the next in my series of getting the above-mentioned tools working together. Previously, it was Centos 5.x, Jaunty (9.04), Karmic (9.10) and now Lucid (10.04). Only subtly different, each of this distributions has pretty much called for its own post on the matter of getting a working Plone 3.x / Python 2.4 virtualenv installation going. So, here goes this time around.
Continue reading »
I’m skipping actually quantifying the number of things to do because this post will undoubtedly get updated as time goes on. I’ve just updated both my computers (personal laptop and work desktop) to Ubuntu 10.04 from 9.10 and I’m very happy with how things have gone. That isn’t to say a few minor things haven’t annoyed me, such as Project Hamster removing its Day view for task management or Python 2.4 being dropped entirely, but overall, it’s gone well. Here’s my thoughts on what you should do as soon as you’ve made the jump (or installed).
Continue reading »
Writing unit tests (especial doctests) for your Plone product is reasonably time consuming. For us developers, having tested code is absolutely essential. This is especially true when clients are beating down your door looking for a fully functional product and you need to know what you’ve written works and isn’t going to fall over (just yet, anyway). Web apps are able to be tested using a multitude of frameworks, and whilst not the most fully featured (eg lacking Javascript support), Zope’s doctest machinery is right there within your Plone product. In order to write these, enter zope.testrecorder to more-or-less automate replicating your actions into tests.
Continue reading »