WordPress.org

The release candidate for WordPress 4.5 is now available.

We’ve made 49 changes since releasing Beta 4 a week ago. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.5 on Tuesday, April 12, but we need your help to get there.

If you haven’t tested 4.5 yet, now is the time!

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

To test WordPress 4.5, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

For more information about what’s new in version 4.5, check out the Beta 1, Beta 2, Beta 3, and Beta 4 blog posts.

Developers, please test your plugins and themes against WordPress 4.5 and update your plugin’s Tested up to version in the readme to 4.5 before next week. If you find compatibility problems, we never want to break things, so please be sure to post to the support forums so we can figure those out before the final release.

Be sure to follow along the core development blog, where we’ll continue to post notes for developers for 4.5.

Free as in Freedom
It is WordPress 4.5
Also free as in beer

WordPress 4.5 Beta 4 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.5, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

For more information on what’s new in 4.5, check out the Beta 1, Beta 2, and Beta 3 blog posts, along with in-depth field guides on make/core. This is the final planned beta of WordPress 4.5, with a release candidate scheduled for next week.

Some of the changes in Beta 4 include:

• Add support for oEmbed moments and timelines from Twitter (#36197).
• More changes to better support HHVM with Imagick. Please test with HHVM setups and resizing/rotating images (#35973).
• Tightened up the Inline Link feature (#33301, #30468).
• Support <hr> editor shortcut with 3 or more dashes (---); no spaces. To give more time to study the best shortcuts for users, text patterns for bold and italic have been removed and won’t ship with for 4.5 (#33300).
• Fixes for SSL with Responsive Images. Please test with SSL, especially on sites with mixed http/https setups (#34945).
• Allow rewrite rules to work in nested WordPress installations on IIS (#35558).
• Various bug fixes. We’ve made almost 100 changes during the last week.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on the WordPress Trac. There, you can also find a list of known bugs.

Happy testing!

Llegamos al fin
del tiempo pa’ beta
¡Pruébalo Ahora!

WordPress 4.5 Beta 3 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.5, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

For more information on what’s new in 4.5, check out the Beta 1 and Beta 2 blog posts, along with in-depth field guides on make/core. Some of the fixes in Beta 3 include:

• Many Theme Logo Support (#33755) fixes, including support for bundled Twenty Fifteen (#35944).
• Add Responsive Preview to theme install previewer (#36017).
• Support Imagick in HHVM (#35973).
• Whitelist IPTC, XMP, and EXIF profiles from strip_meta() to maintain authorship, copyright, license, and image orientation (#28634).
• Support Windows shares/DFS roots in wp_normalize_path() (#35996).
• New installs default to generating secret keys and salts locally instead of relying on the WordPress.org API. Please test installing WP in situations where it can’t connect to the internet (like on a 🛳, ✈️, or 🛰) (#35290).
• OPTIONS requests to REST API should return Allow header (#35975).
• Upgrade twemoji.js to version 2 (#36059) and add extra IE11 compatibility (#35977) for Emoji.
• Various bug fixes. We’ve made more than 100 changes during the last week.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on the WordPress Trac. There, you can also find a list of known bugs.

Happy testing!

Beta one, two, three
so many bugs have been fixed
Closer now; four, five.

WordPress 4.5 Beta 2 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.5, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

For more information on what’s new in 4.5, check out the Beta 1 blog post. Some of the fixes in Beta 2 include:

• Added Horizontal Rule (HR) editing shortcut and dismissible “Paste as Text” notice in TinyMCE.
• Selective Refresh support is enabled for core themes titles and taglines, which allows shift-click to focus on controls and PHP filters to apply in the preview.
• Resolved a fatal error on image upload when ImageMagick could not complete stripping meta during resize (#33642).
• Various bug fixes. We’ve made just over 100 changes in the last week.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on the WordPress Trac. There, you can also find a list of known bugs.

Happy testing!

It’s peer pressure time
Testing: all cool kids do it
Help find ALL the bugs!

It’s time for our second global contributor weekend, and this time we’re focusing on the video team. For this month’s challenge, in honor of it being our second month, you have two options for how you can participate! The challenge for this month overall is to work with at least one hour worth of WordCamp video, which you can do by either creating subtitles or editing the video file in preparation for upload to WordPress.tv.

One of the great things about contributing to the video team is that you get to learn so much, since all the work basically involves watching WordCamp presentation videos. Subtitling is a doubly important need, as it is needed to make all those WordCamp videos accessible to people who are deaf or hard of hearing and can’t listen to the audio track, as well as making it possible for the videos to be consumed (in some cases after subtitle translation) by people who speak different languages.

The challenge will last from Saturday, February 27, 2016 through Sunday, February 28, 2016, and the results will be reviewed afterward by members of the video team. If you enjoy the challenge, the video team would be very excited to welcome you into their ranks! Interested? Here’s how to participate.

What About Last Month?

In January, the inaugural contributor weekend was focused on the support forums. That challenge had 73 participants, including 10 people who provided 20 or more correct answers to open support threads, thereby winning the challenge. Congratulations to Harris Anastasiadis, Ahmad Awais, Takis Bouyouris, Phil Erb, Eric Gunawan, Jackie McBride, Diana Nichols, Kostas Nicolacopoulos, Juhi Saxena, and Sarah Semark! To them and to everyone else who participated, thank you so much for your efforts. Every answer helps, and over the course of this contributor weekend, these amazing volunteers responded to 800 support threads. The support forums queue of requests with no replies went from 28 pages to 7 pages — that was an incredible success, of which every participant was a part!

So head on over to see how to get involved with the one-hour video challenge this weekend, and help us make next month’s post just as impressive! 🙂

WordPress 4.5 Beta 1 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.5, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

WordPress 4.5 is slated for release on April 12, but to get there, we need your help testing what we have been working on, including:

• Responsive Preview of your site in the Customizer (#31195) – See how your site looks in mobile, tablet, and desktop contexts before making changes to its appearance.
• Theme Logo Support (#33755) – Native support for a theme logo within the Customizer.
• Inline Link Editing (#33301) – Within the visual editor, edit links inline for a smoother workflow.
• Additional Editor Shortcuts (#33300) – Includes a few new shortcuts, like `..` for code and **..** for bold.
• Comment Moderation Improvements (#34133) – An enhanced experience when moderating comments, including preview with rendered formatting.
• Optimization of Image Generation (#33642) – Image sizes are generated more efficiently and remove unneeded meta, while still including color profiles in Imagick, for reduced sizes of up to 50% with near identical visual quality.

There have been changes for developers to explore as well:

• Selective Refresh (#27355) – A comprehensive framework for rendering parts of the customizer preview in real time. Theme and plugin authors should test their widgets specifically for compatibility with selective refresh, and note that it may ultimately be opt-in for 4.5.
• Backbone and Underscore updated to latest versions (#34350) – Backbone is upgraded from 1.1.2 to 1.2.3 and Underscore is upgraded from 1.6.0 to 1.8.3. See the this post for important changes.
• Embed templates (#34561) – Embed templates were split into parts and can now be directly overridden by themes via the template hierarchy.
• New WP_Site class (#32450) – More object-oriented approach for managing sites in Multisite
• Script loader (#14853, #35873) – Introduces wp_add_inline_script() for including inline JavaScript just like wp_add_inline_style() works for CSS, and better support for script header/footer dependencies.

If you want a more in-depth view of what major changes have made it into 4.5, check out all 4.5-tagged posts on the main development blog, or check out a list of everything that’s changed.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on the WordPress Trac. There, you can also find a list of known bugs.

Happy testing!

A wonderful day
is one that brings new WordPress
Four Five Beta One

WordCamps are locally-organized WordPress conferences that happen all over the world (and are so fun). Sometimes people don’t realize that WordCamps are organized by local volunteers rather than a central organization, and they contact us asking, “Can you bring WordCamp to my city?” When this happens, we always suggest they start with a meetup group, and think about organizing a WordCamp themselves after their group has been active for a few months. We emphasize that WordCamps are locally-organized events, not something that the central community team plans from afar.

This has been successful in many areas — there are currently 241 meetup groups on our meetup.com chapter program! In some regions, though, enthusiastic volunteers have had more of a challenge getting things started. Because of this, we’re going to try an experiment this year called the WordCamp Incubator.

The intention of the incubator program is to help spread WordPress to underserved areas through providing more significant organizing support for a first event. In practical terms, this experiment means we’ll be choosing three cities in 2016 where there is not an active WordPress community — but where it seems like there is a lot of potential and where there are some people excited to become organizers — and will help to organize their first WordCamp. These WordCamps will be small, one-day, one-track events geared toward the goal of generating interest and getting people involved in creating an ongoing local community.*

So, where should we do these three events?  If you have always wanted a WordCamp in your city but haven’t been able to get a meetup group going, this is a great opportunity. We will be taking applications for the next week, then will get in touch with everyone who applied to discuss the possibilities. We will announce the  cities chosen by the end of March.

To apply, fill in the application by February 26, 2016. You don’t need to have any specific information handy, it’s just a form to let us know you’re interested. You can apply to nominate your city even if you don’t want to be the main organizer, but for this experiment  we will need local liaisons and volunteers, so please only nominate cities where you live or work so that we have at least one local connection to begin.

Thanks, and good luck!

* For the record, that describes the ideal first WordCamp even if you have an active meetup — there’s no need to wait until your group is big enough to support a large multi-day event, and small events are a lot of fun because everyone has a chance to be involved and get to know most of the other attendees.

WordPress 4.4.2 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

WordPress versions 4.4.1 and earlier are affected by two security issues: a possible SSRF for certain local URIs, reported by Ronni Skansing; and an open redirection attack, reported by Shailesh Suthar.

Thank you to both reporters for practicing responsible disclosure.

In addition to the security issues above, WordPress 4.4.2 fixes 17 bugs from 4.4 and 4.4.1. For more information, see the release notes or consult the list of changes.

Download WordPress 4.4.2 or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.4.2.

Thanks to everyone who contributed to 4.4.2:

Andrea Fercia, berengerzyla, Boone Gorges, Chandra Patel, Chris Christoff, Dion Hulse, Dominik Schilling, firebird75, Ivan Kristianto, Jennifer M. Dodd, salvoaranzulla

Our first global contributor drive is coming up next weekend, January 30-31, 2016, and we want you to be involved!

Many of our current contributors first got involved at a Contributor Day at a WordCamp or WordPress Meetup event near them, but not everyone has had that opportunity, so we’re trying to create an online experience that will give new contributors the same kind of live support and group dynamic. We’ll be doing these as weekend challenges rather than one-day events so that WordPress users all over the world can participate without worrying about pesky time zones, but each challenge will be designed to be completed within a few hours, comparable to an in-person Contributor Day.

Our inaugural Contributor Weekend is focused on the Support Team — the folks who volunteer their time to help people with WordPress questions in the support forums and IRC. Over the two day span, forum moderators will be available online to help new contributors and answer questions as needed. The challenge this month is called 20 Questions; your mission (should you choose to accept it) is to help WordPress users by answering 20 forum support requests over the course of the weekend.

You can participate on your own, or you can get together with other people from your local meetup group and work on it together. Working together in person is really fun, so we highly recommend trying to get some folks together if you’re able, but if that’s not possible you can still connect to other participants online. Either way, this is a great way to give back to the WordPress project and have some fun helping people at the same time.

Interested? Get the details on how to participate.

Hope to see you next weekend!

WordPress 4.4.1 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

WordPress versions 4.4 and earlier are affected by a cross-site scripting vulnerability that could allow a site to be compromised. This was reported by Crtc4L.

There were also several non-security bug fixes:

• Emoji support has been updated to include all of the latest emoji characters, including the new diverse emoji! 👍🏿👌🏽👏🏼
• Some sites with older versions of OpenSSL installed were unable to communicate with other services provided through some plugins.
• If a post URL was ever re-used, the site could redirect to the wrong post.

WordPress 4.4.1 fixes 52 bugs from 4.4. For more information, see the release notes or consult the list of changes.

Download WordPress 4.4.1 or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.4.1.

Thanks to everyone who contributed to 4.4.1:

Aaron D. Campbell, Aaron Jorbin, Andrea Fercia, Andrew Nacin, Andrew Ozz, Boone Gorges, Compute, Daniel Jalkut (Red Sweater), Danny van Kooten, Dion Hulse, Dominik Schilling (ocean90), Dossy Shiobara, Evan Herman, Gary Pendergast, gblsm, Hinaloe, Ignacio Cruz Moreno, jadpm, Jeff Pye Brook, Joe McGill, John Blackbourn, jpr, Konstantin Obenland, KrissieV, Marin Atanasov, Matthew Ell, Meitar, Pascal Birchler, Peter Wilson, Roger Chen, Ryan McCue, Sal Ferrarello, Scott Taylor, scottbrownconsulting, Sergey Biryukov, Shinichi Nishikawa, smerriman, Stephen Edgar, Stephen Harris, tharsheblows, voldemortensen, and webaware.