WordPress Planet

December 27, 2009

Weblog Tools Collection: WordPress Plugin Releases for 12/27

New Plugins

HDLNS Today

Automatically insert HDLNS headlines as a widget using the post date.

Strip Ad

Add a Strip Ad above the header to your blog.

Code Comments

Automatically Escape HTML Entities of Code Fragments in Comments

Updated Plugins

Top 10

Count page views on posts and display a list of top posts by page views.

Contextual Related Posts

Display a list of contextually related posts for the current post. You can select the number of posts to display and if you want to automatically display the related posts in your content / feed.

Where did they go from here?

This plugin will show “Readers who viewed this page, also viewed” links on your page. This is similar to Amazon’s product pages which state “Readers who have bought this, also bought”

WP-Table Reloaded

This plugin enables you to create and manage tables in the admin-area of WordPress. You can then show them in your posts, on your pages or in text widgets by using a shortcode.

WatchCount.com WordPress Plugin (WCCWPPI)

The WatchCount.com WordPress Plugin (WCCWPPI) is a free plugin that allows you to display Most Popular eBay items and auctions in real-time, directly on your blog. You can also display eBay items from any particular seller.

Shout Stream

Shout Stream plugin aims to be the bridge of your wordpress and your stream (shoutcast or icecast).

by Perurry at December 27, 2009 01:22 PM under WordPress

December 26, 2009

Matt: Fireside Chat

In New York last month I did a fireside chat with Liz Danzico at the School of Visual Arts which is now available online. The video features myself, Liz Danzico, and the back of Jason Santa Maria’s head.

by Matt at December 26, 2009 09:58 PM under press

Matt: Veggies are People Too

Another Challenge for Ethical Eating – Plants Want to Live, Too in NY Times. I eat lots of beef and BBQ because I heard cows have a big carbon impact.

by Matt at December 26, 2009 06:11 PM under Asides

December 25, 2009

Matt: Christmas Site Updates

First off, Merry Christmas everybody! I’ve been doing some tweaking here around ma.tt. The biggest thing you’ll notice is that I’ve imported about 12,000 photos from my old Gallery-powered gallery, which was broken since I upgraded to PHP5, into core WordPress, and you can see them under this category. I even managed to bring over people tags and comments from the proprietary system I had written. I feel so much safer now that all this data is in WordPress, I know it’ll still work in 10 years. I might have to change how “random” works, though, to exclude the really old photos though, because they can be fairly embarrassing. :)

by Matt at December 25, 2009 11:47 PM under Meta

Weblog Tools Collection: Merry Christmas and Happy Holidays to all!

merry christmas

Merry Christmas and Happy Holidays! from Flickr

We would like to wish all our readers a Merry Christmas and Happy Holidays from the Weblog Tools Collection team and our advertisers.

Be safe, have fun and be sure to spread the cheer!

by Mark Ghosh at December 25, 2009 10:03 PM under LinkyLoo

Dev Blog: Setting Scope

Merry Christmas! One of the things that was discussed at the core commit team meetup was release scope (and scope creep). Now that 2.9 is out and it’s time to start thinking about 3.0, we think it would be appropriate to stop and take a breath before diving in, and make a plan in advance. What winds up happening is that during each release cycle a few new features are selected for inclusion, but then right up until feature freeze (and/or beta cycle), people keep adding feature requests, patches for enhancements, and ongoing bug reports. This means each release winds up getting pushed out later than planned, and with so many things going in per release, it becomes harder to catch new bugs.

The as-long-as-we’re-not-in-freeze-yet model isn’t working. People wind up waiting months longer for new features they want, like Trash and Image Editing, because we’re still adding other things and then we need to test them all. If we kept the releases smaller feature-wise, we could push out the new stuff sooner (3 releases per year is the goal) and have more focused beta testing, making the releases themselves better. It’s hard, because everyone has their pet features and fixes, and if there’s a patch, why not get it in this release rather than waiting? Sometimes people complain that a patch has been waiting to be committed for weeks or months, but what no one ever seems to bring up is that sometimes patches introduce new bugs, and the more we add at once, the harder it is to keep it all well-tested on various platforms, in different hosting environments, etc. So. What’s our proposal?

We take a page from the world of project management and we make a project plan before we jump into the dev cycle. We let everyone propose features and enhancements, and we choose a limited number to include in 3.0 (in this case we need to be especially stringent, because the merge of WordPress and WordPress MU will automatically mean a lot of work) and set a realistic release date that we stick to. We create a tentative set of features for the next two releases, to be re-evaluated at the beginning of the next cycle, so that people know the community is committed to certain features, as opposed to the vague “future release” label we now use for everything not included in the current version. We fix bugs that are reproducible and affect a large number of users before focusing on edge case bugs or bugs that haven’t been well-described or reproduced. We stop diverting our attention from agreed-upon goals when a “squeaky wheel” decides we should all be focused on something else. There are always things that pop up unexpectedly, but we need to do a better job of restraining ourselves when it comes to trying to sneak things into the current release (I include myself in this, of course…as a UX person I always wish we could do everything all at once!).

As an open source project, we accomplish more when we work together than we do following individual agendas, and we need to keep our project focused on commonly-agreed-upon goals instead of following tangents whenever a community member starts to take us on one, regardless of whether it’s to follow a cool idea that everyone loves or a suggestion based on a personal agenda, and regardless of whether it’s a newbie who doesn’t know any better or a frequent contributor or committer who has a strong opinion and a loud voice (so to speak). The issue here is that it’s easy to get distracted, so we need to create a structure that will help us keep moving forward instead of getting sidetracked. We need to keep Trac clean for the current dev cycle so that it includes confirmed features and bug reports, and all new feature suggestions go into a different milestone.

We think it’s at least worth a try. When we re-start the weekly IRC dev chats in 2010, the first meeting will be to talk about the scope of 3.0. When we’ve got a general agreement about what will be included, we’ll create the appropriate Trac tickets, and punt tickets for non-3.0 feature requests/enhancements to a future release so we can stay focused. New bug reports will still come in to the current milestone. It’s going to be hard. There are at least a dozen new features that I feel like we’ve pushed back multiple times that I’d like to see in core, but for this experiment, I’m just going to keep reminding myself, “You can do that with a plugin!”

Sound off on the features you would like to see in version 3.0.

by Jane Wells at December 25, 2009 04:56 PM under Development

December 24, 2009

Weblog Tools Collection: WordPress Theme Releases for 12/24

blutheme

blutheme

Feature rich theme with support for thumbnails, feedburner, twitter, widgets and gravatars

Crispp

Crispp

Crispp is a minimal theme with clean lines that lets visitors focus on your content. A separate administrative section allows you to change the color scheme however you like. The theme is very flexible

Insanitious

insanitious

Fluid width two-column theme with widgetized sidebar, gravatar and comment ready

Dusty City

