Publishing content via Blog API without specifying a Blog-Name results in a published, but broken, blog node [#118959]

Steps to reproduce:

Enable Blog API core module
Publish a blog entry via Blog API

In my case, as a desktop blogging tool, I used the Gnome Blog Panel Applet ("gnome-blog" debian package)
Configuration: protocol = BloggerAPI
Configuration: address = example.com/xmlrpc.php
Configuration: initial user (user/1) and password given
Configuration: Blog-Name: not specified, by mistake
Then I wrote a blog entry (title and body text) and hit the publish button

Result: The blog entry is published on the front page, but not in the site's blog section ('example.com/blog/')

Result: Next I navigated to the blog entry under administer > content management > content. Clicking the 'edit' tab, the following error message is shown:

warning: call_user_func_array(): First argumented is expected to be a valid callback, '/_node_form' was given in /var/www/drupal-5.0/includes/form.inc on line 217.

and I can't delete this node.

Expected behaviour:

My desktop blogging tool should warn me that no Blog-Name was chosen, but it is mandatory to specify one... (Is that a bug of the gnome blogging tool? or Drupal's Blog API? or both?)
Drupal should probably provide a default content-type for content submitted remotely by Blog API (I suggest content-type 'blog' for default), even if no Blog-Name is chosen in the desktop blogging tool?

Let me know if I can provide any other information that would help.

Server: Ubuntu 6.06, Apache 2.0.55, PHP 4.4.2, MySQL 5.0.22, mod_rewrite enabled
Drupal 5.0 release, no contributed modules installed

Comments

Comment #1

pips1 commented 14 February 2007 at 12:17

I forgot to mention, I did enable 'Blog entry' as a 'Blog type' in the Blog API configuration page, previous to submitting my post via Blog API - so that shouldn't be causing the issue... Also, I enabled the 'edit own blog' access permission for 'authenticated user' (Although, it shouldn't really matter, since I posted as initial user, who has superuser rights).

To be clear: It is possible to delete the "published-but-broken" item, but I can't access the 'edit' screen to change its content or status (e.g. uncheck 'promoted to front page'), since the 'edit' screen only shows the error message I reported above.