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 overview the adjustments you probably have been creating in opposition to a beta or RC model.
The most important change is the removing of AJAX record 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 value points with how the performance was carried out, so we’ve spent the final week rolling again a very powerful parts of the function.
- For customers: AJAX has been totally disabled for the record tables. We hope to deliver this again once more, in a type that’s correctly and absolutely carried out, in a future launch. Column sorting stays, however every thing else has returned to its 3.0 state.
- For builders: The whole record desk API is now marked personal. Should you try to leverage new parts of the API, you’re just about guaranteeing that your plugins will break in a future launch, so please don’t do this. 🙂 We hope to allow all of the enjoyable new goodies for public use in a future launch.
That is the one means we might forestall any regressions in performance and value from WordPress 3.0 to three.1. That’s proper, customers and plugin authors can nonetheless do every thing you used to have the ability to do (and somewhat bit extra).
Due to the code churn between RC2 and RC3, this launch candidate wants numerous testing. Each record display screen wants testing. Specifically, the remark moderation display screen wants testing, particularly with keyboard shortcuts (when you didn’t find out about these, now’s your probability to attempt them out).
Different fixes in RC3 embrace:
- Correctly show the creator dropdown in Fast Edit
- Numerous necessary 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 publish codecs and their rewrite guidelines
I’m assembling a bunch of mates in Washington, D.C., this weekend to check WordPress 3.1 and supply suggestions. We’d like to see this concept catch on amongst mates at espresso retailers world wide. (We’ll weblog our outcomes, and we’re interested by utilizing the hashtag #wptest on Twitter.) In case you are testing the discharge candidate and suppose you’ve discovered a bug, there are a number of methods to tell us:
We’re going to check this launch fastidiously to see the place we are able to enhance on our inner processes sooner or later. With that, our requisite haiku, authored by Jane:
Pulling the AJAX —
generally it’s good to step again
and present some restraint.