DustyCity

Dusty City is a WordPress Theme with 5 Sidebar / Widget positions. One below the navigation, one left and right, one between them, and one at the bottom. If you combine the Theme with the Side Posts Plugin, you will have a great flexible Magazine Theme. There is also an Option Page to populate the Footer. Page in German

Santa

SantaTheme

SantaTheme is a WordPress Theme for Christmas with one Sidebar, and one Footerbar for Ads or whatever Widget you want to place there. There is also an Option Page to populate the Footer of the Blog.

Elegant Blog

Elegant Blog

Elegant Blog is meant to be a go-to theme for a content driven site, that aims to eliminate the need for some common plugins and be good to go right out of the box. There’s 7 colour schemes available to choose from and an easy to edit css file to add custom colours. There’s also built-in support for Twitter, various social bookmarking sites, and Google Analytics.

by Perurry at December 24, 2009 05:20 PM under wordpress themes

Weblog Tools Collection: WordPress 2.9.1 Beta 1 Released, Fixes Bugs in WordPress 2.9

A few days back, Jeff had told you about WordPress 2.9.1 being around the corner. The WordPress team has worked hard to get it out of the doors and a beta version of WordPress 2.9.1 is now available for downloads. It fixes bugs with scheduled posts and pingbacks which some users had been facing, due to a bug in curl.

The new version is not immediately available for downloads through the automatic upgrade, however you can download the WordPress Beta tester plugin and go to Tools->Upgrade and perform an automatic upgrade.

Please remember that this is not the final WordPress 2.9.1 release, so you might want to wait for another day or two for a stable release, if you are not comfortable using beta versions.

by Keith Dsouza at December 24, 2009 03:36 AM under WordPress 2.9

Weblog Tools Collection: Trend For 2010 – Paying For Plugins

While paying for plugins is nothing new, I’m predicting that by the end of 2010, there will be a large assortment of plugins for WordPress that will be available for purchase. As we wind down 2009, I’m already beginning to see the trend in action with at least 3 of my 31 installed plugins switching to a paid model. Each person is doing something a little different but the end result is the same. I have to pay to keep using it.

Now I don’t particularly have a problem with plugin authors charging for support or for services around the plugin but I’m seeing the plugin being bundled as part of the purchase. So in a way, you’re not only paying for the plugin, you’re paying for access to support. In most cases, the free plugin becomes dormant and I’m forced to either stick with what works until a version of WordPress is released which breaks the plugin or I pony up the cash to receive upgrades. Shopp, GravityForms and now Ajax Edit Comments each have their own repository server that enables customers to receive upgrades. This is all part of the deal.

I remember a post a year or so ago asking people what would they pay for that they currently did’nt have to. WordPress was one of the things people would pay for if it had a price tag. My question is slightly different. What if every plugin you use on your site requires you to pay money before you get access to upgrades, support, etc? Personally, I don’t mind paying for great work and I can part with my cash for three or five plugins but not for 31.

Not to put down the work of those making a business out of their plugin but something to keep in mind is that as it stands, plugins hosted in the WordPress.org plugin repository contain no price tags. However, some of them do have links, wording, and such to up-sell services or the pro version of the plugin. I don’t have a problem with that as long as the slimmed down version is not crippled to the point where it doesn’t make sense to use the lower end version.

If the authors of the plugins I use on my own site all decided to ditch the free version in favor of a paid model in order to help them make a living, that is their decision to make. However, one of the greatest assets of the WordPress plugin world is that there is an abundant amount of choices for most tasks. Some better than others.

My hope is that the WordPress plugin repository will continue to be free of pay-for plugins. This will insure that I will always have a place to browse an assortment of free alternatives. If the plugin repository were to ever allow commercial plugins to be listed alongside free ones, I’m thinking that the commercial choices would far outweigh the free ones. I really don’t want to go down the road I traveled with Joomla where anytime I wanted to have cool functionality added to my site, I had to pay for it.

Is this a trend you also see in 2010 or do you see something else? Any thoughts on the matter?

by Jeff Chandler at December 24, 2009 12:10 AM under plugins

December 23, 2009

Matt: Everything is a Project

Everything is a project, even this, by Scott Berkun.

by Matt at December 23, 2009 11:29 PM under Asides

bbPress: 2009-12-23 Meetup

What, just because it’s two days before Christmas we can’t rock the bbPress? In summary: anonymous comments from filosofo and email from photomatt (me) on deck, bug fixes to make things sing, PeteMall will be directly committing fixes, and hajii will be bug gardening.

Meetup log after the jump:

