Starting in Drupal 6 the blog ID "1" is no longer accepted as a synonym for default content type, so the RSD information generated by blogapi_rsd() is now completely unusable.

The comment next to the hardcoding of 1 in this function is somewhat misleading, because it alludes to the idea that the blog ID might be used to distinguish among multiple users. In fact, it is used to distinguish from among multiple content types. The multiple users issue is resolved by the user and password arguments that are required to gain access to the API at all.

Right now I believe the RSD information is only exposed from the top-most home page of Drupal, which is a particularly awkward place to expose something accurately. Probably if anything at this top level, the blog ID should default to "blog" because somebody who has enabled the Blog API most likely has done so primarily with the intention of interfacing to their blog content type.

Ideally the system of displaying RSD would be overhauled so that RSD information with a distinct blog ID is generated, depending on the type of content that is being displayed right now. So if a user is at the root of their blog content:

http://thehost/drupal6/blog

The RSD would be generated to include a blog ID of "blog".

In general, the more omnipresent you can make RSD links on Drupal's generated pages, the more likely users will be to have a positive outcome when setting up a remote editor for Drupal. For instance, it would be nice if, for a given node entry in Drupal:

http://192.168.1.20/drupal6/node/3

The generated RSD link would be smart enough to know what kind of content that is, and generate a blog ID with the right name. E.g. "story", "page" or "blog".

Making the RSD really shine in Drupal probably doesn't sound like the sexiest of features, but I know from experience with my customers that often the choice of which CMS to use comes down to "which makes it easiest to set up with their tools." If somebody is eager to use MarsEdit or Windows Live Writer, or another desktop tool, then the increased odds of success in Drupal will make it that much more likely they will be happy with it and decide to use it.

Comments

jdfrankl’s picture

Version: 6.0 » 6.1

To address the bug part of this issue I submitted a patch for the blog ID returned by blogapi.module in response to an RSD request on issue #219818.

dpearcefl’s picture

Status: Active » Postponed (maintainer needs more info)

Does this issue exist in current D6?

dpearcefl’s picture

Status: Postponed (maintainer needs more info) » Active

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.