Plone Upgrade and new Weblog

With the old Plone 2.1.x getting quite outdated an upgrade to the new Plone 2.5 version was iminent. While working on the site an upgrade to a new blogging software was also done.

Well, the plone upgrade from 2.1.1 to 2.5.2 went pretty smoothly. After backing up the complete site Python 2.4 and Zope 2.9.6 were installed from scratch. A new instance was created via mkzopeinstance and the old data.fs file as well as the products directory copied to this new installation.

But no "plone" folder anymore!

The only problem I encountered was that one folder named plone was no longer accessible. This stems from the changed internals of Plone 2.5. Here plone is a reserved view denoting a special view used from within Five. After some experiments I was able to change the name of the folder in an interactive session started by zopectl debug. Thats what I did:

# get the required privileges
admin = app.acl_users.getUserById(‘admin’)
admin = admin.__of__(app.acl_users)
from AccessControl.SecurityManagement import newSecurityManager
newSecurityManager(None, admin)

# create a dummy request
from Testing.makerequest import makerequest
app=makerequest(app)

# do the renaming
obj = app.<some.path>.plone
obj.aq_parent.manage_renameObject(o.getId(), ‘plone2’)

Quills as Blogging Solution

Also, since the old simpleblog based blogging solution is not compatible with Plone 2.5.x (and with Plone 2.1.x only through the ZMI) I played around with qSimpleBlog and Quills as products. With qSimpleBlog throwing errors about access to blogGlobals and other variables or templates left and right, Quills seems to be the way to go.