The mystery thickens....

http://www.nbrightside.com/sandpit/suicidal-post
(Post ?)

http://www.nbrightside.com/sandpit/%25r7zdkwuhtw%25   (Live Preview ?)

No errors reported in Manage-Logs

On Aug 27, 8:45 am, Andy C <[EMAIL PROTECTED]> wrote:
> Habari SVN 2385
> ScribeFire 2.3.2
> Firefox 3.0.1
> Metalog API
> Direct connection (no proxy)
>
> Blog system: MetaWeblog API
> API URL: http://<mysite>.com/blog/xmlrpc
>
> [ Not http://<mysite>.com/blog/xmlrpc.php ]
>
> Auto-detect works fine and ScribeFire connects OK
>
> One error reported presumably while retrieving posts - looks like
> posibly malformed HTML from an antique post from my WordPress blog.
>
> The API at the URL you entered appears to not exist.
>  Please make sure that you have the correct url and try again.
> XML Response:<pre class="error">
> <b>Warning:</b> SimpleXMLElement::addChild() [<a
> href='simplexmlelement.addchild'>simplexmlelement.addchild</a>]:
> unterminated entity reference  Ride' scheme which entails parking on a
> residential road and walking through Wimbledon Village, admiring the
> beautiful people, en-route to Wimbledon Tennis Club on Church Road.
> <snip>
>
> Retreives tag list OK
>
> Live preview of a new post reports
>
> The API at the URL you entered appears to not exist.
>  Please make sure that you have the correct url and try again.
> XML Response:<pre class="error">
> <b>Notice:</b> Object of class XMLRPCStruct could not be converted to
> int in system/classes/posts.php line 106
> </pre>
>
> Publish reports
>
> The API at the URL you entered appears to not exist.
>  Please make sure that you have the correct url and try again.
> XML Response:<?xml version="1.0" encoding="UTF-8"?>
>
> <?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/
> atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet
> href="http://feeds.feedburner.com/~d/styles/itemcontent.css";
> type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/
> Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/
> 1.0"><title>Blog in isolation</title><subtitle>Digging in a Habari
> sandpit</subtitle>
>
> Using /atom as the endpoint reports
>
> The API at the URL you entered appears to not exist.
>  Please make sure that you have the correct url and try again.
> XML Response:<?xml version="1.0" encoding="UTF-8"?>
>
> <?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/
> atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet
> href="http://feeds.feedburner.com/~d/styles/itemcontent.css";
> type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/
> Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/
> 1.0"><title>Blog in isolation</title><subtitle>Digging in a Habari
> sandpit</subtitle
>
> Thought problem might be with my use of Feedburner so tried a 0.5
> vanilla install.
>
> Existing entries could not be retrieved but tags could.
>
> Preview and Publish reported
>
> The API at the URL you entered appears to not exist.
>  Please make sure that you have the correct url and try again.
> XML Response:<pre class="error">
> <b>Notice:</b> Object of class XMLRPCStruct could not be converted to
> int in system/classes/posts.php line 106
> </pre>
>
> On Aug 27, 7:54 am, "Michael C. Harris" <[EMAIL PROTECTED]>
> wrote:
>
> > On Wed, Aug 27, 2008 at 08:41:28AM +0200, Lars Oeschey wrote:
> > >    tried MarsEdit as well now, when setting to AtomPub I can't connect (is
> > >    /xmlrpc the correct URL then?), setting to Metalog API it *seems* to
> > >    connect, but I don't get a list of posts, and the posts I send don't
> > >    appear in the blog (neither as draft nor published)
>
> > /atom for AtomPub.
>
> > --
> > Michael C. Harris, School of CS&IT, RMIT 
> > Universityhttp://twofishcreative.com/michael/blog
> > IRC: michaeltwofish #habari
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/habari-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to