Comments on: EP08 – Trusting WordPress

By: Vince

Vince — Tue, 01 Sep 2009 20:14:24 +0000

Intresting stuff im new to these things i’ll keep an eye on your post to hear more.

By: Kevin Donahue

Kevin Donahue — Sat, 20 Jun 2009 10:36:33 +0000

Great link for the WP Plugin compatibility. Thanks!

By: Moses Francis

Moses Francis — Wed, 17 Jun 2009 16:38:32 +0000

@Nick Kask – i would suggest you wait a little longer after a new release before upgrading your clints sites, especially if you’ve done some extensive modding.

@Leland – i agree with you completely, some ppl just “have to” upgrade to the latest version without giving much thought to compatibility (plugins).

btw Adii, got to watch any footy game at yr place? (if your a football fan that is) hehe.

By: Quick Hits: Tech News | White African

Quick Hits: Tech News | White African — Tue, 16 Jun 2009 17:33:26 +0000

[...] 2.8 big new release for the world’s top blogging platform. I, like Adii, am interested in how much people trust WP to get it right, and just update without doing any [...]

By: Fred

Fred — Tue, 16 Jun 2009 13:41:59 +0000

Count me in on the sentiment that people need to definitely slow things down when it comes to upgrading. It is amazing and it speak very well of Wordpress that they have been able to build that level of trust with their users, but it is certainly not a foolproof system – nothing is.

By: Leland

Leland — Tue, 16 Jun 2009 11:34:04 +0000

I said this on Twitter yesterday, but I really don’t understand the mentality some people have to upgrade WordPress immediately after a new release. Unless there’s some major bug or security issue, what’s the big rush?

In my experience, on WordPress sites dependent on a lot of plugins, upgrading tends to cause a lot more problems than it helps. This is why I try to use as few plugins as possible nowadays since for some reason they expect the plugin authors to constantly keep up with new core updates, and that’s not something that always happens.

Another problem is that it seems WordPress forum moderators don’t seem to be that willing to help, brushing the reports off because it’s “a theme you pay for,” even though they’re are probably lots of free themes that have the same issues.

By: Adii Rockstar

Adii Rockstar — Tue, 16 Jun 2009 06:29:56 +0000

Hehe… Yeah Foxinni had to fix the WooThemes that were using get_categories() and only he knows how the hell he got it to work… But it is kinda dodgy that a change to such an important function wasn’t better documented.

By: Adii Rockstar

Adii Rockstar — Tue, 16 Jun 2009 06:28:47 +0000

I definitely think 2.8 was more of an “in-between” release, where they were paving the way for some massive new stuff coming in 2.9 (maybe) or 3.0 (more probable). So whilst I’m not wowed by 2.8 either, I do love the widget interface, as it’s a MASSIVE improvement from before.

By: Dan Harper

Dan Harper — Mon, 15 Jun 2009 23:36:33 +0000

Actually I think the importance of not just upgrading straight away is very evident with the 2.8 release.
Many themes use an options page, but in the 2.8 release the get_categories() function no longer performs as it should in back-end code (oddly, unless it is ran from inside a function).

Obviously this has caused huge amounts of themes to suddenly break – this doesn’t seem to be the case with WooThemes as they have been coded slightly different.

It was actually quite difficult to get WordPress Support Moderators to acknowledge this as an actual problem – it was repeatedly blamed on theme authors. It’s now been acknowledged as a bug, so hopefully it’s fixed soon!

By: Nick Kask

Nick Kask — Mon, 15 Jun 2009 19:48:52 +0000

I use WordPress on a lot of client sites, and always hit Upgrade Automatically when prompted by WordPress.

I am not concerned about a failure. Should I be? Sure.

But shouldn’t I also trust WordPress enough to think they wouldn’t have that feature unless it, you know, worked?

That said, 2.8 has some nice new features. But from a medium-level developer standpoint, I saw nothing spectacular, but I didn’t expect it with a “.x” update. I am sure, however, that a lot of work went into making it better on the code/app side, and that’s what I’ve come to expect from WordPress.