Cam

That did the trick. Many thanks.

Works like a charm — many thanks Kafkaesqui!

Update: Nope, nothing happened. Is there anything else I can try?

Thanks Ian… I’ll give that a bash and see what happens.

Update: I’ve sorted my problem out. There was a conflict between the rewrite rules for individual archives and category archives. I had my individual entry permalinks set up as /archives/%year%/%monthnum%/%day%/%postname%/ and my category archives set up as /archives.

By changing the category archive base to /archives/category, I managed to solve my dramas, without having to use any rewrite rules imported from an old copy of WP.

So there you go. Not a biggy at all, but one that took me about 4 hours to figure out. I did learn a lot about mod_rewrite and regex in the process, though, so it wasn’t a complete waste of time.

(And also for reference, copying the old rewrite rules over fixed the individual archive problems, but broke category and monthly archives, but this may have been a function of the heavily-hacked .htaccess I currently use.)

OK, just for reference, copying the rewrite rules over from my local copy of WP 1.2 made it work. In as far as it goes, this is fine, but I have heavily hacked that particular install and the associated .htaccess, so I’ll have to see if it causes any other carnage with the new install of 1.5 I have running.

More importantly, though, was that the 1.5 install didn’t work right out of the box. Has anyone come up with a fix for a brand-spanking new WP?

macmanx, I am using mod_rewrite for a couple of other things, running on other virtual servers on the same Apache install (2.0.52 under OS X 10.3.7.). And with my local 1.2, nice URLs work just fine. I have messed about with the 1.5-generated .htaccess a bit to see if I could get it to work, but no dice so far.

Kafkaesqui’s advice (above) about keeping the old rerwrite rules doesn’t really work in this instance, as I’ve created a brand-spanking new virtual server for a fresh install, so there’s no old entries on this partiular blog.

I might try copying some over from my local 1.2 and see if that works.

I’d be interested if someone has found a solution for this one, too. I am playing around with the Feb 04 nightly on my local dev server, but can’t get my preferred permalink structure to work:

/archives/%year%/%monthnum%/%day%/%postname%/

I want to keep the /archives/ on the URL so that when I upgrade my production site I don’t break any of my old permalinks (and besides, I think it looks nice).

There are a few other topics on the forums with similar queries, but I am yet to find one that has a solution. Has anyone solved this one?

Thanks heaps for that guys — that’s exactly what I was after!

Check the plugin author’s page (or whereever you downloaded it from) for instructions. Generally you have to add a snippet of code to your WP template to display the output from the plugin.

The User Manual was one, can’t really remember any of the others off the top of my head. It seems to be fixed now, though.

Thanks for the tip NM… I’ll do that.

I have done a couple of minor updates to the script — you can download 0.2 from the same place as the original.

rubyji – have you set up your .htaccess file so you can use the clean URIs?

First up, thanks all for the replies.
From what I’ve seen, displays inline (correct?) this is pretty easy to change to display: block; using CSS, so I'm not too worried about that.
In terms of the existing plugin, the 'lang' thing does concern me, though. When I changed over to WP, I tried to build my site so that it validates as XHTML 1.0 Strict. Although the 'lang' attribute would (almost) certainly pass muster with the validator (unless it is invalid for the <pre> tage or validates the attributes against some list so only values like 'en-us' or whatever would pass), I think using it would violate the spirit of the standard, which is bad karma in my book.
I know beggars can't be choosers, so I guess it's a question of either shutting up or doing it myself. (I'm only starting out with the whole PHP thing, but it's something I'd definately like to have a crack at when I get more proficient, and the whole reason I was after something in the first place was so that I could document what I have learned and publish the code I have written to date.)