[13:01] <photomatt> <meetup>
[13:02] <photomatt> merry christmas everyone :)
[13:02] <filosofo> merry Christmas, photomatt :)
[13:02] <photomatt> what is everyone up to these holidays?
[13:03] <hajii> workin :-)
[13:03] <filosofo> Visiting the in-laws
[13:03] <filosofo> photomatt, didn’t you write bbPress over Christmas? If I’m remembering correctly.
[13:04] <photomatt> yep, 4 years ago?
[13:04] <photomatt> 5?
[13:04] <photomatt> I was young and foolish
[13:05] <hajii> young-ER
[13:05] <photomatt> ha ;)
[13:05] <hajii> anything on the agenda this week?
[13:06] <photomatt> I cut my teeth yesterday, silly fix
[13:06] <photomatt> some error notification stuff with 5.3
[13:07] <photomatt> so now you don’t see a page of white errors when trying to install
[13:07] <photomatt> but on the bright side I got my bbpress env all up and kicking
[13:08] <filosofo> So what’s the roadmap for bbPress development? How can we get things moving?
[13:09] <filosofo> For example, should we start tackling the conversion to wp canonical plugin?
[13:09] <photomatt> my todo for the holiday is 1 thing: email notification
[13:10] <filosofo> There’s a plugin already for that, right?
[13:10] <filosofo> Can you just roll in the code?
[13:10] <westi|gone> howdy all
[13:11] * westi|gone is now known as westi
[13:11] <filosofo> hello westi
[13:11] <photomatt> filosofo: buddypress has a pretty good integration method already
[13:11] <photomatt> filosofo: do you have a fav plugin for it? could just roll in code
[13:11] <westi> photomatt: did you see my note regarding your first 5.3 related change – I think you might have broken the PHP4 compat of the code before you had the right error hiding
[13:12] <filosofo> photomatt, I haven’t used email notification on bbPress, I just know of the plugin[s]‘ existence.
[13:13] <hajii> What is 5.3, the PHP Version 5.3 where people where getting warnings?
[13:13] <hajii> -h
[13:13] <westi> hajii: yes PHP 5.3
[13:13] <photomatt> westi: yes, the glotpress and backpress changes?
[13:13] <photomatt> I shall fix those
[13:13] <westi> photomatt: yes those
[13:14] <hajii> Can I propose a plan of attack?
[13:14] <westi> my tentacles don’t stretch far enough to revert them ;-)
[13:14] <filosofo> photomatt, what are your thoughts about buddyPress / bbPress integration? Are you thinking of doing that instead of making bbPress a canonical plugin?
[13:14] <photomatt> they’re not mutually exclusive
[13:15] <photomatt> have you tried out the buddypress integration? I didn’t realize it had gotten as good as it has
[13:16] <filosofo> What makes it different from a non-BuddyPress WP/bbPress integration?
[13:16] <photomatt> they basically embed/bundle the whole thing
[13:19] <photomatt> I’m pretty chill about 1.1 specifically, I think it can be a feature or two, and a cleanup of trac
[13:19] <PeteMall> ok I’m late
[13:19] <photomatt> I guess I’m a little scared of the plugin-thing so I’m procrastinating :)
[13:19] <hajii> I vote no new features, fix what is included first
[13:19] <hajii> maybe it’s 1.0.4 (or 3 or whatever we’re at)
[13:20] <hajii> hpguru opened a bunch of trac tickets recently pointing out things that are included that just don’t work correctly
[13:20] <filosofo> I was thinking bbPress as plugin integration would mean, e.g., using WP custom post types, or the like, instead of bbPress’s separate table structure.
[13:20] <filosofo> Or maybe like P2
[13:21] <filosofo> bbPress "posts" as WP comments on "forum" WP posts
[13:22] <photomatt> hajii: links? which do you think are the most important?
[13:23] <photomatt> I’m down with "no new features before bugs" in principle
[13:23] <PeteMall> photomatt: r u the only one committing to trac now?
[13:23] <PeteMall> I’m gonna work on a few tickets this week
[13:24] <PeteMall> christmas shutdown is good for open source projects
[13:24] <photomatt> yep :)
[13:24] <photomatt> if you’ve got some stuff you want to knock out I can give you SVN access too
[13:24] <photomatt> it’s easy peasy right now
[13:24] <PeteMall> that would be nice
[13:25] <filosofo> Regarding bbPress / WP integration, it would be nice to be able to use WP template functions for bbPress.
[13:25] <PeteMall> photomatt: u manage mullenweg.com right?
[13:25] <filosofo> I don’t think you can do that with the buddyPress stuff, right?
[13:25] * Salt is now known as Salt|afk
[13:25] <photomatt> yep
[13:25] <PeteMall> pm
[13:26] <hajii> for the record, I think the "
[13:26] * Thomas_Clausen (n=Ejer@1010ds1-rdo.0.fullrate.dk) has joined #bbpress
[13:26] <hajii> feature poll" was a bad idea.
[13:26] <hajii> open a can of worms
[13:26] <hajii> bug free == feature
[13:27] <filosofo> hajii, asking for suggestions isn’t the same as taking them :)
[13:27] <photomatt> exactly
[13:27] <photomatt> and perhaps we’re religious on a few things, I’m pretty anti-bbcode, for example
[13:27] <hajii> that’s true. But it’s also demoralizing to some people to give feedback and then never see it go anywhere
[13:27] <PeteMall> lol
[13:27] <hajii> not me, for example
[13:28] <hajii> but, people will EXPECT after submitting their suggestion in a feature poll
[13:28] <PeteMall> so whats the long term plan wrt to close wp integration as filosofo has been talking about
[13:28] <photomatt> hajii: I tried to make it clear it was feedback-oriented, not necessarily a edict
[13:28] <filosofo> hajii, same thing with http://wordpress.org/extend/ideas/
[13:28] <photomatt> speaking of that though, I was really surprised by "anonymous posting"
[13:29] <photomatt> what exactly does that mean?
[13:29] <filosofo> you don’t have to log in, like wp comments
[13:29] <photomatt> I mean I know, but I don’t understand the why I guess
[13:29] <hajii> some people feel that asking people to log in is a barrier to participation
[13:29] <filosofo> why do you see it as different from WP comments?
[13:30] <hajii> some people feel facebook connect will also remove a barrier to participation
[13:30] <filosofo> You don’t require commenters to log into ma.tt to comment, for example
[13:30] <PeteMall> alter egos of forum members
[13:30] <photomatt> interesting — that wouldn’t be too hard
[13:30] <photomatt> we’ll need better anti-spam and moderation though
[13:30] <filosofo> I have a bbPress plugin for "anonymous comments" that’s 98% done
[13:30] <hajii> that is/was a plugin as well, anonymous posting
[13:31] <photomatt> filosofo: could you put it as a patch on trac?
[13:31] <filosofo> sure
[13:31] <hajii> better moderation (forum specific) is the oldest ticket on trac, I think :-D
[13:31] <hajii> one of the two oldest anyway
[13:31] <photomatt> hajii: I’m a big believer in moderation — it’s my fav feature in WP
[13:34] <photomatt> did my connection drop?
[13:34] <filosofo> photomatt, for future reference, what’s the best way to get your attention for a trac ticket?
02[13:34] * tewwy_ (n=tychay@208.80.69.102) Quit
[13:35] <filosofo> since you’re the committer :)
[13:35] <PeteMall> everyone got quiet =)
[13:35] <photomatt> filosofo: skype, actually
[13:35] <photomatt> saxmatt02 is me on skype
[13:36] <filosofo> So you don’t mind if I ping you about a patch on skype?
[13:36] <photomatt> for bbpress, not at all
[13:36] <filosofo> ok, cool
[13:38] <PeteMall> anything else on the agenda for today?
[13:38] <photomatt> so it sounds like we have email notif and filosofo’s anon comments on deck
[13:38] <photomatt> hajii and PeteMall are into bugs, and we’ll go through trac
[13:39] <hajii> do you want me to do anything specific for those bugs in trac that currently exist?
[13:39] <photomatt> PeteMall has asked for direct SVN access
[13:39] <Thomas_Clausen> @PeteMall I’ll like to throw something in there!
[13:40] <Thomas_Clausen> Will porting posibilities from other forumsoftware be a concern in future releases of bbPress?
[13:40] <photomatt> PeteMall: the main rule is to put everything possible through trac, post patches there, get feedback and review
[13:40] <PeteMall> yup
[13:41] <photomatt> but in trunk we can be loosey goosey a little bit, the beautiful thing about SVN is it’s easy to roll back
[13:41] <photomatt> oh! and coding style
[13:41] <photomatt> http://codex.wordpress.org/WordPress_Coding_Standards
[13:41] <PeteMall> I’ve been meaning to talk about that
[13:42] <PeteMall> stick to the coding standards… remember – code is poetry
[13:42] <hajii> Wait, what was the slogan from 2weeks ago? We suck a little less with each release?
[13:43] <filosofo> Not sucking is the goal of all great poets. :)
[13:43] <photomatt> :)
[13:44] <photomatt> hajii: in trac I’d say most helpful is verifying bugs
[13:44] <photomatt> testing patches
[13:45] <photomatt> setting priorities and milestones
[13:45] <photomatt> being nice to new people that drop by, helping mentor them through getting a patch or idea in the right place
[13:46] <photomatt> generally what we call bug gardening in WP, though that is a weird term
[13:46] <photomatt> when you think about it
[13:47] <hajii> tending to the bugs, lovingly
[13:47] <PeteMall> yea… helping them grow. nurturing
[13:47] <photomatt> I like tummelling
[13:47] <photomatt> http://indexmb.com/tummling-have-you-heard-of-it/
[13:47] <hajii> like the dude who raised the moths in the silence of the lambs, kept them warm, fed them, gave them love
[13:48] <hajii> Death’s Head Moth
[13:48] <hajii> :D
[13:49] <filosofo> well, on that note… :)
[13:50] <photomatt> haha yes
[13:50] <hajii> heh
[13:50] <photomatt> that’s a good ending point, unless someone else has anything they want to raise
[13:50] <hajii> nope, I will focux on bugs
[13:50] <hajii> in trac
[13:50] * Guest3427 is now known as Nightgunner5
[13:51] <photomatt> well thank you everybody
[13:51] <PeteMall> &lt;/meetup
[13:51] <PeteMall> ;)
[13:52] <PeteMall> missed the other side
[13:52] <photomatt> man the way mirc stores logs is annoying :)
[13:52] <PeteMall> &lt;&#47meetup&gt;

