The second release candidate for WordPress 3.4 is now available. Since RC1, we’ve made a few dozen final changes.
Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely your last chance to test your plugins and themes to find any compatibility issues before the final release. We’ve published some resources on the development blog to help you prepare.
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. Or, if you’re comfortable writing a reproducible bug report, file one on WordPress Trac. Known issues that crop up will be listed here, but we’re hoping for a quiet few days so we can get some great features into your hands next week!
To test WordPress 3.4, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). Be sure to visit → About for an updated list of features and under-the-hood changes.
The first release candidate (RC1) for WordPress 3.4 is now available.
An RC comes after the beta period and before final release. We think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. So if you haven’t tested WordPress 3.4 yet, now is the time! Please though, not on your live site unless you’re adventurous.
With more than 500 tickets closed, there are quite a few changes. Plugin and theme authors, please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.
If you are testing the release candidate and think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If any known issues crop up, you’ll be able to find them here.
To test WordPress 3.4, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip).
If you’d like to know which levers to pull in your testing, visit the About page ( → About in the toolbar) and check out the list of features! You’ll definitely want to try the live theme previews.
Bonus: Happy birthday WordPress — nine years old today.
Been hanging out with a few WordPress.org hackers — Scott, Nacin, and Otto — the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over 19,000 plugins listed and they’re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. Here’s a quick before and after snapshot you can zoom in on to see a visual overview of some of the changes:
Our first focus was around improving the discussion and support around plugins.
You’ll now notice that threads about a plugin are pulled directly into a “support” tab on the plugin page — each plugin has its own forum. We’ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you’re using. And finally to show how active and well-supported a plugin is, you can see ”16 of 75 support threads in the last two weeks have been resolved.” Finally, if you’re logged in you get access to the new “favorites” feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!
If you’re a plugin author, we’ve started with a short threshold (2 weeks) for the resolved stats so it’s easy to catch up and stay on top of it. (It’ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.
We’ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:
- “Plugin headers” or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.
- You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn’t yours. There is no better way to follow the development of your favorite plugins. There’s nothing like the smell of fresh changesets in the morning.
- Behind the scenes, we’ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.
All of this will continue to evolve as we get feedback and see usage, but we’re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ — it imparts magical coding powers.)
Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it’s easily my favorite. Don’t get me wrong, I love attending WordCamps and local WordPress meetups (which are awesome and you should try to attend if you are able), but at the core team meetup, the focus on working together and getting things done is unique, as is the experience of every person in the room being so highly qualified. This year, instead of just planning a core team meetup, I’m aiming a little higher and shooting for a full-on contributor/community summit.
Core code isn’t the only way to contribute to the WordPress project. We have an active theme review team, support forum volunteers, people writing documentation, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we’ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.
In addition to bringing together the active contributor team reps to work together, I think it’s important to include community members who don’t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!
Taking a cue from events with limited availability like AdaCamp (attendance) and the jQuery conference (speaker roster), I want you to nominate people and/or WordPress-based businesses to participate in the summit. Yes, you can nominate yourself.* You can nominate up to 10 additional people — be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there’s a theme or hosting company (for example) that you think should be there, you don’t need to go looking for employee names. This nomination process will hopefully ensure that we don’t overlook someone who is making a difference in our community when it comes time to issue invitations.
Nominations will be open for a week, after which the survey will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at WordPress.tv. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you’re thinking to yourself that maybe now’s the perfect time to start contributing time to the WordPress project, good thinking! In the meantime, if you want to weigh in, fill in the community summit nomination form. Thanks, and wish us luck!
* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.
** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.
Less bugs, more polish, the same beta disclaimers. Download, test, report bugs. Thanks much. /ryan #thewholebrevitything
WordPress 3.3.2 is available now and is a security update for all previous versions.
Three external libraries included in WordPress received security updates:
- Plupload (version 1.5.4), which WordPress uses for uploading media.
- SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins.
- SWFObject, which WordPress previously used to embed Flash content, and may still be in use by plugins and themes.
Thanks to Neal Poole and Nathan Partlan for responsibly disclosing the bugs in Plupload and SWFUpload, and Szymon Gruszecki for a separate bug in SWFUpload.
WordPress 3.3.2 also addresses:
- Limited privilege escalation where a site administrator could deactivate network-wide plugins when running a WordPress network under particular circumstances, disclosed by Jon Cave of our WordPress core security team, and Adam Backstrom.
- Cross-site scripting vulnerability when making URLs clickable, by Jon Cave.
- Cross-site scripting vulnerabilities in redirects after posting comments in older browsers, and when filtering URLs. Thanks to Mauro Gentile for responsibly disclosing these issues to the security team.
These issues were fixed by the WordPress core security team. Five other bugs were also fixed in version 3.3.2. Consult the change log for more details.
Download WordPress 3.3.2 or update now from the Dashboard → Updates menu in your site’s admin area.
WordPress 3.4 Beta 3 also available
Our development of WordPress 3.4 development continues. Today we are proud to release Beta 3 for testing. Nearly 90 changes have been made since Beta 2, released 9 days ago. (We are aiming for a beta every week.)
This is still beta software, so we don’t recommend that you use it on production sites. But if you’re a plugin developer, a theme developer, or a site administrator, you should be running this on your test environments and reporting any bugs you find. (See the known issues here.) If you’re a WordPress user who wants to open your presents early, take advantage of WordPress’s famous 5-minute install and spin up a secondary test site. Let us know what you think!
Version 3.4 Beta 3 includes all of the fixes included in version 3.3.2. Download WordPress 3.4 Beta 3 or use the WordPress Beta Tester plugin.
Howdy, folks! Another week, another beta. Since we released Beta 1 last week, we’ve committed more than 60 bug fixes and feature adjustments based on testing and feedback. If you’ve been testing Beta 1, please update to Beta 2 to make sure things are still working for you. If you are a theme or plugin author and have not yet started testing your code against the 3.4 beta, now’s the perfect time to start. And as always, if you find any bugs, let us know! Full details on testing and bug reporting can be found in last week’s Beta 1 post.
Download WordPress 3.4 Beta 2
WordPress 3.4 is ready for beta testers!
As always, this is software still in development and we don’t recommend that you run it on a production site — set up a test site just to play with the new version. If you break it (find a bug), please report it, and if you’re a developer, try to help us fix it.
If all goes well, we hope to release WordPress 3.4 in May. The more help we get with testing and fixing bugs, the sooner we will be able to release the final version. If you want to be a beta tester, you should check out the Codex article on how to report bugs.
Here’s some of what’s new:
- Theme Customizer with Previewer
- Flexible Custom Header Sizes
- Selecting Custom Header and Background Images from Media Library
- Better experience searching for and choosing a theme
And some of the under-the-hood changes:
- New XML-RPC API for external and mobile applications
- New API for registering theme support for custom headers and backgrounds
- Performance improvements to WP_Query by splitting the query (Please test!)
- Internationalization improvements (improved performance and locale support)
- Performance and API improvements when working with lists of installed themes
- Support for installing child themes from the WordPress Themes Directory
Remember, if you find something you think is a bug, report it! You can bring it up in the alpha/beta forum, you can email it to the wp-testers list, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the WordPress Core Trac. (We recommend starting in the forum or on the mailing list.)
Theme and plugin authors, if you haven’t been following the 3.4 development cycle, please start now so that you can update your themes and plugins to be compatible with the newest version of WordPress.
Download WordPress 3.4 Beta 1
The South by Southwest Interactive Festival (SXSW) holds a special place in the history and heart of WordPress. Though the conference has changed in the years since I first met Matt in the hallway in 2003 — before WordPress even had a name — it’s still arguably one of the most influential events in our industry, and we’ll be there again this year. Will we see you there?
There will be a WordPress booth at the SXSW trade show March 12-15. Our booth was packed to overflowing last year as we helped people with their blogs and gave away WordPress swag, so this year we’ll have more space to meet as many of you as possible. Stop by if you need a helping hand with your site, or just to say hi. We’ll also have buttons, stickers, and t-shirts again this year.
This year’s WordPress party will be hosted by the WordPress Foundation on Monday, March 12 from 6-9pm. Space is limited, so make sure you RSVP (no SXSW badge is required). The party this year will be at the Buzzmedia Pure Volume House, and the story of how we hooked up with them is pretty cool.
Once upon a time, David Wang had a business called Buzzmedia in Malaysia, with the twitter username @buzzmedia. When David changed gears and started ClickWP, a WordPress support business, he stopped going by the Buzzmedia name. In the U.S., a company also called Buzzmedia wished it had that Twitter username, and asked if they could have it since David wasn’t going to use it anymore.
David, feeling the WordPress community love, said he would give them the name, and suggested they do something in return for the WordPress Foundation. So, everyone talked to everyone else and it worked out that Buzzmedia was willing to donate a fantastic venue for this year’s party as well as covering the bar.
In the end, the Foundation got a great SXSW party, Buzzmedia got their twitter username, and David got the warm glow of having used his power for the good of the WordPress community, and they all lived happily ever after.
Seriously, though, the PureVolume House is always a great SXSW venue, so thank you David and Buzzmedia for your generosity! We’ll have drinks and snacks and a few hundred WordPress-loving partygoers, so you know it will be a good time. Kind of like a WordCamp afterparty without all the work of a WordCamp.
The venue can hold 500 people, and based on last year, we’ll hit that pretty quickly. The one requirement is that you use WordPress. On the RSVP form, you will be asked to enter the URL of your WordPress-powered site (if you have more than one, just pick your main site). If you fill in this field with something other than what’s requested (such as “N/A” or putting in a fake url) your RSVP may be deleted, so please make sure to enter your real site.
We hereby declare 2012 as the Year of the WordPress Meetup. You’ll want to get in on this action.
meet·up \mēt-əp\ noun
A meeting, especially a regular meeting of people who share a particular interest and have connected with each other through a social-networking Web site: a meetup for new moms in the neighborhood; a meetup to plan the trip; a meetup for WordPress users.1
So what is a WordPress Meetup? Basically, it’s people in a community getting together — meeting up — who share an interest in WordPress, whether they be bloggers, business users, developers, consultants, or any other category of person able to say, “I use WordPress in some way and I like it, and I want to meet other people who can say the same.” Meetups come in different shapes and sizes, but they all carry the benefit of connecting you with potential collaborators and friends, and helping you learn more about what you can do with WordPress. Here are some of the common types of WordPress meetups:
- Hang out and work on your WordPress sites together
- Social/happy hour type gatherings
- Developer hacking meetups
- Show & tell of how group members are using WordPress
- Formal instruction on how to use WordPress
- Lecture series (possibly with visiting speakers)
- Genius bar/help desk
There’s no prescribed format, as each local group can decide for itself what they want to do. Some groups mix it up from month to month, while others have multiple events each month to satisfy the needs of their community.
The tough part? Running a popular group takes time and money. Just as we worked last year to remove the financial burden for WordCamp organizers and provide logistical support so they could focus more on their event content and experience, we want to start extending that kind of support to meetup groups as well. We don’t want it to cost anything for someone to run a WordPress meetup, or to attend one — building local communities should be as free as WordPress itself!
Since there are so many more meetups than there are WordCamps, we’re going to start with the cost that is the same for every group: meetup.com organizer dues. We’re setting up an official WordPress account on Meetup.com right now, and over the next couple of weeks will be working with existing meetup group organizers, people who want to start a new meetup group, and the helpful folks at Meetup.com to put this program in place. WordPress meetup groups that choose to have their group become part of the WordPress account will no longer pay organizer dues for that group, as the WordPress Foundation will be footing the bill.
This is exciting for several reasons. First, it means local organizers who are giving something back to the project by way of their time won’t also have shell out $12-19/month for the privilege. That alone is a big step. Second, it will open the door to more events and leaders within a community, since leadership and event planning won’t need to be tied to “owning” the meetup group. Third, more active meetup groups means more WordCamps, yay!
In addition to the financial aspects, we’ll be working on ways to improve social recognition of meetup activity by incorporating feeds from the official meetup groups into the WordPress.org site, and including meetup group participation in the activity stream on your WordPress.org profile.2 I’m also hoping we can do something around providing video equipment to meetup groups (like we already do for WordCamps) to record presentations and tutorials that can be posted to WordPress.tv, helping meetup groups offer WordPress classes in their community, and getting involved with mentoring WordPress clubs at local schools and universities. Oh, and we’ll send out some WordPress buttons and stickers to the groups that join in, because everyone loves buttons and stickers.
We’re also putting together some cool resources for people who want to start a new meetup group. There will be a field guide to getting started and some supplies to help you get your group going, and a forum for organizers to talk to and learn from each other.
Over time, we’ll be talking to organizers and looking at what other expenses we can absorb and what other support we can provide to local groups. For now, we’re starting with the organizer dues. If you currently run a WordPress meetup group (whether you are using Meetup.com or not) or would like to start a WordPress meetup group in your area, please fill out our WordPress Meetup Groups survey. Filling in the survey doesn’t obligate you to join the official group, it just gives us a starting point to a) find out what groups are around/interested, and b) get some information on existing groups and their expenses and needs. Meetup.com will contact the group organizers who’ve said they’d like to join the new program, and will walk them through the logistics of the change and answer questions before helping them to opt-in officially.
So, if you currently run a WordPress meetup group, or you would like to start one, please fill out our WordPress Meetup Groups survey. I can’t wait to see more meetups!
1 – Adapted from “meetup” definition at dictionary.com.
2 – Didn’t know about profiles? Check out http://profiles.wordpress.org/users/yourwordpressdotorgusernamehere (put in the username you use in the WordPress.org forums) to see yours!
« Newer Posts
— Older Posts »