WordPress 3.1 Launch Candidate 3 – San Francisco

WordPress 3.1 Launch Candidate 3 is now out there. 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 evaluate the modifications you probably have been creating towards a beta or RC model.

The largest change is the removing 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 may leverage. Sadly, with extra testing got here realizations that there have been too many main bugs and usefulness points with how the performance was applied, so we’ve spent the final week rolling again crucial parts of the function.

  • For customers: AJAX has been totally disabled for the listing tables. We hope to convey this again once more, in a type that’s correctly and absolutely applied, in a future launch. Column sorting stays, however every thing else has returned to its 3.0 state.
  • For builders: All the listing desk API is now marked non-public. For those who try and leverage new elements of the API, you might be 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 method we may stop any regressions in performance and usefulness 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 a bit 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 (in case you didn’t find out about these, now’s your likelihood to attempt them out).

Different fixes in RC3 embrace:

  • 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 internet.config on permalink save
  • Correctly validate publish codecs and their rewrite guidelines

I’m assembling a gaggle 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 world wide. (We’ll weblog our outcomes, and we’re occupied with utilizing the hashtag #wptest on Twitter.) If you’re testing the discharge candidate and assume you’ve discovered a bug, there are a number of methods to tell us:

To check WordPress 3.1, attempt the WordPress Beta Tester plugin (you’ll need “bleeding edge nightlies”). Or you possibly can download the release candidate here (zip).

We’re going to check this launch rigorously 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 —
typically you should step again
and present some restraint.

Glad testing!


Cogknockers is a San Francisco WordPress Development Agency with 20+ Years Experience.  WordPress Design is at the core of our services.

Share this post

Share on facebook
Share on google
Share on twitter
Share on linkedin
Share on pinterest
Share on print
Share on email

0

Scroll to Top