Another WordPress Upgrade…

So WordPress let a nasty hacker modify their download and I've got to go around upgrading everything again. Now upgrading WordPress isn't difficult except that every time you do, it puts back all the useless crap on the dashboard that I remove. I have a perfectly good feed reader, I don't need my dashboard showing me old posts from the WordPress development blog and irrelevant posts from Planet WordPress.

With one blog that would be bearable, but I'm currently maintaining five WordPress installs and I'm sick of it. So after way too long I've cottoned on to the fact that the index-extra.php file that causes all the problems is unlikely to change very often and I can probably just store a patch file and then quickly reapply it. That patch is here if anyone else wants it. It simply replaces the downloading and parsing of the RSS feeds with creating an empty array and it removes the mysterious "partner=wordpress" from the end of the call to Technorati to get the incoming links. Why is that there? If there were an upfront and honest explanation of it I probably wouldn't mind but I really don't like secret partnering deals going on in software that I run locally1.

 

1 - Don't even get me started on how annoyed I am with Mozilla's browsers insisting on taking me to their Google portal every time they upgrade - just in case they can squeeze a few bucks out of the deal.

2 Responses to “Another WordPress Upgrade…”

  1. Henri Yandell Says:

    Thanks Adrian, applied.

    I’ll need to start publishing my diffs too.


  2. Symphonious » Auto Update And Privacy Says:

    [...] comes as no surprise to me that the WordPress mob broke this rule with their new auto update - they always seemed shifty to me. Tell me why exactly you need the URL of the blog to determine if a new version is available? [...]


Leave a Reply

Alternatively, subscribe to the Atom feed.