Recent Topics

1 Jun 14, 2003 19:20    

I'm currently using WordPress 0.71, another fork in the road of b2 evolution (no pun intended), and thought I'd take b2evolution out for a spin. I wanted to try blogging to b2evolution with w.bloggar, but experienced the same problem I had trying to use w.bloggar with WordPress.

I get an error message returned by w.bloggar that it can't parse the blog post because it's encountered more than one XML top level (root) element.

Has anyone got a fix for this?


2 Aug 17, 2003 20:37

This w.bloggar issue will be fixed in the next release.

3 Aug 18, 2003 01:29

Thanks very much for fixing this problem. I'll look forward to trying this out.

4 Sep 26, 2003 06:07

Still getting an XML error with w.bloggar

Unable to parse the XML response... Parser Reason: Only one top-level element is allowed in an XML document.

b2evo version is
w.bloggar version is v3.02

Should it be fixed in this version or no?

5 Sep 26, 2003 13:59

it *is* fixed in the latest release candidate. (

6 Sep 26, 2003 16:39

It's that extra .2, I get it now. I will blow it away and try again.


b2evo is great stuff, by the way.

7 May 19, 2004 05:38

I am using b2evo
and w.bloggar 3.03.0165.

I am getting the following error message in w.bloggar:

Unable to parse the XML response. Parser Reason:XML document must have a top level element.


8 May 29, 2004 15:37

Okay, I got the same error, using the same version of b2evo and bloggar...

I found the bug:

simply edit the file : "xmlrpc.php", line 19 and replace:

require_once(dirname(__FILE__).'/../$core_subdir/_main.php' );


require_once(dirname(__FILE__).'/../b2evocore/_main.php' );

why? since "xmlrpc.php" is directly accessed, "$core_subdir" should not been defined before...

Edit: already mentionned [url=]here[/url] ;)

9 Mar 07, 2005 15:15

I'm using b2evo v and w.bloggar 4.00.0191 and I wasn't able to connect until I made the chage you suggest to xmlrpc.php. The thread you link to has a different change, and it didn't help me. So now I can connect and post, but it still throws up that error message about top level element every so often.

I was using a few weeks ago, and I could post from w.bloggar without any hacking. Did this bug get reintroduced?

Form is loading...