by Matt at December 23, 2009 10:10 PM under Meta

Dev Blog: WordPress 2.9.1 Beta 1

Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP’s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help us get 2.9.1 ready to go by testing 2.9.1 Beta 1.  The easiest way to test Beta 1 is to install the WordPress Beta Tester plugin, elect to get on the point release development track, and then perform an automatic upgrade via the Tools->Upgrade menu.  You can also download the Beta 1 package and install manually.  Fourteen tickets have been fixed in 2.9.1 Beta 1.  Since the curl problem and a couple of other problems are dependent on specific hosting configurations, any and all testing help is greatly appreciated.

by Ryan Boren at December 23, 2009 07:58 PM under Releases

Matt: Permanently Deleted

“The WordPress people, as good as they are, don’t seem to ken why this ‘convenient’ and possibly life-saving feature creates repercussions and consequences. Like the Senate, it’s all a game to them.” Permanently Deleted : Edward Champion’s Reluctant Habits. Hat tip: Joe Clark.

by Matt at December 23, 2009 06:02 PM under WordPress

Weblog Tools Collection: WPhone Admin Plugin Looking For Fresh Blood

My name is Doug Stewart and I, together with Stephane Daury and Viper007Bond, entered and won the “mobile admin interface contest” Matt Mullenweg sponsored on the wp-hackers mailing list back at the end of 2007. Our plugin, WPhone:

…creates an option while logging in to replace the default admin interface with one designed for your phone (see screenshots).

It contains two versions of the mobile admin interface:

  • Rich: designed for the iPhone / iPod Touch and other phones supporting full Javascript and CSS featuring fancy AJAX and sliding menus
  • Lite: a lightweight, simple version designed for all other phone types (no Javascript or anything else required)

WPhone was readily picked up by the mobile computing WordPressers of the world and saw a great deal of use in its first months. Then Automattic announced the release of their iPhone/iPod Touch app and we figured that WPhone’s days were numbered. However, folks have continued to use it, particularly on Blackberries, Nokia N-series handsets and yes, even Windows Mobile devices. This is great, with two caveats:

  1. WPhone doesn’t fully work with versions of WordPress newer than 2.5
  2. Stephane, Viper and I no longer have time to bring it up to snuff

So, to put it bluntly, we need your help in bringing a compelling mobile admin experience back to all mobile users, be they Droid, Pre, Blackberry, Windows Mobile, or yes, even iPhone users that don’t want yet another app clogging up their home screens.

If you’re interested, please visit this post over on the WPhone site for further details or send an email to batsignal@wphoneplugin.org.

Many, many thanks in advance and a big thanks goes out to Mark and the rest of the WTC crew for allowing me to post my plea here.

by dstewart at December 23, 2009 03:00 PM under WordPress Plugins

BuddyPress: What’s Coming in BuddyPress 1.2?

Development for version 1.2 of BuddyPress is beginning to wind down and we’re looking at a feature freeze at the end of this month. I’d expect the new version to be released some time at the end of January after a period of beta testing. We’ve got a host of new features to look forward to in this new version and I’d like to give you a glimpse of a few of them.

One of the biggest changes is the activity stream. There has been a lot of focus on making the activity stream far more interactive in 1.2, and to do this we have merged together some of the features in previous versions of BuddyPress. Instead of having to post messages on a group or profile wire, or posting a separate status update, you can now post messages directly to the site wide stream, your profile stream, or a group activity stream. This stops fragmentation of the interface and brings content posting into one unified input box.

One of the benefits of this interactive activity stream is that we can now provide the ability for other members to post direct replies to your updates. In 1.2 the activity stream includes the ability for threaded commenting. This allows for full conversations to take place around activities and makes the activity stream that much more of a two way process.

Another major update in 1.2 is the introduction of a new default theme. We’ve worked hard to produce a theme that will help both end users and developers. The new theme offers a more usable and unified interface with far more personal customization than the previous default. The theme also greatly simplifies the HTML, CSS and Javascript that powers it, allowing for greater ease of customization. If you’re fully invested in the previous default, don’t worry, this theme is not going anywhere and has already been updated to support the new features in 1.2. The new default simply provides a fresh alternative.

If you’re itching to start trying out some of the features in the new version, you can head on over to the BuddyPress Test Drive. The test drive runs the latest development version of BuddyPress and represents the state of the newest version as it currently stands. If you’d like to start working with the development version you can always check out the latest version from our svn code repository. However, remember that until the final version is released code is subject to change.

I hope everyone has a wonderful festive season and an even better new year celebration. 2010 is going to be an exciting year for BuddyPress, I’m looking forward to sharing it with you.

by Andy Peatling at December 23, 2009 09:09 AM under preview

Mark Jaquith: New in WordPress 2.9: Post Thumbnail Images


Many WordPress themes, especially those with “magazine-like” layouts, use an image to represent each post. It might just be on the front page. It might be alone, or alongside an excerpt. Until now, there was no standardized way to do this. Many themes would require you to tediously enter a Custom Field with the value being the URL you wanted to use. Often you had to do cropping yourself. With WordPress 2.9, theme authors can easily enable Post Thumbnail selection UI and call those image using simple template tags.

First, in the theme’s functions.php, declare that your theme supports this feature. This will enable the UI in the WP Admin.

add_theme_support( 'post-thumbnails' );

That will enable Post Thumbnail UI for both Post and Page content types. If you’d only like to add it to one, you can do it like this:

