Content Management System (CMS) News, Reviews, Events and Analysis.
 
 
 

WordPress 2.8 Out, Raises Usability Bar for Drupal 7

WordPress 2.8 Out, Raises Usability Bar for Drupal 7What ho! Is that a new version of WordPress (news, site)  we spy?

The answer is yes. But of course, you probably knew already; WordPress 2.8 was released for immediate download toward the end of last week. Just like most seasoned blogging platform fans, we’ve come to expect big things from the system. This time, the newest version not only fits the usual bill, it also presents some pretty stiff competition for other platforms like Drupal.

World, Meet Baker

Named after the late trumpeter and vocalist Chet Baker, Wordpress 2.8 is certainly all jazzed up. After some tinkering, a few tweaks here and there, and over 790 bug fixes, “Baker” is being described as “a nice fit and finish release for WordPress with improvements to themes, widgets, taxonomies, and overall speed.” Let's look at the major updates in detail:

  • Speed: A change in the way WordPress handles style and scripting has reportedly made the system way faster.
  • Redesigned widgets interface: For everyone who’s ever been frustrated with widgets, WordPress 2.8 has attempted to answer your prayers. The new interface allows users to do edit widgets on the fly, have multiple copies of the same widget, drag and drop widgets between sidebars, and save inactive widgets without losing all of their settings. Additionally, developers now have access to a spiced up API for creating widgets.
  • Theme Browser: This feature is where it’s at. With the new theme browser users can search for themes based on colors, their preferred number of columns, and a fixed or flexible width—all from the dashboard. Whatever filters through based on these criteria can then be selected and installed with a single click of the mouse. For the tweak-happy, (that is, those of you that like to edit themes and plugins yourself), version 2.8 features a new CodePress editor, which gives syntax highlighting to the previously-plain editor.
     

Want to see these features in action? Check out the video:

 

 

Drupal's Baked?

There are more fun features, of course. To be exact, over 180 changes, upgrades and improvements are along for the 2.8 ride, but let’s go back to that nifty little theme browser, and what we think it means for the other fish in the sea.

Coincidentally, just a day before WordPress announced their new baby, Jacob Singh, a member of the Acquia staff, noted on the team’s blog the problems with installing or editing themes in Drupal. He writes: “When the average Drupal site owner without ssh, cvs and other geek gadgets wants to update modules on or themes on their Drupal site, they currently have to do the following:

  1. Go update status and see the mod is out of date
  2. Take the site offline
  3. Make a backup (if they can)
  4. Know where to find the module on d.o., download the tarball
  5. Unzip the tarball
  6. Remove the current directory
  7. Use FTP to upload the new directory
  8. Run update.php”

Eight whole steps is a far cry from WordPress’ new plug-and-play functionality, isn’t it? Not to mention the amount of technical know-how it requires. For the technically challenged, it appears that working with themes in Acquia’s Drupal is akin to scaling K2: scary and very, very difficult. This is certainly a major turn off for the growing number of automation fanboys and fangirls.

Like we’ve said before, “If Web developers are going to be eliminated…it's going to be courtesy of hosted (SaaS) solutions with pluggable component architectures and point and click presentation themes.”

This nugget of knowledge is in no way beyond team Drupal. To prove it, Singh also makes mention of a project he’s working on called Plugin Manager (for details, head on over here). Unfortunately, working such a tool into Drupal’s core has presented some issues, which Singh also covers. But hey, at least they’re trying.

Meanwhile, WordPress is still one step and full steam ahead, and their developments will certainly push the other guys to either kick out some magic of their own or fall to the wayside. Do you think they stand a chance?

 
Read More About:
, , , , , , , ,
 
Was this article useful?
 

10 Reader Comments

1 | Jacob Singh — June 17, 2009 7:31 AM

Hi Chelsi,

Interesting writeup on WordPress and their new release. You certainly seem very enthused about it. Being a WordPress user myself for my tiny blog, I will most likely check it out sometime.

I wanted to correct a couple things about your mention of Drupal's “plugin manager” project, its status and its intentions.

