Backbone (and Underscore!) are bundled with WordPress – explore how you can leverage their power to deliver complex user experiences while keeping your code organized and maintainable.
First, we will explore why Backbone is awesome, and what it lets you create is amazing! We will look at some examples of where and how it is used to power web apps and increasingly large areas of the WordPress dashboard. Seeing these incredible user experiences built in Backbone will help get you excited about using Backbone in your next project.
Next, we will dig into Backbone fundamentals to get a crystal clear understanding of the fundamental concepts underlying Backbone applications: Models, Views and Collections. We’ll look at how these tie to templates, events and routes for rendering, interaction and state handling. We discuss using Backbone in themes and plugins: how to include Backbone, how to interact with the back end to get and put data, including using the new WP REST API. We will cover WordPress specific helper functions that help our Backbone projects.
Finally, we will explore several very simple Backbone applications that demonstrate interacting with WordPress using the Rest API.
The revisions system in WordPress has been given a complete overhaul in the new (upcoming) Version 3.6 of WordPress. The new version of revisions patches several longstanding bugs and issues with the revisions system and introduces a slick new user interface for viewing and comparing revisions.
The revisions interface focuses on two primary use cases: undoing mistakes by finding the last correct revisions, and reviewing changes as part of an editorial workflow. To improve these uses, a completely new UI was created, and numerous bugs were fixed.
Highlights of new Revisions features for WordPress 3.6
Revisions Rewrite using Backbone.js – this complete reworking of the way users interact with the stored revisions combines immediate screen updates with a scroller that makes exploring revisions quick and easy. Massive effort was put into refining, testing and improving the system – it allows rapid scrobbing through up to hundreds of revisions. Quickly locate the revision you need and restore it; also allows comparing of any two revisions – no more clicking and waiting to see a comparison, just scroll through to find the revision you need – #23497
Store a copy of the current post data as a revision – keep the revisions data current – previously only the previous save was stored as a revision, now the current save is stored as a revision. #16215
Filter to override WP_POST_REVISIONS (or define it later) – allows you to disable or set the number of revisions allowed on a per site basis setting on a multisite install – #22289
Pass post ID to post revision field filter – #19932
What’s Fixed in Revisions for WordPress version 3.6
Previous versions of WordPress had several problems with the revisions system that have been corrected in the 3.6 release. The following significant bugs were addressed in this release cycle:
Duplicate autosave/revisions clutter the database (because revisions are saved even if nothing has changed) – #9843
Extra revision created every time a new post is inserted– by the first time you published a post, there were already two revisions – #24708
Restoring post revisions does not update _edit_last– now the revisions system tracks who last restored a post revision – #20982
Post Revision history displays the incorrect author – the old system stored a revision before updating a post, yielding bad data that 3.6 corrects. #16215