add_theme_support( 'post-thumbnails', array( 'post' ) ); // Add it for posts
add_theme_support( 'post-thumbnails', array( 'page' ) ); // Add it for pages

Simply remove the one you don’t want to support.

Next, you should specify the dimensions of your post thumbnails. You have two options here: box-resizing and hard-cropping. Box resizing shrinks an image proportionally (that is, without distorting it), until it fits inside the “box” you’ve specified with your width and height parameters. For example, a 100×50 image in a 50×50 box would be resized to 50×25. The benefit here is that the entire image shows. The downside is that the image produced isn’t always the same size. Sometimes it will be width-limited, and sometimes it will be height-limited. If you’d like to limit images to a certain width, but don’t care how tall they are, you can specify your width and then specify a height of 9999 or something ridiculously large that will never be hit.

set_post_thumbnail_size( 50, 50 ); // 50 pixels wide by 50 pixels tall, box resize mode

Your second option is hard-cropping. In this mode, the image is cropped to match the target aspect ratio, and is then shrunk to fit in the specified dimensions exactly. The benefit is that you get what you ask for. If you ask for a 50×50 thumbnail, you get a 50×50 thumbnail. The downside is that your image will be cropped (either from the sides, or from the top and bottom) to fit the target aspect ratio, and that part of the image won’t show up in the thumbnail.

set_post_thumbnail_size( 50, 50, true ); // 50 pixels wide by 50 pixels tall, hard crop mode

Now, you can make use of the template functions to display these images in the theme. These functions should be used in the loop.

has_post_thumbnail() returns true/false and indicates whether the current post has a manually-chosen Post Thumbnail (in the loop):

<?php
if ( has_post_thumbnail() ) {
	// the current post has a thumbnail
} else {
	// the current post lacks a thumbnail
}
?>

the_post_thumbnail() outputs the Post Thumbnail, if it exists (in the loop):

<?php the_post_thumbnail(); ?>

Those are the basics. How about some advanced stuff?

What if you want to use a small 50×50 hard-cropped image for the home page, but want to use a 400 pixel-wide (unlimited height) image on the post’s permalink page? You’re in luck. You can specify additional custom sizes! Here’s the code:

functions.php

add_theme_support( 'post-thumbnails' );
set_post_thumbnail_size( 50, 50, true ); // Normal post thumbnails
add_image_size( 'single-post-thumbnail', 400, 9999 ); // Permalink thumbnail size

home.php or index.php, depending on your theme structure (in the loop):

<?php the_post_thumbnail(); ?>

single.php (in the loop):

<?php the_post_thumbnail( 'single-post-thumbnail' ); ?>

That’s it! set_post_thumbnail_size() just calls add_image_size( 'post-thumbnail' ) — the default Post Thumbnail “handle.” But as you can see, you can add additional ones by calling add_image_size( $handle, $width, $height, {$hard_crop_switch} );, and then you use that new size by passing the handle to the_post_thumbnail( $handle );

If you want your theme to support earlier versions of WordPress, you’ll have to use function_exists() to keep from calling these new functions in those versions. I’ve omitted that code to keep these examples as simple as possible. Here would be the functions.php example with the wrapper code:

if ( function_exists( 'add_theme_support' ) ) { // Added in 2.9
	add_theme_support( 'post-thumbnails' );
	set_post_thumbnail_size( 50, 50, true ); // Normal post thumbnails
	add_image_size( 'single-post-thumbnail', 400, 9999 ); // Permalink thumbnail size
}

There is one caveat for this feature in WordPress 2.9 — it only works fully for new image uploads. We can’t yet resize images on the fly, although I’m strongly considering it for a future version. If you call the template functions on a post that has a Post Thumbnail that was uploaded prior to your theme having declared the new sizes, you won’t be able to do hard-cropping, and the box-resize will be done in the browser. As a temporary solution, Viper007Bond has a great plugin that will go back and create missing image sizes for you: Regenerate Thumbnails.

I’m looking forward to see what kinds of sites you can build with this feature!

by Mark Jaquith at December 23, 2009 07:19 AM under WordPress 2.9

December 22, 2009

Weblog Tools Collection: 2.9.1 Around The Corner

WordPress 2.9 was released last weekend. Yesterday, I was notified that 2.9.1 is most likely around the corner due to some issues that arose because of a last-minute addition to the core of WordPress. The issues revolve around scheduled posts not firing because the cron scheduler ends up broken. The patch can be found here which is already a part of 2.9.1.

While reading the support thread, I became concerned with some of the responses that were published. For example, “How could you release an upgrade that is obviously this problem-filled?” or “WordPress should have tested 2.9 before releasing it!“. I’m not sure how many times this has to be preached to the choir but each version of WordPress is tested before it’s release to the public. That is what the Beta releases are for as well as the Release Candidates. WordPress 2.9 went through one release candidate version and two beta releases. In fact, before RC1 hit the public, all of the tickets assigned for that version were closed. Each version was tested by anyone who volunteered. There seems to be this notion that there are thousands of WordPress developers and they should iron out every bug before releasing software to the public. While there are hundreds of WordPress developers submitting patches here and there as well as squashing bugs, not every hosting setup can be tested. This is where the end users come in.

Dion Hulse who has been a long time contributor to the WordPress project illustrates this problem quite well in a blog post entitled WordPress, A Call To Arms. I think Dion says it best in the first paragraph which illustrates the lack of testing problem quite well.

WordPress 2.9 was just released, And several users have run into a bug. Surprising? Not really. There’s one simple reason for this, While thousands of people Test each and every WordPress release, These users are not You.

While hundreds or thousands download the betas to perform testing, the real crux of the testing comes when the “Stable” release is shipped. The stable version is installed by everyone because it’s considered to be stable only since you now have hundreds of thousands of blogs running the software which translates into more testing environments, you’re going to run into bugs the testers simply didn’t find. This gives the perception that the Stable release was not stable at all and therefor, should have never been released. But, if the software were never released, the bug would most likely would not have been found.

Please Help Out:

It’s very easy to setup a test installation of WordPress, especially since the release of Peter Westwoods plugin called Beta Tester. While testing on a local server is a good idea, most local servers are not setup to mimic the configuration of the public web server. This is why it’s actually better to test on the same setup as your public facing site than on a local server.

Now, if you happen to come across something you believe to be a bug, please refer to this article in the Codex which contains instructions on how to report it.

by Jeff Chandler at December 22, 2009 09:11 PM under testers

Weblog Tools Collection: WordPress Plugin Releases for 12/22

New Plugins

HDLNS Today

insert one of over 1200 categorized RSS feeds, using the (latest) post date on the page to keep the rss headlined contextually relevant to the blog post

Q2W3 Inc Manager

This plugin was made to easily add html, css, javascript and PHP code to public WordPress pages.

