Will's blog

I was talking with Josh the other day and he told me that I should take the time to learn Subversion and switch over rather than investing more time to tame my projects with CVS and CVSTrac. So I spent a good portion of today moving my PyBlosxom plugins (the ones that I wrote and/or maintain on my own) to a Subversion repository and Trac.

There are a couple of things that will take getting used to, but overall I've been able to replicate everything I did with CVS in Subversion.

I'm still making modifications to the setup, but I'll be hosting all my PyBlosxom plugins work at http://www.bluesock.org/~willg/cgi-bin/pybltrac.cgi/. I've allowed anonymous ticket creation for feature requests, bug reports, and the like. If you're sitting on issues, patches, and things of that nature, feel free to submit them.

Prior to today, I was maintaining all my PyBlosxom plugins by hand... which was kind of stupid, but I hadn't really gotten around to investigating better solutions.

However, that day has come! I've pulled them all into a CVS repository and set up CVSTrac to manage documentation, bugs, features, and allow people to see version history for all of them. I'm in the process of going through all the plugins, adding CVS tags, updating copyright dates, fixing documentation, adding notes in regards to where the plugin is maintained and all that.

I aim to make the end result more organized for me and users looking for plugins and also require less effort to maintain.

In lieu of other solutions, I'm going to start releasing contributed plugins plugin packs. This one should work with PyBlosxom 1.1.

If you find problems with contributed plugins, visit this page on how to contact us. "Problems" could be bugs, feature-requests, or setup issues.

If this works out, then I'll continue releasing contributed plugin packs that match up to PyBlosxom.

Find the contributed plugin pack here (contrib.1.1.tar.gz).

Brett discovered some issues with booklist as it interacts with comments. So this fixes those issues.

You should note that if you're using booklist and comments, you should have at least 2 books in your list. Otherwise comments sees it as a single entry, decides to show comments for it, and then stomps on the property in the entry that dictates which template to use. That's a bug in comments that needs to get fixed.

Get it on my pyblosxom plugins listing

Fixed encoding issues and some other things. Thanks Aslak!

Get it on my pyblosxom plugins listing

Fixed a bug where categories with four letter names were getting picked up even if the name wasn't all digits. Thanks Ludvig Omholt!

Pick up the new plugin here: my pyblosxom plugins.

I got a comment from David Ascher on this entry which pointed out some issues with the wbgamazon plugin. After a few minutes, I fixed the problems listed and released a new version.

my pyblosxom plugins

I've blogged for so many months now that the Archives listing on the side was getting pretty long. I don't really want a long list of months and years there, so I was looking for options.

Ned Batchelder lists his archives by year. For each year, there's a summary page by month which lists the dates and titles of all blog entries for that month. I really liked this idea, so I wrote my own archives plugin to use it. It's not exactly the same--the output is slightly different. It's good enough for me, though.

my pyblosxom plugins

Turns out it was creating garbled yucky stuff that hosed my RSS 0.91 feed. I fixed it so that if it thinks it's outputting to an RSS feed, it just returns rather than doing the transformation.

I should look into making this a postformatter--that would be better.

my pyblosxom plugins

I added the Request object to the locals for eval_python_block. I also did away with the "printout" kluge I had--you can use print now.

If you used an old version and are upgrading to this version, you'll need to convert all your "printout" function calls to regular print statements.

Find it in my plugin index.

I decided the registry plugin needed to allow users to see all the pending submissions and details therein. So I made some changes:

• added handling of /registry_queue which shows all the pending submissions.
• added some code to displaying of the entry so that the "edit" link doesn't appear if there's already a pending change.

Get it on my pyblosxom page.

There are some minor tweaks, but more importantly, I added the ability to evaluate python code blocks in the static page. Find it in my plugin index.

I whipped up a plugin that changes the renderer to the debug renderer if there's a "debug=yes" in the querystring. It's not wildly exciting, but it works nicely and I can debug things without necessarily taking my entire blog down.

Get it at my plugin index.

I've been in some kind of neat motivational kick the last few days to update my plugins. This time, I've overhauled the registry plugin that Wari uses for the Pyblosxom web-site.

Changes:

• added ability to submit new entries
• added ability to edit existing entries
• fixed sorting so that you can sort by any input name
• added the ability to do option inputs
• moved declaration of what items were involved to the config.py file (along with other things)
• added documentation to the top
• refactoring of item specification stuff

Anyhow, if you were one of the one or two people that were using it, this is definitely worth updating to. If you need help reconfiguring it or if you have problems, let me know.

It can be downloaded at my pyblosxom page.

(snuck it in just before the end of the year--yay!)

I was poking through other peoples' blogs and bumped into one that mentioned a bunch of things I should do to my booklist plugin to fix it. One of which involved switching it from hard-coded html to use pyblosxom flavours. So I did that work and some other neatening up and released it. Get it on my pyblosxom page.