Wordpress 2.3 You Suck
September 26th, 2007 by Michael Gray in BlogsIf you're new here, you may want to subscribe to my RSS feed. Read my top posts or learn more about Michael Gray. Want more frequent updates follow me on Twitter. Thanks for visiting!
Ok I’m not a programming expert, but I have been involved with computers and programming long enough to pick up a few things you shouldn’t do, like …
Don’t make massive changes to your database schemas that break existing functional programming. I worked for a retail company and had been using the same database schema for over 10 years and one of the top rules was don’t make a change that will break someone else’s fully functional program. I mean hello … do I have to explain the reasoning behind this … what kind of third rate one eyed single finger coders you have working there. Look at all the non functional plugins we’ve got to deal with now. I have one blog with at least 6 plugins … not worth the trouble right now updating across all the blogs I manage … sigh
Sphere It
September 26th, 2007 at 9:01 am
I couldn’t agree more, just when I got the auto-update working well enough to trust it on numerous sites. I don’t feel like checking the entire list of plugins against these lists right now.
September 26th, 2007 at 9:08 am
Schema changes will happen as things evolve, it’s a fact of life, especially for an open source project. For those in your situation, don’t update to 2.3 for a while until most/all of the plugins get updated. It doesn’t do any good to complain about the inevitable.
September 26th, 2007 at 9:25 am
How can you be annoyed at a FREE open source service? Most of the plugins that are built for wordpress are not officially supported by wordpress themselves. Its not wordpress’ responsibility to make sure their software works with all third party plugins. Its the job of the plugin makers to keep up surely??
September 26th, 2007 at 9:39 am
Thanks for letting us know. I was going to upgrade tonight, but forget it if 5 of my plug-ins aren’t going to work.
September 26th, 2007 at 9:47 am
@chris that’s like ford introducing a new line of cars that are 18″ wider than highway lanes because it’s an improvement, and saying it’s not their fault governments have to repave roads to accommodate them.
September 26th, 2007 at 10:24 am
Wordpress was checked by Mysql company experts and stuff was optimized. Maybe this has something to do with it?
September 26th, 2007 at 10:35 am
Wordpress is still great, I’m sure most of the plugins will get updated reasonably swiftly.
If not, then a plugins probably obsolete/dead anyway.
September 26th, 2007 at 10:38 am
Man I thought I lost my blog yesterday trying to upgrade. Backup .. backup .. backup…. 2.3 does suck. I had more errors than… you know what.
September 26th, 2007 at 11:35 am
I updated 3 blogs last night without a hiccup. I don’t use many plugins, but then I work in niches that are small enough nobody would bother competing anyway, making the fancy stuff unnecessary. I haven’t noticed any differences yet, though.
September 26th, 2007 at 11:50 am
I have more than 50 plugins installed, and at one point I even had up to 90 installed.
Anybody wanna take a guess what would happen if I upgraded?
September 26th, 2007 at 1:22 pm
That’s quite a list they have there. Looks like a lot of work for the plugin authors. This is why I never upgrade immediately. A few days can make a big difference in knowing what it will take to successfully upgrade.
September 26th, 2007 at 1:26 pm
It’s open source. Why don’t you get off your ass and update the plugins your using to be compatible with the current version of wordpress. If your using code that’s not part of the official core then you have not bitching excuse to be blabbing.
September 26th, 2007 at 2:42 pm
“One of the core philosophies of WordPress is to keep the core code as light and fast as possible but to provide a rich framework for the huge community to expand what WordPress can do, limited only by their imagination.”
http://wordpress.org/extend/
The giant title on this page is “WORDPRESS IS INFINITELY EXTENSIBLE”
September 26th, 2007 at 4:20 pm
Mike,
Your not serious are you? The natural evolution of software dictates that any existing app will likely change unless of course its perfect (have not seen one yet).
Your anger may be better directed at WordPress for not having an early release program for developers before the official release or better yet the developers for not updating their plugins immediately following the release.
September 26th, 2007 at 5:41 pm
>Your anger may be better directed at WordPress for not having an early release program for developers before the official release
Agreed that would absolutely be a better course of action. Most of the plugins I use that are broken have to do with DB tables changing or being eliminated, quite a PIA.
September 26th, 2007 at 5:48 pm
You ever seen the PHP model of the SMF message board platform? You can tell they really worked hard to make it easy to upgrade even with third party plugins. One click updates usually do the trick. It’s amazing and I only wish WordPress would follow a similar model.
As it stands now I can’t upgrade beyond 2.0.X because it’s simply beyond my capacity to do so. It took all my brain power to build my site on my own that I simply can’t do it all over again without resorting to expensive consulting. Besides, there is virtually no new feature I see from 2.1 on that can’t be replicated with a current plugin.
September 26th, 2007 at 6:53 pm
The plugins aren’t the fault of WordPress, though.
September 26th, 2007 at 11:34 pm
>Your anger may be better directed at WordPress for not having an early release program for developers before the official release
Agreed that would absolutely be a better course of action.
There were several release candidates before the official release of 2.3
Also, to echo other people’s comments, its ridiculous to knock plugin authors of an open source system.
Rather then berate wordpress or the plugin developers, I would suggest using your programming skills to help notify plugin authors where the issues are. Or if you don’t have the capability to help identify the issue, why not drop a small donation to a plugin author to help motivate to spend some time to fix the issue?
September 27th, 2007 at 12:22 am
or wordpress could do stop making “improvements” that break exisitng programs and we wouldn’t need to start this vicious cycle
September 27th, 2007 at 1:25 am
i think, the developers could make changes but improvments are very necessory. And as Douglas said herd party tools are not wordpress’s problem -:)
September 27th, 2007 at 9:57 am
i almost want to post my previous comment a second time. if it is wordpress’ goal to rely on the community to provide function beyond the “light and fast core”, then updates shouldn’t break the functionality to which they have dedicated the software.
September 27th, 2007 at 5:30 pm
I just chalk it up under “shit happens.” I can’t get too mad at someone that gives away something that good, for not running decisions by 3rd party add-on writers. Sure, it would be nice, though.
Personally, I keep a throwaway installation on a test sub-domain, that uses all of the plugins I use… and that’s where I test the upgrades.
I also give the good plug-in authors credit for jumping right in and getting things fixed, evolving along with WP. Same can be said for Firefox, when they break stuff.
I get what you’re saying, but that’s not really a good comparison, as WP didn’t create something that’s incompatible with the internet.
It would be more comparable to when a car manufacturer changes the body style. Should we be upset that door from an ‘86 Mustang won’t work on a new Cobra? And that’s an example of a company being incompatible with itself–not 3rd party add-ons.
So, you could take it a step further. Does a car company screw over the after-market companies with a body style change? A company could rake in the cash on a ground effects kit, only to find out the next year not one part of it will work with a new model.
That list can go on forever. How about when someone throws out a new rim or tire size? Should tire companies really have to make a 24″ tire for a Honda Civic, just because some idiot thinks it would look cool with 24″ spinners? haha
September 27th, 2007 at 7:18 pm
THis is why I always wait for the first service pack before using new software.
September 28th, 2007 at 12:13 am
Mike Seiler Says:
“Personally, I keep a throwaway installation on a test sub-domain, that uses all of the plugins I use… and that’s where I test the upgrades.”
Yes indeed.
http://beta.webmaster404.com/
September 29th, 2007 at 1:04 pm
well, may be they want to try a few things on wordpress anyway, when something is too popular they might try to learn some new things!
October 1st, 2007 at 12:41 am
Wow, thanks for the heads up. I was thinking about updating my blogs tonight, but had held off for some strange reason. Glad my intuition staid my hand.
October 3rd, 2007 at 3:23 pm
[...] Share This [...]
October 8th, 2007 at 11:20 am
you are talking about software.
plug in or 3rd party software maker need to make change their own when new operating system is coming. NOT main software need to make change for plug in or any 3rd party software. That’s insane.
October 11th, 2007 at 9:53 am
@Graywolf - Ford cars aren’t free the last time I checked mate