Submitted by johnh on February 23, 2007 - 03:39.

You look after websites, you end up wasting days after days of your life cleaning up baby poop. In this case, we were trying to add Feedburner to a pre-existing Wordpress 2 blog. Obviously that couldn't possibly work. Suggestion was to upgrade to the current codebase of WP2.0. Of course you know what happens next -- I spend yet more hours I will never reclaim picking through code which was never tested on anything (see passim), and which of course completely falls apart as soon as you try running it on -- say -- FastCGI. Which is the only way you'll ever get the bloody thing to serve more than a couple of pages an hour if you get any traffic. Onwards to the meat of today's advice:

Hey, dipshits: plugins [1] go in subdirectories.

On what crack-smoking planet do you release a codebase (2.0.9, since you asked) which allows you to activate a plugin in that subdirectory while simultaneously requiring it to be in its parent directory when I call the options page?

And throw errors about redeclaring classes if I try to fix it, and disable/enable plugins on your whim depending on where they're currently stored?

Here's a present:

You read that, and I'll spend another three cocking hours unbreaking the plugins you just screwed. Which, for the record, was all of them.

[1] Incidentally, how are they plugins when you need to perform major surgery on the core app to make them work in the way you claim they do? That's rather like referring to a kidney transplant as 'jewellery'.

delicious | digg | reddit