1 froop May 21, 2006 04:58
3 balupton Jul 06, 2006 03:43
can you enlighten me on what w.bloggar is?
4 froop Jul 06, 2006 05:33
Sure. It's a program that connects through the XML-RPC API and allows me to update my blog. It worked fine on the old 0.9.x releases though.
Website is http://wbloggar.com/
5 blueyed Jul 06, 2006 19:44
balupton, would you like to test and look into this issue?
6 balupton Jul 07, 2006 01:31
Edit:
It's a problem on b2evolutions end, as the xmlrpc.php folder returns:
<?xml version="1.0" ?>
<methodResponse>
<fault>
<value>
<struct>
<member>
<name>faultCode</name>
<value><int>103</int></value>
</member>
<member>
<name>faultString</name>
<value><string>XML error: no element found at line 1</string></value>
</member>
</struct>
</value>
</fault>
</methodResponse>
Which is obviously not what w.bloggar is looking for hence the error ur getting.
I will look into it more now.
Edit:
The problems happening in /blogs/inc/_misc/ext/_xmlrpcs.php here
xml_parser_set_option($parser, XML_OPTION_CASE_FOLDING, true);
// G. Giunta 2005/02/13: PHP internally uses ISO-8859-1, so we have to tell
// the xml parser to give us back data in the expected charset
xml_parser_set_option($parser, XML_OPTION_TARGET_ENCODING, $xmlrpc_internalencoding);
xml_set_element_handler($parser, 'xmlrpc_se', 'xmlrpc_ee');
xml_set_character_data_handler($parser, 'xmlrpc_cd');
xml_set_default_handler($parser, 'xmlrpc_dh');
if (!xml_parse($parser, $data, 1))
{
// return XML error as a faultCode
$r=new xmlrpcresp(0,
$xmlrpcerrxml+xml_get_error_code($parser),
sprintf('XML error: %s at line %d',
xml_error_string(xml_get_error_code($parser)),
xml_get_current_line_number($parser)));
xml_parser_free($parser);
}
7 balupton Jul 07, 2006 01:53
Besides what i just posted, i have no clue what is going on.
I've posted the problem in the w.bloggar forums here;
http://wbloggar.com/usersforum/viewtopic.php?t=168&start=0&postdays=0&postorder=asc&highlight=
To see if they can shed some light on the issue.
8 blueyed Jul 08, 2006 19:04
I'll look into it now.. VMWare to the rescue..
9 blueyed Jul 08, 2006 20:19
I cannot reproduce it here. Neither locally nor on:
demo.b2evolution.net/v-1-8/blogs/xmlsrv/xmlrpc.php
I'm using w.bloggar 4.00, maybe they have fixed it there?
10 balupton Jul 08, 2006 20:21
yeh im using the version... Are you using the IE or Mozilla build? Maybe that has something to do with it.... - I'm using the IE build.
11 balupton Jul 08, 2006 20:23
Just tried it then..... And working fine for me..... Even though i have not updated anything....
12 blueyed Jul 08, 2006 20:28
I've used the Mozilla build.
13 froop Jul 09, 2006 03:03
I'll grab the Mozilla build and give it a shot. I didn't really think it would make any difference as I figured it was just the engine it was using to generate the previews.
I'll drop back in when I test it.
14 balupton Jul 09, 2006 03:12
Well what i was saying is that i was using the IE build, and now it is working without flaw... They must retrieve information from the server on how to work.... Because i haven't updated anything and now it's working...
15 froop Jul 09, 2006 04:33
I have no idea. The Mozilla build still does the same thing for me.
It never occured with the 0.9.x series so I figure there is a bit of code that got changed in the CVS builds.
16 balupton Jul 09, 2006 04:40
Well it's working for me and blueyed just fine...
I was getting your error before, but i tried it last night and it was working with no problems...
And i haven't updated w.bloggar or b2evo since my first and last try.
17 froop Jul 09, 2006 05:00
It is strange...
I might see if I can find another tool and see if it gives me any kind of error.
18 blueyed Jul 09, 2006 08:56
froop, could you please post some more informationm that gives us a chance to reproduce it?
what w.bloggar version are yuo using?
What text are you trying to post?
Which b2evo version are you using?
Have you tested it with them demo site?
19 froop Jul 09, 2006 09:08
The latest w.bloggar version. Both IE and Mozilla editions.
Text I am posting? Well everything I post brings the error. http://frooptech.net/ if you wanna check it out.
Latest CVS version. Updated probably every second day or so.
I haven't tested it with the demo site. Didn't realise I could. I'll give it a try sometime.
20 froop Jul 11, 2006 05:39
It seems it may be a w.bloggar issue.
I've tried a few other programs and none of them seem to have the same issue.
Strange.
21 blueyed Jul 11, 2006 19:09
Does it happen with the demo site?
Use demo.b2evolution.net/HEAD/blogs/xmlsrv.php for it.
It may be a xmllib problem or something (which PHP uses).
22 froop Jul 11, 2006 19:41
Works fine on the demo site. Not on my site though.
Next time I update it from the CVS I might delete all the files and re-upload them and see if it makes any difference. I can't see why it would but I can always hope.
EDIT: Just pondering something. Maybe it has something to do with the Post ID or something. My site has easily a couple of 100 posts while the test site only has a few. Just popped into my head because w.bloggar pops up it was successful with a post id when your done.
23 blueyed Jul 11, 2006 19:47
This will probably not help.
Rather try comparing the phpinfo() output of your site with the one from the demo site. It's linked there.
My guess still is that it's a libxml issue and you would need to rebuild your php with a more recent one or try upgrading your PHP in general. Both might be not an option unfortunately, sorry.
24 balupton Jul 11, 2006 19:47
When blueyed mentioned xmllib, he was referring to a built in library with php. You can find out what version you have by;
<?php echo phpinfo(); ?>
And you should see something like;
xml
XML Support active
XML Namespace Support active
EXPAT Version 1.95.6
So if you can post that, and your php version maybe thats the reason...
But like i said before, i was getting the same error as you when you mentioned it, then when blueyed said he didn't have the problem i tested again, and this time i didn't have any error. And i did not update or change anything in between both tests.
Edit: beat me to the chase blueyed.
25 froop Jul 11, 2006 19:53
xml
XML Support active
XML Namespace Support active
EXPAT Version expat_1.95.7
Yeah. It WAS working fine. Definetly with the 0.9.x series. And it still posts fine aswell... it just pops an error up after the post.
Other programs I have tried have no dramas with it either... so I have no idea what the go is.
26 balupton Jul 11, 2006 19:57
Go crazy in the w.bloggar forums ;) - probably the best solution...
But yeh, in my case it didn't work one day, and worked the next, but for you it never worked...
My guess is just that there is a wierd bug in w.bloggar.
27 froop Jul 11, 2006 20:05
I think I'll probably just give up and stick with Zoundry Blog Writer now. The support on the w.bloggar forums looks to be pretty non-existant and the guys working on Blog Writer are pretty helpful and open to suggestions.
28 jarfil May 21, 2007 19:43
I've just come across this problem, and it's due to the use of $HTTP_RAW_POST_DATA in inc/_misc/ext/_xmlrpcs.php.
As you can [url=http://bugs.php.net/bug.php?id=22338]read here[/url], $HTTP_RAW_POST_DATA is not set when php register_globals=off. That would explain reports about it stopping to work suddenly.
The fix is to use this instead:
file_get_contents("php://input")
Right now, I've found use of HTTP_RAW_POST_DATA in 1.9.1, 1.9.2, 1.9.3, 1.10.0 and CVS, in the following files:
[url=http://evocms.cvs.sourceforge.net/evocms/b2evolution/blogs/inc/_misc/ext/_xmlrpcs.php?revision=1.7&view=markup]blogs/inc/_misc/ext/_xmlrpcs.php[/url]
lines: 406, 544 and a bunch of global defs
[url=http://evocms.cvs.sourceforge.net/evocms/b2evolution/blogs/cron/mms.php?revision=1.9&view=markup]blogs/cron/mms.php[/url]
lines: 37 and 680
29 yabba May 21, 2007 20:06
just for reference : [url=http://forums.b2evolution.net/viewtopic.php?t=11662]mms.php[/url] bug
¥
30 blueyed May 21, 2007 21:46
Here's a patch I've just committed to v-1-10 and which should fix this, by setting $HTTP_RAW_POST_DATA from php://input, if it's not set already:
Index: ./blogs/cron/mms.php
===================================================================
RCS file: /cvsroot/evocms/b2evolution/blogs/cron/mms.php,v
retrieving revision 1.1.4.3
diff -u -r1.1.4.3 mms.php
--- ./blogs/cron/mms.php 4 Nov 2006 19:54:50 -0000 1.1.4.3
+++ ./blogs/cron/mms.php 21 May 2007 19:44:26 -0000
@@ -21,6 +21,13 @@
*/
require_once dirname(__FILE__).'/../conf/_config.php';
+
+if( ! isset($HTTP_RAW_POST_DATA) )
+{
+ $HTTP_RAW_POST_DATA = implode("\r\n", file('php://input'));
+}
+
+
require_once $inc_path.'_main.inc.php';
param( 'login', 'string', '', true );
@@ -737,4 +744,4 @@
* cleanup
*
*/
-?>
\ No newline at end of file
+?>
Index: ./blogs/xmlsrv/xmlrpc.php
===================================================================
RCS file: /cvsroot/evocms/b2evolution/blogs/xmlsrv/xmlrpc.php,v
retrieving revision 1.105.2.4.2.2
diff -u -r1.105.2.4.2.2 xmlrpc.php
--- ./blogs/xmlsrv/xmlrpc.php 25 Apr 2007 22:18:17 -0000 1.105.2.4.2.2
+++ ./blogs/xmlsrv/xmlrpc.php 21 May 2007 19:44:27 -0000
@@ -51,6 +51,16 @@
$post_default_title = ''; // posts submitted via the xmlrpc interface get that title
+
+// Setup $HTTP_RAW_POST_DATA, used by xmlrpc lib:
+if( ! isset($HTTP_RAW_POST_DATA) )
+{
+ $HTTP_RAW_POST_DATA = implode("\r\n", file('php://input'));
+}
+// Trim requests (used by XML-RPC library); fix for mozBlog and other cases where '<?xml' isn't on the very first line
+$HTTP_RAW_POST_DATA = trim( $HTTP_RAW_POST_DATA );
+
+
/**
* Used for logging, only if {@link $debug_xmlrpc_logging} is true
*
Still getting this bug. I didn't with the 0.9.x releases but I have been getting it since moving to the CVS versions.
Is it a bug in the CVS or is w.bloggar just not doing something right?