1. “For the technically challenged, it appears that working with themes in Acquia's Drupal is akin to scaling K2”

I think that's a false analogy and any research into the matter shows it isn't all that scary, but a more important point is that Drupal is not “Acquia's Drupal”. It is just Drupal, Acquia doesn't own the Drupal source code, and has no more say in the direction of Drupal than anyone else who puts time in. Drupal is, and will remain, a true open source project. Acquia is a services and support company structured around Drupal.


2. The Plugin Manager project - http://drupal.org/project/plugin_manager was led by Joshua Rogers (who is also w/ Acquia now). This is an add-on module which, once installs allows in-site GUI installs of modules for Drupal 6. It has been available for months. Not sure if you knew that.

The issue referenced above is related to making this functionality a part of the Drupal 7 release itself, not as an add-on. Many people are working on this, most notable Charlie Gordon who initiated the drive in the first place.

you also wrote:
“Unfortunately, working such a tool into Drupal's core has presented some issues, which Singh also covers. But hey, at least they're trying.”

There are no issues working it into Drupal core.
The main thing we are trying to overcome technically is something which I believe wordpress does not do, which is ensure that the add-ons downloaded from wordpress.org are authentic and not tampered. This is a major security concern, and package signing (like you will find in GNU Linux distros), is a very important part of such a system, and we don't want to launch without this in place.

If a server in between yourself and the provider of add-ons is compromised, or you are subject to a XSS attack without package signing, a hacker would be able to install and run code on your site. We'd like to take it a little slow, and make sure we get it right, even if it means being “one step behind”.

Thanks for the mention and I'll be sure to follow up when we get the plugin manager done to send you a demo and get your feedback.

Best,
Jacob

2 | Mike — June 17, 2009 7:52 AM

Let's be clear.

If you want a blog, use WordPress or Movable Type (or whatever).

If you want a community-centric site, use Drupal.

If you want something in-between, do a bit more research.

To say that WP is one step ahead is somewhat crass in this context.

3 | Jake — June 17, 2009 1:16 PM

In what way is that clear? The recent updates to WordPress (and now BuddyPress) make WordPress useful for a lot more than weblogs.

4 | fred — June 18, 2009 8:27 AM

what gets done in drupal that doesnt get done in wordpress? beside a 6 figure development bill?

5 | Steve T. — June 18, 2009 10:39 AM

The old addage “Time is Money” holds particularly true in the fields of web freelancing, contracting and development. Wordpress holds the edge on Drupal when it comes to rapid development, deployment and end-user-friendliness. Given the state of the World's economies, it' obvious that Wordpress would best Drupal as the choice for blogs and CMS's (like news sites).

I'm surprised at how often Joomla flies under the radar in situations like this, though. Once you move beyond simple blogs and editorial based news sites, Wordpress's limits *really* show. But whereas many would assume Drupal as the logical option, Joomla 1.5.x (and soon 1.6.x), is actually superior based on the afformentioned criteria. With the advent of Joomla 1.6, I fail to see why anyone would want to persue the convoluted development and maintenance present with Drupal.

Of course, I only speak for myself here. What drives me towards Joomla is what I have been able to achieve with it. What keeps me going is how straight-forward the framework is (to me), how rapid development can be, and how my performance (measured by what I have been able to produce) measures against my peers (*superior* and *faster*).

I digress. Wordpress is fast becoming (if not already) an industry standard. The measure of open source software is in the strength and profitability of the community which drives it's development. In that case, Wordpress is a winner.

6 | Matt K — June 24, 2009 2:13 PM

i have to agree with mike. if you want a blog, use wordpress or one of the other many blogging platforms. but once you try to move beyond a blog using wordpress, it becomes painfully obvious how limited wordpress is for much past a blog. it just depends on what you're trying to build. in my case i use drupal day in and day out (and i spent 3-4 years with wordpress prior to now) and i love it.

7 | Samson — June 28, 2009 10:10 PM

