So it’s the end of day one halfway through day two (this took a lot longer to write than I thought!) […]
When writing tests, there’s one thing we’re now sure to do because it’s caught us out so many times before: […]
Over the past few days, I’ve been tinkering with the latest alphas of Plone 4, particularly with an eye to […]
As Plone developers, a lot of the problems we have when writing code and templates are only revealed with cryptic, sometimes misleading error messages from somewhere way down the stack from their underlying cause, if at all. When an error is raised, by some template rendering, Zope does provide some useful traceback information specifying the template with line numbers and expressions and whatnot. But why shouldn’t we be able to access this information without raising an error?
I recently had the problem of finding out if a content type in Plone implemented a certain interface, but only […]
One of our current projects working with Plone requires multilingual content using the LinguaPlone product. One of the features that […]