Q2W3 Thickbox

This plugin enables thickbox pop-up window on thumbnail images. As soon as plugin is installed, all your thumbnail images will be opened in popup window.

Updated Plugins

scbFramework

A set of useful classes for WordPress plugin developers.

AVH Amazon

The AVH Amazon plugin gives you the ability to add multiple widgets which will display one or more random item(s) from your Amazon wishlist, baby registry and/or wedding registry. It also has the ability to show an item with its link, in posts and pages by use of shortcode.

WP-Table Reloaded

WP-Table Reloaded enables you to create and manage tables in your WP’s admin area. No HTML knowledge is needed. A comfortable backend allows to easily edit table data.

Twitter Fans

Twitter Fans plugin will add a widget in WordPress that you can drag and drop into your sidebar and set your username to get it work. No password required.

All in One Webmaster

This plugin allows you to easily integrate Google Webmaster Tool, Yahoo SiteExplorer and Bing Webmaster Central

WP Archive-Sitemap Generator

WP Archive-Sitemap Generator plugin generates simple Archives/Sitemap based on your blogs posts and pages. This is not another XML sitemap plugin, but rather a nice post sitemap or page sitemap generator. Now user can show total comments count after posts.

Twitter Goodies

This plugin shows your twitter profile/search tweets under Sidebar Area (Widget), Post and/or Pages. Tweets will REFRESH AUTOMATICALLY. Also it has reply option inside widget on mouse over action. Admin panel option available under Settings -> Twitter Goodies to set different color combination and twitter widget options.

Merge Tags

Adds the ability to combine two or more tags (or categories) into one.

by Perurry at December 22, 2009 03:43 PM under WordPress

Publisher Blog: UPS Joins WordPress.com VIP Hosting


UPS has announced the launch of their new blog, Upside, which is running on WordPress.com VIP Hosting:

The Upside blog, designed and built by T3 is a “blog created by UPS to share personal insights and perspective about the largest transportation company in the world.”

Some really interesting content posted so far including a video of how UPS and Zappos are working together.

[ Visit blog.ups.com ]

by Raanan Bar-Cohen at December 22, 2009 01:52 PM under VIP

Matt: Stealth Startups

Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets on TechCrunch.

by Matt at December 22, 2009 06:54 AM under Asides

December 21, 2009

Alex King: WordPress 2.9 Upgrade

WordPress 2.9 has been released – time to upgrade! There are some pretty nice new features in this release. I’m glad to be able to retire a few plugins now that the post thumbnail feature is built in and we’re going to wear out the comment meta feature in our custom implementations.

I’ve got a lot of sites to upgrade – I’ll have a little more on the process I use for this in a follow-up post.

If you need help with your upgrade, our team at WordPress HelpCenter is available and happy to help. Give us a call: (303) 395-1346 or email help@wphelpcenter.com.

by Alex at December 21, 2009 07:04 PM under WordPress

Joseph: WordPress 2.9 – XML-RPC and AtomPub Changes

Just in time for Christmas WordPress 2.9 is out. Here’s what has changed in the XML-RPC and AtomPub APIs since 2.8.6:

