The fifth (and likely the final beta) build release (version 0.9.360) is now available for download. This release contains mostly bug fixes and a few enhancements.

• Added support for Flickr media storage (image upload).
• HTTP Proxy support. See Tools -> Preferences -> General -> Proxy. Note that the current implementation does not support Google ClientLogin (i.e. Blogger.com and Picasa). Updated July 24, 2008 - Version 0.9.363 supports Google ClientLogin via HTTP Proxy - please see this forum post.
• When image files are dropped into the editor, a dialog box is shown to allow you to choose the thumbnail size settings.
• Width and height attributes of <img> tags are automatically generated if they are not set (images without these attributes do not work on WordPress.com hosted site).
• The <img> tag ALT attribute is now automatically set (derived from the filename) when you drag and drop an image into the editor.
• When you drop attachments/files into the editor, the <a> tag TITLE attribute will be set with the file name and file size.
• The Src input field in the Image Properties dialog now supports paths that start with underscores as well as UNC paths.
• The XML-RPC layers uses local Date Time format (instead of UTC) for TextPattern. This is a work around until TextPattern's XML-RPC layer plugin supports UTC.
• The src attribute in <img> elements for Picasa urls contain the imgmax parameter. This parameter is now also applied to href attributes in <a> elements. E.g. link from a thumbnail image to larger image. (If the imgmax parameter is not added on to the URL, then Picasa server returns the large images as attachments which forces the browser to prompt the "Open With" or "Save As" dialog.)
• WordPress specific:
• • When you remove existing tags for a post and update the post, the tags are removed from the WP entry.
  • You can now set WP per-post password.
  • You can now change the WP post status such as Pending, Private etc.

WordPress 2.6 users should enable Remote Publishing on the WP server.

As usual, many thanks goes to all our users for taking the time to send us feedback as well as bug reports.

Labels: beta, download, portable, raven, raven2go, releaseNotes

Raven and most other desktop clients use the XML-RPC api on WordPress in order to publish posts as well as to download posts. The XML-RPC api is normally shipped enabled with WordPress version upto version 2.5.x.

Beginning with WordPress 2.6, the XML-RPC api is disabled by default. To use Raven with WordPress 2.6+, you must enable XML-RPC Remote Publishing via WP Administration Console.

1. Login to WordPress 2.6 Administration Console and goto Settings -> Writing.
2. Check the "XML-RPC" checkbox found under the Remote Publishing section. (see screen shot below).

You can find more information on this issue via RedSweater and the original WordPress Trac Ticket.

Labels: development, raven, wordpress, xml-rpc

As you know, Raven allows you to set the post date-time stamp to a future date time. In in previous versions, when you post an entry with a future date-time, the blog post URL (link location) is available (to Raven) as soon as you post it. Having the blog post URL is very useful - especially, if you want to view the post online, or refer to it (i.e. link to it) with in Raven in another post.

Recently, I noticed that Blogger no-longer returns the blog post URL if the post date-time is set for a future date (or if your PC clock date-time is faster than that of Blogger servers date-time).

According to Google's Blogger developers, this is "as designed" - i.e the post URL is not returned for posts with future date-time stamps. We do not agree with this design, but it is their design.

What we have done as a work around (with build 336), is that Raven will attempt to 'refetch' the blog post URL the next time you run "Download Recent Posts". Even in this case, the URL is available only if the blog posts' date-time is either 'now' or in the past - relative to the time you ran "Download Recent Posts".

Labels: blogger, development, issues, raven