Posts tagged 'python' – Page 3

Buildout and Version Problems

Two blog entries in one day - wow it’s been a good work day.

Just a quick chronicle of my thoughts: version conflicts in buildout aren’t always pretty. My latest escapade into trying to load up Varnish through zc.buildout resulted in a hair-tearing out message:

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 1477, in main
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py …

Plone: Python Eggs And Development

Welcome to the new year! It’s the start of another journey around the sun and the beginning of work for me. Whilst I’m the only one actually working around here today, I thought I’d take the chance and update with some useful info:

Troublesome Python eggs

Now, much to my amazement, when you’re creating/compiling/whatever Python eggs for Plone you need to actually specify the files you want included in the build. I suppose it’s fair enough, but thought it might have actually done it for me. No such luck!

The SOURCES.txt file …

Plone: Ploneboard Conversation Editing

I’m back with even more Plone goodness. Turns out Ploneboard has a problem/issue (well, HAD an issue until I went and edited the code on the SVN repository for the Collective of Plone. Read: will not have in the next major release) with redirecting the user after they go and edit a post. So essentially the user ends up getting to a page that says ‘Insufficient privileges’, which is was extremely odd considering I do everything as an admin.

The fix goes a little something like this:

In ploneboard_scripts/comment_redirect_to_conversation change it to be:

# XXX if we ever …

Plone: Relative ‘Recent Changes’ Portlets

The problem I’ve been faced with today on our Plone systems is that I need to created a ‘Recent Changes’ portlet that’s relative to where the user is on the site.

Now, the standard portlet doesn’t do anything for me, so that’s pretty useless. I had a look at the standard code for the portlet too and it’s not really feasible to try and mess with:

<tal:recentlist define="view here/@@recent_view; results here/results;">

However, using a (nasty?) workaround, if we put the classic Recent Changes portlet into play, we can change that above …