WordPress 3.1 Launch Candidate 3 is now obtainable. After cautious analysis of the three.1 options in RC2, we acknowledged the necessity to make some changes. There are some vital variations from earlier variations of three.1, so please assessment the adjustments in case you have been creating towards a beta or RC model.
The largest change is the elimination of AJAX listing tables, which had been an effort to maneuver all of our list-style screens to full AJAX for pagination, searches, and column kinds, and to consolidate the list-style screens right into a single API that plugins might leverage. Sadly, with extra testing got here realizations that there have been too many main bugs and usefulness points with how the performance was carried out, so we’ve spent the final week rolling again an important parts of the function.
- For customers: AJAX has been fully disabled for the listing tables. We hope to convey this again once more, in a kind that’s correctly and totally carried out, in a future launch. Column sorting stays, however all the pieces else has returned to its 3.0 state.
- For builders: Your complete listing desk API is now marked personal. In the event you try to leverage new elements of the API, you’re just about guaranteeing that your plugins will break in a future launch, so please don’t try this. 🙂 We hope to allow all of the enjoyable new goodies for public use in a future launch.
That is the one method we might forestall any regressions in performance and usefulness from WordPress 3.0 to three.1. That’s proper, customers and plugin authors can nonetheless do all the pieces you used to have the ability to do (and a bit of bit extra).
Due to the code churn between RC2 and RC3, this launch candidate wants lots of testing. Each listing display wants testing. Specifically, the remark moderation display wants testing, particularly with keyboard shortcuts (when you didn’t find out about these, now’s your likelihood to attempt them out).
Different fixes in RC3 embody:
- Correctly show the creator dropdown in Fast Edit
- Varied essential fixes to quite a few taxonomy question variables
- Fixes to the theme deletion course of
- Fixes to pages used for posts
- IIS and Multisite: Keep away from resetting net.config on permalink save
- Correctly validate put up codecs and their rewrite guidelines
I’m assembling a bunch of pals in Washington, D.C., this weekend to check WordPress 3.1 and supply suggestions. We’d like to see this concept catch on amongst pals at espresso outlets around the globe. (We’ll weblog our outcomes, and we’re fascinated with utilizing the hashtag #wptest on Twitter.) If you’re testing the discharge candidate and suppose you’ve discovered a bug, there are just a few methods to tell us:
We’re going to review this launch rigorously to see the place we are able to enhance on our inside processes sooner or later. With that, our requisite haiku, authored by Jane:
Pulling the AJAX —
generally it’s essential to step again
and present some restraint.