[drupal-devel] [bug] Category selection does not work with Movable Type blogapi

Dries drupal-devel at drupal.org
Sun Aug 14 10:06:12 UTC 2005


Issue status update for 
http://drupal.org/node/24030
Post a follow up: 
http://drupal.org/project/comments/add/24030

 Project:      Drupal
 Version:      4.6.2
 Component:    blogapi.module
 Category:     bug reports
 Priority:     normal
 Assigned to:  walkah
 Reported by:  mrmachine
 Updated by:   Dries
 Status:       patch (code needs review)

I committed this patch to DRUPAL-4-6.  I won't commit it to HEAD.  We
need a better fix for this.




Dries



Previous comments:
------------------------------------------------------------------------

Tue, 31 May 2005 22:38:14 +0000 : mrmachine

Using a blog client (linux - either Drivel or BlogTK) and the Moveable
Type api, you can retrieve categories and select one for your post, but
once the post is submitted, it fails to allocate the category - making
the use of a blog tool pretty useless.




------------------------------------------------------------------------

Tue, 31 May 2005 22:45:51 +0000 : laura s

I use ecto, set to MoveableType API,but so far I'm not able to repeat
this problem. 


Could it be the client? I was also able to set Drupal's BlogAPI to the
MetaWeblog setting and it seemed to work fine -- even with ecto set to
MoveableType API. You might be able to try that as a workaround.




------------------------------------------------------------------------

Thu, 02 Jun 2005 12:04:12 +0000 : mrmachine

I tried ecto on my son's Windows box, and yes - it does set categories
correctly ... too bad there's no linux version 


but anyway, i tried changing Drupal's blogapi to Metaweblog, and kept
Drivel and BlogTK set to Moveable Type API. It didn't work for Drivel,
but it did for BlogTK ... thanx for the hint!




------------------------------------------------------------------------

Sun, 05 Jun 2005 14:36:44 +0000 : fflewddur

I've been trouble-shooting this issue using w.bloggar on Windows and
Drivel on Linux.  w.bloggar is able to post using the Movable Type API,
but the category selection only works if you click "Post", not "Post and
Publish".  Drivel, by default, publishes all posts, which is why the
category never shows up when using Drivel with Drupal.  To post entries
with categories to an official Movable Type implementation, the client
must first post the entry, then call mt.setPostCategories, and then
call mt.publishPost.  The mt.publishPost call is what seems to be
confusing Drupal, as it doesn't appear to differentiate between a post
that has been published with one which has.  Movable Type does not
publicly display posts which have not been published; it considers them
as drafts which the author has not yet finished.  Thus, Movable Type
servers require the mt.publishPost call.


I have Ethereal traces of several example posts to Drupal using both
w.bloggar in "post" and "post and publish" mode, as well as Drivel.  If
you think they'd be useful in debugging, let me know and I'll forward
them on to you.


Cheers,
Todd




------------------------------------------------------------------------

Thu, 09 Jun 2005 03:57:11 +0000 : mrmachine

has anyone had a chance to look at this since Todd debugged it?




------------------------------------------------------------------------

Mon, 13 Jun 2005 20:56:58 +0000 : mrmachine

can someone have a look at this?




------------------------------------------------------------------------

Tue, 14 Jun 2005 00:05:25 +0000 : walkah

Attachment: http://drupal.org/files/issues/blogapi-publish-post.patch (634 bytes)

having a look - it seems that mt.publishPost may well have been wiping
the term info set by setCategory.


As I only have ecto available to me currently, I can't test this
patch... but if I understand the debugging work correctly - this should
fix it. (the difference being ecto and MarsEdit - the two that I have
access to currently - don't call publishPost).


please confirm this fixes things... thanks. (I'll test more when I'm
home again at the end of the week).




------------------------------------------------------------------------

Tue, 14 Jun 2005 23:06:29 +0000 : mrmachine

beauty! this has fixed it for me!


thanx
shayne




------------------------------------------------------------------------

Wed, 15 Jun 2005 04:29:48 +0000 : baudolino

This is not fixed until a decision about whether to commit this patch is
made. Reverting this to patch status.




------------------------------------------------------------------------

Sun, 19 Jun 2005 20:25:55 +0000 : Dries

Actually, this is an annoying property of node_save() ...  I guess you
can't use node_invoke_nodeapi($node, 'insert') or
node_invoke_nodeapi($node, 'update')?




------------------------------------------------------------------------

Thu, 23 Jun 2005 17:53:32 +0000 : walkah

i'm not sure that'd make a difference, would it? isn't the issue that
$node->taxonomy is unset?




------------------------------------------------------------------------

Wed, 20 Jul 2005 11:56:50 +0000 : mrmachine

i upgraded to 4.6.2 (a tad late though - i'd been hacked), and am now
back to the original problem (i.e. - using Drivel or BloGTK, i am
unable to set the category - i can choose one, but it doesn't stick)
... i'm guessing it's because this is "not fixed" and so wasn't
committed with the 4.6.2 release.


am i able to use the same patch to "not fix" 4.6.2? in doing so, i
won't mess up any 4.6.2 security patches, will i?


shayne




------------------------------------------------------------------------

Sat, 23 Jul 2005 21:26:06 +0000 : mrmachine

"am i able to use the same patch to "not fix" 4.6.2?

"
no. no i can't. 


i'd really like to test any possible fixes. 


are there any?




------------------------------------------------------------------------

Mon, 25 Jul 2005 00:18:51 +0000 : mrmachine

has anyone managed to test this patch on 4.6.2? i haven't been able to
get it working, so i'm back to a patched 4.6.1 blogapi.module ... i
just hope this doesn't mean i'm still open to security vulnerabilities
of 4.6.1 as my site was defaced only last week ... though i'm sure the
vulnerability was only in the xmlrpc.php file.







More information about the drupal-devel mailing list