XML-RPC

  • Expose user registration option via wp.getOptions/wp.setOptions ( ticket #10454 )
  • Fix bug in wp.getComment that reported spam comments with a status of hold ( ticket #10510 )
  • Adjust how the XML-RPC server is activated so that the functions can be reused in other areas ( ticket #10513 )
  • Fix bug in setting optional number of pages arguments for wp.getPages ( ticket #10659 )
  • Reduced memory usage when processing requests ( ticket #10698 )

AtomPub

  • Fix a conflict with plugins that redefine wp_set_current_user() ( ticket #10938 )

If you are using the WordPress XML-RPC/AtomPub APIs in your software or service, or are just interested in this part of WordPress, please join the WordPress XML-RPC email list. Code changes and patches can be submitted via tickets at http://core.trac.wordpress.org/.

Related posts:

  1. WordPress 2.8 – XML-RPC and AtomPub Changes
  2. WordPress 2.7.1 Released – XML-RPC and AtomPub Changes
  3. WordPress 2.7 Released – XML-RPC and AtomPub Changes

by Joseph Scott at December 21, 2009 04:24 PM under xml-rpc

WordPress.tv: Weekly Recap: Inspirageek’s Interview with Matt Mullenweg and WordPress 2.9


A happy holidays to you from WordPress.tv!

We published two videos for you this week—one an interview with Matt Mullenweg of Automattic, and the other a video introduction to the neat stuff included in the latest release of WordPress.

Josh Grenon of Inspirageek interviews Matt Mullenweg in our first video published this week. They discuss some general tips for entrepreneurs, the development process for (the now released) WordPress 2.9, some basics behind VideoPress and why it’s great, and a few other odds and ends.

This weekend also saw the release of WordPress 2.9, the latest and greatest edition of our favorite software. To herald this event, our very own Michael Pick has composed an introductory video to WordPress 2.9, hitting the major updates and changes you’ll be playing with in the weeks to come. It’s a quick watch—check it out and feel free to embed when you talk about WordPress 2.9 on your own blog.

With the Christmas and New Year’s holidays coming up in the next two weeks, I expect new videos here on WordPress.tv will be few and far between, but we’ll still be here to check out and publish videos you direct us to using our handy contact form.

All of us here at WordPress.tv wish you a very happy holiday season and look forward to more great WordPress videos in 2010!

by Ryan Markel at December 21, 2009 04:37 AM under VideoPress

WordPress.tv: Introducing WordPress 2.9 – “Carmen”



Introducing WordPress 2.9 Carmen

by Ryan Markel at December 21, 2009 12:39 AM under upgrade

December 20, 2009

Weblog Tools Collection: WordPress Theme Releases for 20/12

Mons Montis

Mon Montis

Three column theme perfect for churches and other non-profits.

CleanRoar

cleanRoar

Keeping up with the seasons, cleanRoar takes a facelift and puts on the Christmas skin. It features a functional back-end packed with options. The skins can be swapped between the Legacy cleanRoar skin and the all new Christmas skin.

Technology

Technology_Theme

The Technology WordPress theme is a three column theme. Supports banner ads and the WP-PageNavi plugin.

Navy Spiral

NavySpiral

Navy Spiral is a notebook-inspired theme with cool blues and grays, clean lines, and subtle design cues to let your writing pop! No matter where writing inspiration takes you, you’re online notebook will always be there to share your thoughts and stories. Widget-ready, gravatar-enabled, and set to download.

Racing Red 01

Racing Red

Racing Red 01 is a simple WordPress Theme with one Sidebar and Widget Support. There is an Option Page to populate the Footer. Page in German

by Perurry at December 20, 2009 03:28 PM under wordpress themes

Weblog Tools Collection: WordPress 2.9 Feature Focus Batch Plug-in Updates

WordPress 2.9 (Carmen) has been officially released and has quite a few new features.  Some are visible and right on the page while many others are under the hood. 

One of the features that I really like is the ability to bulk update my plug-ins.  In previous versions of WordPress you had to update each plug-in individually by clicking on the automatic upgrade link in the WordPress plug-in, entering your FTP credentials and then waiting for the update to happen. If you had a lot of plug-ins this process could take a while to do.

To utilize the new bulk update process go to the Tools>Upgrade menu in the admin panel: 

wordpress29toolsupgrademenuitem 

There you will find a screen that looks something like this":

wordpress29bulkupgradeplugins

Select the check boxes for all the plug-ins you want to update and then press the Upgrade Plug-in button at the bottom and you will then be taken to a dialog box your familiar with to provide your FTP credentials. Once you have plugged those in the upgrade process will happen and once it is done you will be presented with this results page:

wordpress29bulkupgradepluginsresults

That is it for the process.  The only change I would recommend in a future update to WordPress is to place a link for this functionality on the actual plug-in admin page – maybe in the bulk action drop down menu.  From what I could see this bulk update option is only available on the main upgrade page.

So what is your favorite new feature of WordPress 2.9?

by WindowsObserver at December 20, 2009 03:24 PM under wordpress-plugin

December 19, 2009

Peter Westwood: What should go into a WordPress maintenance release?


Now that WordPress 2.9 has hit the streets there are inevitably going to be a number of bugs which slipped through testing which people will identify and we need a good process for deciding which of these bugs should be included in an upcoming 2.9.1 release and which of them can wait until 3.0 to be fixed.

In the past I think we have included to many changes into the maintenance releases.  This has partly been due to the lack of end-user testing which has taken place during the beta phase and partly based on a drive to fix bugs sooner rather than later.  This has had the unfortunate downside of diverting the time of the core contributors, that they could have been spending on working on features for the next major release, and has meant that the release cycle has been extended to longer than we would have liked.  This means that you don’t get the cool new features like Trash as soon as you would have done.

This post is an effort to summarise my thoughts on this subject and I would welcome discussion in the comments below – hopefully we can come up with a succinct set of criteria which will may it clear to everyone what the community thinks should be included in a maintenance release and what should not.

First of all I think it is important to understand the purpose of a maintenance or point release.  To me these releases are about fixing critical bugs which affect a large percentage of end-users and disrupt their ability to use the software. They need to have a small number of changes so as to make them easy to test, lightweight to develop and to reduce the impact on the next major release. This also means that they will be easy to upgrade too and are less likely to break plugins / themes in the process so making the upgrade to them even easier and more worry free.

If we let the content of these release grow too large then we will never have the time to work on the new features for the next major release which will then mean that release takes longer to arrive and may end up with less features.  We also need to remember that every change has the risk of introducing a new bug and this is another reason we should limit the number of changes in a maintenance release.

Now we need to identify what sort of bugs fit into the category of critical bugs.  The most obvious and easiest to identify are the security bugs – fixes for these need to be available as soon as possible. Once we get beyond security bugs it can get more difficult to quantify the affect of the issue and therefore how soon a fix needs to be in the hands of the users.

The following list of criteria are my straw man proposal on this subject:

  • The issue is easily reproducible and testable.
  • The issue is severe – e.g. it makes a whole feature unusable and therefore the fix cannot wait for the next major release.
  • The issue is a regression from a previous major release – for example if an unintentional/incompatible change to an API or UI was made.
  • The issue is not just that warnings or notices appear when WP_DEBUG is enabled the area of code in question must also fail to work correctly.

What do you think?

by Peter Westwood at December 19, 2009 10:56 PM under wordpress-2.9.1

Weblog Tools Collection: Download WordPress 2.9 “Carmen”

Surprise, WordPress 2.9 “Carmen” is out and available for downloads, you can either download it from here or use the inbuilt updater to upgrade to WP 2.9.

More info available at the WordPress blog. In case you want to know about the new features, check out my earlier review of new features in WordPress 2.9 or visit the WP Codex for WP 2.9.

by Keith Dsouza at December 19, 2009 01:31 AM under WordPress 2.9

Dev Blog: WordPress 2.9, oh so fine

I want to make you mine, all the time… oh wait. Hello. I’m here on behalf of the entire WordPress development team and community to announce the immediate availability of WordPress version 2.9 “Carmen” named in honor of magical jazz vocalist Carmen McRae (whom we’ve added to our Last.fm WP release station). You can upgrade easily from your Dashboard by going to Tools > Upgrade, or you can download from WordPress.org. And of course, it wouldn’t be a major release without a short video summarizing some of the cool things about the new version:

The coolest new stuff from a user point of view is:

  1. Global undo/”trash” feature, which means that if you accidentally delete a post or comment you can bring it back from the grave (i.e., the Trash). This also eliminates those annoying “are you sure” messages we used to have on every delete.
  2. Built-in image editor allows you to crop, edit, rotate, flip, and scale your images to show them who’s boss. This is the first wave of our many planned media-handling improvements.
  3. Batch plugin update and compatibility checking, which means you can update 10 plugins at once, versus having to do multiple clicks for each one, and we’re using the new compatibility data from the plugins directory to give you a better idea of whether your plugins are compatible with new releases of WordPress. This should take the fear and hassle out of upgrading.
  4. Easier video embeds that allow you to just paste a URL on its own line and have it magically turn it into the proper embed code, with Oembed support for YouTube, Daily Motion, Blip.tv, Flickr, Hulu, Viddler, Qik, Revision3, Scribd, Google Video, Photobucket, PollDaddy, and WordPress.tv (and more in the next release).

2.9 provides the smoothest ride yet because of a number of improvements under the hood and more subtle improvements you’ll begin to appreciate once you’ve been around the block a few times. Here’s just a sampling:

  • We now have rel=canonical support for better SEO.
  • There is automatic database optimization support, which you can enable in your wp-config.php file by adding define('WP_ALLOW_REPAIR', true);.
  • Themes can register “post thumbnails” which allow them to attach an image to the post, especially useful for magazine-style themes.
  • A new commentmeta table that allows arbitrary key/value pairs to be attached to comments, just like posts, so you can now expand greatly what you can do in the comment framework.
  • Custom post types have been upgraded with better API support so you can juggle more types than just post, page, and attachment. (More of this planned for 3.0.)
  • You can set custom theme directories, so a plugin can register a theme to be bundled with it or you can have multiple shared theme directories on your server.
  • We’ve upgraded TinyMCE WYSIWYG editing and Simplepie.
  • Sidebars can now have descriptions so it’s more obvious what and where they do what they do.
  • Specify category templates not just by ID, like before, but by slug, which will make it easier for theme developers to do custom things with categories — like post types!
  • Registration and profiles are now extensible to allow you to collect things more easily, like a user’s Twitter account or any other fields you can imagine.
  • The XML-RPC API has been extended to allow changing the user registration option. We fixed some Atom API attachment issues.
  • Create custom galleries with the new include and exclude attributes that allow you to pull attachments from any post, not just the current one.
  • When you’re editing files in the theme and plugin editors it remembers your location and takes you back to that line after you save. (Thank goodness!!!)
  • The Press This bookmarklet has been improved and is faster than ever; give it a try for on-the-fly blogging from wherever you are on the internet.
  • Custom taxonomies are now included in the WXR export file and imported correctly.
  • Better hooks and filters for excerpts, smilies, HTTP requests, user profiles, author links, taxonomies, SSL support, tag clouds, query_posts and WP_Query

All of this and more is reflected in the over 500 tickets, bugs, and enhancements that WP developers in this release cycle.

This release included code from over 140 contributors, here’s everyone we were able to identify: aaroncampbell (Aaron Campbell), abackstrom (Adam Backstrom), aldenta (John Ford), alexkingorg (Alex King), [amilanov], antonylesuisse (Antony Lesuisse), apeatling (Andy Peatling), apokalyptik (Demitrious Kelly), arena (André Renaut), batmoo (Mohammad Jangda), Ben Dunkle, BenBE1987, Benjamin Flesch, bookchiq (Sarah Lewis), brianwhite, c0nstruct, caesarsgrunt (Caesar Schinas), CalebKniffen (Caleb Kniffen), chrisbliss18, chrisscott (Chris Scott), christoph179, coffee2code (Scott Reilly), [cross country flight], Curioso, davecpage (Dave Page), dcole07 (Dan Cole), dd32 (Dion Hulse), demetris (Δημήτρης Κίκιζας), Denis-de-Bernardy, dj-wp, dwright, eddieringle (Eddie Ringle), error (Michael Hampton), ewestp, fabifott, filosofo (Austin Matzko), greenshady (Justin Tadlock), gsnedders/link92 (Geoffrey Sneddon), hailin (Hailin Wu), hakre, hanilovesme, Harald Nesland, harrym, holizz (Tom Adams), ikonst, jacobsantos (Jacob Santos), janeforshort (Jane Wells), jamescollins (James Collins), jdub (Jeff Waugh), jeff_ (Jean-François “Jeff” VIAL), jeremyclarke (Jeremy Clarke), JeremyVisser (Jeremy Visser), jikamens, jmulley, Joern_W, johanee (Johan Eenfeldt), johnbillion (John Blackbourn), johnjamesjacoby (John James Jacoby), johnjosephbachir (John Joseph Bachir), JonathanRogers, joostdevalk (Joost de Valk), Jose Carlos Norte, josephscott (Joseph Scott), junsuijin, kevinB (Kevin Behrens), kometbomb, lilyfan (IKEDA Yuriko), [lostinlafayette], madhyde, MattyRob, mdawaffe (Michael Adams), Mittineague, miqrogroove, morfiusx, mrmist (David McFarlane), mtdewvirus (Nick Momrik), mysz, nacin (Andrew Nacin), nanochrome, nao (Naoko McCracken), nathanrice (Nathan Rice), nbachiyski (Николай Бачийски), niallkennedy (Niall Kennedy), nickohrn (Nick Ohrn), ninjaWR (Ryan Murphy), noel (Noël Jackson), Otto42 (Samuel Wood), pairg, peaceablewhale (Franklin Tse), prettyboymp (Michael Pretty), ProDevStudio, ramiy, redsweater (Daniel Jalkut), ruslany, sambauers (Sam Bauers), scribu, Sewar, Simek, simonwheatley (Simon Wheatley), sirzooro (Daniel Frużyński), sivel (Matt Martz), skeltoac (Andy Skelton), snakefoot, stephanreiter (Stephan Reiter), strider72 (Stephen Rider), taco1991, takayukister (Takayuki Miyoshi), tellyworth, tenpura, usermrpapa, utkarsh, Viper007Bond, vladimir_kolesnikov (Vladimir Kolesnikov), VoxPelli (Pelle Wessman), [voyou1], wahgnube, waltervos, westonruter (Weston Ruter), wnorris (Will Norris), xenlab (Eric Marden), yoavf (Yoav Farhi). Wowza!

2.9 has been an exciting development cycle, and I must say it has whetted our appetite for 3.0, which is coming next (probably this spring) and will include at the very least the merge of MU with the WordPress core, and a new default theme. We can’t wait to start working on it. But first, some Carmen McRae tunes and a beer. Join us! :)

(After you upgrade, of course!)

I hope everyone is having a wonderful holiday season.

by Matt at December 19, 2009 12:46 AM under Releases

December 18, 2009

Dev Blog: 2010: A Theme Odyssey

After the video from the core team meetup was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt’s announcement that there would be a new default theme in 2010, so I thought I’d start with that as the first of the meetup summaries.

When Kubrick was bundled with core back in 2005, it was a cutting edge theme. Custom header, rounded corners, clean design… if you were using WordPress back then, let’s face it, you were impressed. Time moves on, though, fashions change, new styles become old standards, and what was once cutting edge suddenly seems old-fashioned and out of date.

So, a new bundled theme in 2010? We think it’s a good idea. Something nice and light that can serve as a good example theme, include newer theme-based features, and look nice (and current) on a public site. We’d like to introduce a new default theme with version 3.0, which is anticipated to come out in mid-2010 (hence the name), and think it would be good for it to blend well aesthetically with WordPress itself.

I’d been advocating moving toward Elastic, the theme framework/WYSIWYG theme editor that was one of our Google Summer of Code student projects, but after some discussion I agreed with the guys that while Elastic is awesome and should be promoted as a community development project, it’s heavier than a default theme needs to be. The default theme doesn’t need to be a full-featured framework, it just needs to work well, look awesome, have good code and be a good starting point for beginning themers. We were thinking of a fairly minimalist design that would make it easy to customize.

As for the code, there’s a question of if it will really be a new theme, or if it will be a re-styled and updated version of Kubrick.  We don’t know the final answer to that yet, because the ultimate decision will be made with the community’s input, but we believe all new markup is the way to go. What do you think? Without venturing into theme framework territory, are there features you think a new default theme should have? Some people have been talking about it on Trac over the past year, if you wonder what’s been tossed around so far. I thought about posting a poll here (you know how I love posting polls to gauge opinion), but in this case I think a discussion thread might be better, so that each vote can explain the reason behind it. So, have an opinion on what a new default theme should include? Weigh in at the forums.

by Jane Wells at December 18, 2009 06:36 PM under theme

WordPress Planet

This is an aggregation of blogs talking about WordPress from around the world. If you think your blog should be part of this send an email to Matt.

Official Blog

For official WP news, check out the WordPress Dev Blog.

Subscriptions

Last updated:

December 28, 2009 10:15 PM
All times are UTC.