Hi Brian,

Not sure if this will resolve your issue in COREBlog but Quills provides
MetaWeblogAPI compatibility[1]. Have a browse and see if you can use any
tips from the code :) README.txt[2] also provides some further tips[2].

-Tim

[1]
http://dev.plone.org/collective/browser/Products.Quills/trunk/Products/Quills/deprecated/MetaWeblogAPI.py
[2]
http://dev.plone.org/collective/browser/Products.Quills/trunk/Products/Quills/README.txt

On Wed, 2008-06-25 at 19:56 -0400, Brian Kennison wrote:
> Hello everyone,
> 
> 
> I've got several places and people that generated information that
> having the ability to store them and access them in a COREblog
> instance makes a lot of sense.  COREblog say that it supports several
> APIs but I'm having trouble making them work. I'm trying to post this
> data using the blogger API  but I keep getting a 403 errors. (Not sure
> what is happening) I'm calling the blogger API
> http://mysite/coreblog-instance/blogger with XML-RPC payload but as of
> yet "no love".
> 
> 
> I've searched the mailing list and web but haven't found what it takes
> to post in this manner. I saw a post from the author in  2006 that
> says that Zope/Plone should take care of the authentication but I
> didn't see a follow up.. I know a call to "blogger" creates an
> AuthBridge instance but not sure how it works.  
> 
> 
> l saw some things about the xmlrpc-client doing basic authentication
> and was wondering  if that is the case then would it be possible to
> bypass the blogger call  and just go straight to the newPost? 
> 
> 
> 
> Any insight. help, would be appreciated. 
> 
> 
> Thanks in advance,
> 
> 
> -- Brian Kennison
> 
> 
> _______________________________________________
> COREblog-en mailing list
> [email protected]
> http://postaria.com/mailman/listinfo/coreblog-en
> Unsubscription writing to [EMAIL PROTECTED]

_______________________________________________
COREblog-en mailing list
[email protected]
http://postaria.com/mailman/listinfo/coreblog-en
Unsubscription writing to [EMAIL PROTECTED]

Reply via email to