Drupal despite its content creation advantages has some serious problem when it comes to true social-net based community sites. Despite massive requests over the last 2 to 3 years they have not solved or shown any eagerness to solve this. It is almost hell as impossible to do in Drupal what WordpressMU+Buddypress (or for that matter Elgg) can do almost out-of-the-box.

If you are not concerned with the following factors Drupal is not a problem for you.

TEN FACTORS YOU NEED BE AWARE ABOUT DRUPAL

1. Drupal has no concern for Privacy. You cannot hide your online status or decide to show them at will. Either it is on for all users or it is off for all users.
2. Abuse control - The Abuse module has threshold set to hide content when say, for example, 10 users report against a content it is supposed to get hidden. Now if you have Views ( a plugin to build up topic lists and display) the hidden topic still shows up. The two plugins or modules do not talk to each other.
3. Blocking an user - Very imperfect! Blocked users can still pester you by PM. Either you put PM totally on or totally off - you cannot block a single user completely
4. RSS - the site admin cannot put off RSS. The users have no choice top put on or off RSS of their own posts.
5. No decent image gallery. All the forum posts and support sites like Lullabot will say you have to download and upload at least five to six modules, write codes or import codes and a lot of fuss. Simple album for each user on your site - no easy Drupal way
6. Out of the box easy to manage Social Profile like Buddypress, Elgg or Dolphin Boonex - Forget it in Drupal!!
7. MULTIPLE BLOGS per user - you can configure Wordpress MU to have as many blogs as an user wants. This is simply impossible in Drupal
8. Search - Drupal does not rely on its own Search they pack with the core. They use a Java search instead. Most hosts do not support php and java together. Acquia sells it as a service. Very weird.
9. Drupal support community, apart from a stony dull face, says these things regularly “too many posts for us to handle” “users do not contribute” “code yourself” “pay someone to get things done” - whether this is good or bad is up to you
10. “Drupal may do this or do that, Drupal X will bring the star and moon for you, so many works are going on” but all that is in FUTURE, by that time WP may have advanced more. So, if you are concerned with the time called NOW…

8 | Zachary — June 30, 2009 12:45 PM

Or, they are tools that work or do not work well in a problem domain. None is better or worse. There, end of story. Drama about software: meaningless.

I will note, however, that an advantage Drupal and Joomla have over Wordpress is the CiviCRM module for non-profits. So see, its not that they are better or worse, its just they are different tools. Or, maybe its just an issue of personal preference, or what makes sense to different people. I like Drupal's slogan, “Community Plumbing”. When you plumb a house, you put the pipes where they need to go, one by one. Sometimes you have to do a little hack to get a result (writing or extending code). Its made from this perspective mostly, not to please people who are superficially design oriented, and who have no training in taking the time to learn a highly customizable framework. This is our problem in America right now - laziness and blaming others for our own shortcomings in learning.

9 | Albright — July 1, 2009 7:32 PM

Drupal's current UI development works are being done in a Wordpress blog http://www.d7ux.org/ - what more can be said? Many of the Wordpress features are being “feature-lifted”, maybe under new skins, to combat market share losses to WP. However, as pointed one post above, no one is attentive to the lack of features like Wordpress MU or Buddypress. And unless features are there it will be a like house with no rooms but beautiful doors and windows!

10 | nomad — January 13, 2010 3:21 PM

I would like to see Wordpress take the reigns and become what Drupal should have become. It's painfully obvious that Drupal will not become more like Wordpress so instead of wishing and hoping for Drupal, focus on Wordpress's future instead. Drupal is for programmers who are happy to spend hours and hours with site issues. Wordpress is about simple and fast and getting it done and then going to the beach.

The one thing I hate most about Wordpress is their need to attach wp- to every line of code and every file, wtf is up with that ? I usually strip clean every trace of wp- before I install.

Leave a Response

  Remember me?

Related Web CMS Articles

 

From our Job Board  View all jobs | feed Jobs RSS feed | Post a job right now

 

Featured Events  View all events | feed Events RSS feed | Add your event

STAY UP TO DATE
Subscribe to our RSS feed...
SUBSCRIBE TO OUR RSS FEED