In the Trunk

February 4, 2007

by Ryan Boren

Here’s a quick rundown of new stuff that has gone into trunk for WP 2.2.

TinyMCE 2.0.9
Prototype 1.5.0
script.aculo.us 1.7.0
jQuery 1.1.1
WP XML-RPC API (WP-specific API for working with pages, authors, and categories)
Atom 1.0 Feeds
Atom Publishing Protocol support
Better MySQL UTF-8 support
User cache streamlining
Improved options caching
Plugin sandboxing

20 Comments

Doug Karr permalink

February 4, 2007 2:28 pm

It would be pretty cool if the XML-RPC functionality was utilized with plugins to check for the latest version. Folks that publish the plugin could post some custom fields to their post with the latest versions.

Thanks! This is good info.
Jonathan permalink

February 4, 2007 3:44 pm

I have a request: can we give wp_get_archives the ability to sort archives post-by-post per category or per month? That would be schnawsome. It would eliminate the necessity of a plugin. Where can I make this request?
shorty114 permalink

February 4, 2007 4:27 pm

jQuery *and* Prototype? You’re not going to be able to use $ with both, that’s for sure… how will this non-standard thing work?
Baris Unver permalink

February 4, 2007 4:28 pm

I have a request, too I want the autosaving capability to be optional.
Jeff permalink

February 4, 2007 6:11 pm

I, too, am confused about including both jQuery and prototype. They are extremely similar libraries — it doesn’t make any sense to include them both. Not to mention obvious (and noted above) conflicts.

Unless there is something we don’t know.
Ryan permalink

February 4, 2007 8:56 pm

WP internals might move over to jQuery. We would still provide prototype because many themes and plugins use it and because we already shipped it with 2.1. We can look at using jQuery.noConflict() if needed.

Regardless of which library we use for WP internals, there is much demand to include both of these popular libraries. Bundling them allows plugins and themes to easily load them with the script loader and avoid multiple includes and version conflicts. However, since the library we decide to use internally will already be loaded for most admin pages, using that same library for plugin and theme development will save loading an extra library. We won’t try to force a library though. Out-of-the-box WP will only load the one it uses internally, but plugin authors can do as they wish.
Alan J Castonguay permalink

February 4, 2007 10:40 pm

Does TinyMCE 2.0.9 work in Safari?
Patrick Havens permalink

February 4, 2007 11:20 pm

Thanks for the list here. Are there any special things we would need to know about using these libraries? ie. WordPress specific?

Also how will the Prototype/JQuery class be handled? An option in the menu?

Sorry for the noobish questions… I’ve been wanting to play with the login and other systems using the libraries, but wanted a clue on any WordPress specific coding needed. Some basic calls for floating divs and such haven’t worked.
Dan permalink

February 5, 2007 10:18 am

Please, please PLEASE can we have mass-editing mode for posts and pages? Please? I love you?
Jeff permalink

February 6, 2007 12:21 am

Ryan, sounds good. The plugin authors for 2.2 are going to need to be very careful about the conflict between the two libraries (excepting the work around you mention .noConflict()).

I’m quite happy to hear the internal is moving to jQuery, that’s my platform of choice. *Glee*. Mmmm…chainable functions…..
Avi Alkalay permalink

February 8, 2007 11:50 am

I’d like to suggest this:

- OpenID support. Livejournal and Movabletype already has it.
- Possibility to define which and how information is included in RSS and ATOM feeds, just as HTML themes.
- Better internationalization as described here: http://avi.alkalay.net/2006/11/soleil-theme-for-wordpress.html

Thank you