Tag

Wordpress

Browsing

I would like to state that who ever designed the widget interface in WordPress 2.5 is a complete moron. A retarded monkey could have done better. Gone are the days where you just drag and drop widgets. Have more than one sidebar or widgetized area? No problem, just drag the widgets to the corresponding widgetized area. No, in 2.5, you have to select which sidebar you want to edit from a dropdown, then add the widgets to that sidebar. Then you have to click save and choose the next sidebar from the dropdown. Oh wait, you want to move something from sidebar 2 to sidebar 1? Ok, instead of dragging and dropping like you did before you have to go to sidebar 2, remove it, save, go to sidebar one, add it, save. What a pain in the ass. EDIT: Also, if you go to a theme that has less sidebars than your previous, the widgets mess up. It’ll display whatever widgets you have in sidebar 1 from the previous theme, but when you change it and hit save, it removes them all and puts widgets from sidebar 2, making you do the whole process over again.

One of the things that has bugged me over the past year or so with WordPress is that the community seems to be disappearing. Some of the developers have left to create other software and some have just left. It seems the passionate group of volunteers that helped support WordPress have moved on as well. The WordPress IRC channel was once a place I enjoyed hanging out in and helping whenever I could. Now, I never speak in there. I hardly look at what’s being said in there at all. Some of the volunteers that helped out in the forums have even been asked to leave by Matt and company. Matt seems to be doing a great job at driving a wedge in the community. His way, or leave. Or as he once put it, you don’t like it, fork it.

Themes.wordpress.net is pretty much a graveyard. I used to go there several times a week to check out all the nice new designs that people were making. Even if I wasn’t ever going to download the themes it was nice to see what was being produced. Now the only place that publishes new WordPress themes on a regular basis seems Weblogtoolscollection.com, and that has even seemed to slow down a bit. I don’t know if that’s because passionate theme developers aren’t producing themes anymore or what. Now your choice is to use Google and hope you don’t find a site that puts malicious links and/or code into the theme you download.

The latest thing that Wank pointed out is that the Plugins page on the Codex no longer exists. It was a fairly complete list of plugins for WordPress. It’s no longer there. So if Matt chooses to tell you your plugin isn’t good enough for the official repository, there’s no place to notify users that your plugin exists. That page on the Codex was a great page. Also absent from Extend is the link for themes. It was there before 2.5 came out. So, Matt takes away the theme repository, has the plugins page deleted, drives away developers and volunteers and this is supposed to be a community? Yeah, right.

As you probably know by now if you’re a WordPress user, WordPress 2.5 came out today.  Along with that, WordPress.org received a redesign.  I won’t say much about the new version, as it seems to be the same, except an ugly admin redesign.  I will however point out that I have a new theme up here.  It probably won’t stay up too long, but I figured it’s a great theme for the season.  Cardinals opening day is Monday and the baseball season will be underway.  Just wanted to throw up a theme that celebrated the season a bit and this theme I thought was very elegant looking.  Anyway, let the baseball commence!

I’m back to using WordPress for now. This is nothing against Habari. I’m just not ready for it. I spent several hours for a few days trying to get things to work the way I wanted them to. The Habari community was extremely helpful and I wouldn’t have gotten as far as I did without them. My thanks to them. I just felt bad constantly asking for help. I’m not a coder. I manage to get by. I also had to constantly modify themes to get them to work (or to get them to work how I wanted them to work) and to look right in various browsers. I’m still excited to use it, but it will probably be a bit before that happens, not because their product isn’t stable, but because I’m not. ;)

Dmondark in #habari did me a huge favor and ported the wordpress audio player plugin. That was essentially my last major hurdle I had to overcome in order to switch to Habari. I already have an install up and running with all my blog posts and plugins. Everything seems to be running smoothly. So, this weekend, I may be moving the blog from WordPress to Habari. If I do move, I’ll have a new feed address, so make sure you stop by the site to get the new address so you can update your feed readers.