WordPress 2.3

Upgrade complete – sidebar borked.

Apparently the introduction of the new tagging doo dah means a table is now no longer valid, the table that quite a few plugins were using, one of which was powering my miniblog posts.

Hence why they’ve all, suddenly, appeared here.

So, until I get some free time to get the code sorted out myself, this is how it’s gonna be… mind you, maybe a switch to single column…


  1. lucy p said:

    time to simplify, gordon! take advantage of the er… borkage. borking? borkdom. borkation. borkness? you know. I used to spend HOURS (obv. I’m not as techie as you) every time I upgraded wp or b2 or whatever else I’ve used in the last few years, fixing the breaks. Now I just give in to the upgrade. is that pathetic?

    October 11, 2007
  2. Gordon said:

    It also took a hack of one of the PHP files to get it working. Not mad happy about any of this. Previous upgrades have been quick and easy, why did this one break?

    October 12, 2007
  3. Lyle said:

    Because it’s doing lots of new stuff, and could almost have been titled WordPress 3, rather than 2.3

    They’ve changed taxonomies, done lots of different stuff, and so it was always going to break something.

    Although the hack to the PHP file would worry me, definitely.

    October 12, 2007
  4. Gordon said:

    I didn’t like it either Lyle, and it was only a lucky Google that took me to a Support forum post that contained the hack. Changes to the DB mean I can’t go back either.

    My fault though, I should’ve checked but as you say, a point release this is NOT.

    And regardless of all that, let me repeat two words: backwards compatability!!!

    (from what I understand, the tables no longer used are still there, so why can’t the system write out to those AND the new stuff??!!)

    October 12, 2007

Comments are closed.