Monthly Archives: July 2008

Prologue 1.4.1

Posted on by
24

Version 1.4.1 of the Prologue WordPress theme is now available. Prologue is in the theme directory now, so if you aren’t into using Subversion this is the easiest way to grab the new version. Here’s the list of changes since the 1.3 release:

  • Fix CSS for lists (Matt Thomas)
  • Show login message when comments are disabled instead of comment form (Sam Bauers)
  • Don’t float the avatar out for the authors widget
  • Rename get_avatar( ) to prologue_get_avatar( )
  • Use make_clickable( ) in posts, makes URLs mentioned clickable. (Michael Adams, Barry Abrahamson)
  • Provide edit link for comments (Mark Riley)
  • Add theme tag: microblog (Lloyd Budd)
  • Respect time settings instead of hard coding them (Lloyd Budd)
  • iPhone style sheet (Matt Mullenweg)

If you’ve been having problems with WordPress 2.6 and Prologue please give this version a try before sending in any new problem reports.

The Future of WordPress for iPhone

Posted on by
Reply

Raanan has outlined the near future of the WordPress for iPhone app. The most interesting part though? The source code for the app is now available at http://iphone.svn.wordpress.org/. You can also browse the repository via Trac at http://iphone.trac.wordpress.org/browser.

If you’ve found a bug or have a new feature to suggest, go file a new ticket. User authentication is done with WordPress.org accounts.

WordPress for iPhone

Posted on by
9

Here’s the announcement from Matt Thomas on the WordPress for iPhone blog:

We’re live! WordPress for iPhone just launched on the App Store. Download it now and get to blogging. We’ll have more information about the project and how you can contribute soon.

If you run into issues while using the app, we’ve got a page for reporting them up now. Before you do, please check out a few frequently asked questions.

This WordPress for iPhone app uses XML-RPC to post to your blog, so if you are using WordPress 2.6 then make sure you have it enabled under the Settings -> Writing section in wp-admin.

Version 1.0 is just the beginning, we’re already planning for new features.

WordPress > Theme Directory

Posted on by
7

Bringing the new theme directory under the WordPress “extend” umbrella allowed us to take advantage of all the infrastructure that has already been built up to support WordPress.org. If you’ve browsed through the plugin directory, you’ll feel right at home in the new theme directory.

WordPress Theme Directory.

Since announcing this last night we’ve had a lot of new theme submissions. So far the responses I’ve seen have been very positive and excited about having a new central home for WordPress themes.

WordPress 2.6 – XML-RPC & AtomPub Changes

Posted on by
8

WordPress 2.6 has been released.

For those of you interested in keeping up with XML-RPC & AtomPub changes in WordPress, here’s what has changed from 2.5.1 to 2.6:

XML-RPC

  • The starify function was removed from xmlrpc.php (ticket 6634)
  • New method – wp.getUsersBlogs see Blog ID in WordPress and XML-RPC Blog APIs for some background (ticket 7130)
  • New field – xmlrpc in blogger.getUsersBlogs (same background as above, ticket 7130)
  • New method – wp.getPageTemplates (ticket 6098)
  • New field – wp_page_template in the wp.getPage method (ticket 6098)
  • New method – wp.getOptions (ticket 7123)
  • New method – wp.setOptions (ticket 7123)
  • Added support for enclosures in metaWeblog.newPost and metaWeblog.editPost (ticket 3405)
  • The <!––more––> tag is no longer embeds newlines before and after in metaWeblog.newPost and metaWeblog.editPost (ticket 6016)
  • XML-RPC is disabled by default for new installs of WordPress. Upgrading will NOT disable XML-RPC (ticket 7157)

AtomPub

  • If $_SERVER['ORIG_PATH_INFO'] is set, we use that instead of $_SERVER['PATH_INFO'] in determining the $path value (ticket 6995)
  • Fixed problem where using clean URLs (instead of ?p=1 style) would cause wp-app.php/posts requests to return zero posts (ticket 7249)
  • AtomPub is disabled by default for new installs of WordPress. Upgrading will NOT disable AtomPub (ticket 7157)

Since the story around disabling XML-RPC & AtomPub by default has gone through a few twists, I’ll re-state the current situation: new installs of WordPress will have XML-RPC and AtomPub access disabled by default, upgrades of WordPress to version 2.6 from previous versions will not have XML-RPC and AtomPub disabled as part of the upgrade process. There is no check box for enabling these services during the install or upgrade. The process for turning them back on are simple check boxes in wp-admin under Settings -> Writing.

On the security front, there are no known security issues in XML-RPC or AtomPub. If you think you’ve discovered one please email the details to security@wordpress.org.

Another point that I’ve seen a few folks bring up is the feeling that this is just the first step in removing XML-RPC and/or AtomPub entirely or that they’ll stop getting new features. These features are not going away and as for continued development and new features, go back and read the top of this post. That said, we can definitely use more people looking at the XML-RPC and AtomPub code.

If you are interested in XML-RPC/AtomPub, please come join us on the wp-xmlrpc email list.