Akhirnya sang blog engine WP dengan versi 2.7 sudah keluar, katanya interfacenya sangat luar biasa,  silahkan download disini

Apa yang baru? saya ambil dari http://codex.wordpress.org/Version_2.7

New Features

• XMLRPC Comments API (Ticket 7446)
• Keyboard shortcuts for comment moderation (Ticket 7643)
• Sticky Posts (Ticket 7457)
• Theme update api, like we do for plugins (Ticket 7519)
• Dashboard and write box rearranging (write box in trunk)
• One-click plugin installs (Ticket 6015)
• Reply to comments from admin (Ticket 7435)
• Core updating (Ticket 5560)
• Frame-like method for moderating ping/trackbacks
• Plugin browser embedded (Ticket 6015)
• PHPXref hosted on WordPress.org
• Separate Large and Full image sizes, related improvements (Ticket 7151)
• Comment threading (Ticket 7635)
• Comment paging
• Batch and inline editing (Ticket 6815)
• HTTPOnly cookies
• Column hiding for all management pages
• Post box hiding for all edit pages
• Upgrades and install over SFTP
• Template Tag wp_page_menu wrapper for wp_list_pages and support for Home page (Ticket 7698)

Developer Features

All of these features should be experimental at the moment and subject to change or removal before the final release.

HTTP API

This should be moved to its own section. I didn’t mean to actually write everything about the HTTP API. — Ticket 4779

The HTTP API is an attempt to standardize the HTTP requests and responses for WordPress. It will eventually obsolete Snoopy and deprecate the other functions in WordPress. That is, once the HTTP API is completely stable.

The HTTP API handles the response as well, so that it standardizes how you handle the final response. What is given back to you is in the form of an array, with the headers, body, and response as array keys. More will be explained about them later.

The main focus is the WP_Http class, which facilitates the HTTP requests and the transports. Transport is the term given to the classes, which handle the HTTP requests. The five supported transports are Fsockopen, Fopen, Streams, Curl, and HTTP.

The fsockopen uses the fsockopen() PHP function to handle the HTTP requests. The fopen and stream transports use the fopen() PHP function, with the latter one using the context parameter to activate the PHP streams. The Curl and HTTP transports use their respective PHP extensions to handle the PHP extensions and are the preferred transports.

The plugin developers will be handling HTTP requests using the wp_remote_request(), wp_remote_get(), wp_remote_post(), and wp_remote_head(). There are several helper functions for handling the responses, but it is advised for performance purposes to access the raw response array as much as possible. The response helper functions are wp_remote_retrieve_headers(), wp_remote_retrieve_header(), wp_remote_retrieve_response_code(), wp_remote_retrieve_response_message(), and wp_remote_retrieve_body().

There are test cases available for the HTTP API and eventually they will probably be added to the Automattic WordPress Tests repository. The current coverage isn’t that great, but is currently being improved.

Plugin Uninstaller

There is a new plugin uninstall in WordPress 2.7 that allows a plugin to uninstall itself, when the user deletes the plugin. There are two uninstall methods that the plugin can implement. One is by creating a file in the base plugin directory named uninstall.php and storing the uninstall code there. The second method is by creating a hook that will execute the uninstall routines and using register_uninstall_hook() function to register the hook with WordPress.

Comment API

The Comment API is for managing comments using the XMLRPC protocol. See Ticket #7446 for more information and progress.

Inline Documentation

The WordPress 2.7 has almost every file fully documented with phpdoc type inline documentation. This includes most of the

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.