I've just added a simple support to filter my blog entries by language: simply pass "lang=sr" or "lang=en" parameters (e.g. use /blogging?lang=en to get only English, blogging related entries).
So folks, choose what suits you better.
I wonder if this is the same problem I had when transferring Pyblosxom to a new host.
I switched to using SuExec on a new machine, and it seems to refuse to execute scripts which have +rw set for the group, eventually spitting out the error message in the form of "Premature end of script headers".
Yeah, as I already said here when transferring my blog, this was pretty non-obvious to find out, especially so since most people tend to look for Pyblosxom problem, instead of SuExec.
Though, Data might be having entirely different problem, but since there are some security consious comments there, I guess SuExec is used as well :)
Okay, I've been cleaning up my blog somewhat. And as say:
Just having a blog tool isn't enough. You have to hack it. Make it your own.
First of all, zombie complained of my blog taking forever to load. Well, that has been fixed, and now I list 4 last entries on the start page. This took a whopping 5 lines of Python code to create.
This also resulted in a new parameter being defined: 'limit'. If you put
py['limit'] = 5 in your config.py, you'll limit the number of entries on your blog start page to five. All other pages will be unaffected with this parameter. If you don't want this limit, just don't define it.
I've also upgraded to Pyblosxom 0.8.1, and switched the base URL to danilo.segan.org (it's still available through danilosegan.com, but the new address should be default) — sorry for any problems this may cause in your aggregators :(.
While upgrading, I decided to make precise patches that apply cleanly to 0.8.1 source. So, I've come up with patches for:
I'm considering adding CommentAPI support, but I lack any useful clients so that I could make use of it (and test it, of course).
Also, I've temporarily disabled my trackback autodiscovery, so I won't ping any sites for a few day (I'm hoping to make it work better, and to add pingback support alongside trackback).
If I find some time, I might even add MetaWebLog API support, because Gnome Blog in CVS (so this is insider's info, keep it to yourself :-) now supports the dropping of images and sending it through MetaWebLog API. Hey, how kuhl is that?
Besides MetaWebLog API, I hope to get i18n up to my requirements for Pyblosxom in the near future. That means using Accept-Language for transparent content negotiation, and gettext for translating strings in server-side code.