To find the blog ID to use: when you first log in to MT, you see the main menu. On the left is a list of blogs. Click on the one that you want to use in the XML-RPC bridge. In the resulting page, look at the address bar in your browser. It should contain this:



where N is a number. N is your blog ID.

Maybe I found something on this!!! I ran mt-check.cgi on my server and look what I found in part:

CHECKING FOR OPTIONAL MODULES:

The following modules are optional; if your server does not have these modules installed, you only need to install them if you require the functionality that the module provides.

   LWP::UserAgent...
       Your server has LWP::UserAgent installed.

   SOAP::Lite...
Your server does not have SOAP::Lite installed. SOAP::Lite is optional; it is needed if you wish to use the MT XML-RPC server implementation. Please consult the installation instructions for help in installing SOAP::Lite.

   File::Temp...
Your server does not have File::Temp installed. File::Temp is optional; it is needed if you would like to be able to overwrite existing files when you upload. Please consult the
installation instructions for help in installing File::Temp.


Your server has all of the required modules installed; you do not need to perform any additional module installations. Continue with the installation instructions in the section "Setting up your Blog Directories".

meryl--that is the error you're getting from Radio? That would seem to imply a problem with the path to your XML-RPC server for MT. What is the URL that you specified?

Re: the messed-up character entity decoding--I'm not sure what is causing this. I will investigate it some more tonight. I know that it will largely be fixed in 2.0, mainly because we are using XML::Parser in 2.0 (if available). But I find it odd that even the decode_html I posted into working to decode the greater-than signs (and/or less-than).

It's broken now for me, too. I did have it working at one point. The error I get is 'Poorly formed XML text, we were expecting a tag. (At character #384)'. I updated MT 1.4 last night, but I was able post from Radio after that. I even re-installed Radio this morning and haven't been successful at all.

Just a follow up note to verify: When I installed soap::lite, the api worked, but since it transports html as literal characters, it still does nothing I find useful.

Ok feeling like an idiot here:

i think the forum software is converting the less than symbols and not allowing me to demonstrate.  Tried CODE & QUOTES, but they still get converted to correct char. here in forumn as opposed to "<" which is how they appear in MT/any text editor.

I got Radio Userland 8 posting to my MT blog by using the following settings:

server:         www.myserver.com
port:            80
path:            /cgi-bin/mt/mt-xmlrpc.cgi
blogid:         1
Username:   myname
passwd:       mypassword

I had to post to my blog normally and look at the URL to determine the blog_id I wanted to use.
This works -- the posts enter into the proper blog and get published --however, I keep getting errors in Radio that say:

The server, www.myserver.com, returned error code Server: Invalid entry ID 'bloggerApiTestmanilasitescomManilaWebsite#230'

I guess it is no big deal, as I said, it IS publishing the entries to the proper blog. Anybody else got any input on this? Anybody got Category support working with it yet?

Great! Thanks, Ben. I'll try this when I get home.

gm2: good point, I should've mentioned that. If you want to use the bridge tool, you need to have the MT XML-RPC server support--that requires that you have SOAP::Lite installed.

Bill--good point about mt-xmlrpc.cgi. You're right, it was accidentally left out of the list of "Perl scripts" listed in the installation docs. Thanks!

Here are my settings:



Yes, that is the path to my cgi file.

Odd, eh?

Yes, I do have another category selected.  Actually, I've tried *not* sending to the Home category, just checking the intended blog category, but nothing appears to get published in this case.  Radio stores it OK, it just doesn't get sent to the channel.  I see this behavior using DW's std. ManilaBloggerBridge as well.

I got a similar error when trying to get Radio posting to MT and the problem was that I told Radio to go to the regular mt.cgi instead of the mt-xmlrpc.cgi. Check your config against the example I posted above and see if something might be wrong.

Radio Userland is interesting in its use of distributed computing, but outside of aggregation I find it underpowered. Particularly annoying is the fact that if you install it on two PCs, and they both point at the same Userland blog, you wipe out the work you have done on the other PC. What it needs is some way to synchronize the local sites on each of the PCs, and I am surprised they are at version 8 with something that can't sync.

The one thing I do want is a place where I can view a list of news items, check a box, and have that item posted to my MT blog.

It does concern me that I can't get any of the Blogger API tools (such as BlogBuddy) to work with my MT. I came across a client that does aggregation called NewzCrawler. It has a blog interface that works with Blogger but not with MT. In this case NewzCrawler tries to get a list of blogs from the server but can't do it, and there is no place to designate a specific blog ID. NewzCrawler gets a code 500 error from mt-xmlrpc.cgi; I suppose it is calling blogger.getUsersBlogs.

John

Dreamhost uses Debian GNU/Linux, and they are months away from upgrading it and the Perl. They tell me that about Debian
that



 I expect I'm not the only on in this situation. Are there other XML parsers I could try out with MT?

Here's a posting to demonstrate the before and after:

BEFORE (From Radio's GUI Editor)


AFTER (In MT's editor)


Again, Posting once from Radio produces 2 identical post like the above in MT.

Thanks! I couldn't figure out what to use as my blogID.

Why is it turning my links into ascii text though? *pout* I wanna be able to use links in my post.

Hi all,

I've been trying to set up Radio to post to MT and everything seems ok until it all grinds to a halt and I get this error from Radio:

Poorly formed XML text, it must end with a . (At character #140.)

Any clues anyone? I'd love to get this working.

Thanks in advance.

Rogi.
http://www.rogis.net/weblog

Is there anything specific that is being pointed out as "poorly formed text"? Is there anything else in that error message that isn't coming through in the ikonboard?

Try removing the http:// from the hostname; that might work.

Yes,

I did that first thing.  Got Radio to post to MT, but with the problems indicated above by evans and also MT has generated two identical postings.  I'm using 3-button post-n-pub in Radio, but I'm using the PnP button for these particular postings.

Reguarding the problem as described by evans, it truly does appear to only be ">" less than signs and non-breaking spaces.

I'll post some examples to show how nbsp also catches apersands as well.

The error in question appears at the bottom of the Manila-Blogger Bridge page (http://127.0.0.1:5335/manilaBloggerBridge/) in the RU local site when a new entry is posted to the Userland site. The entry posts fine. The only place this error is logged is on this page; the regular RU events log doesn't seem to capture Manila-Blogger Bridge activities.

While the error is consistent, the "Number of errors" increases with each posting: 5, 10, 13, 28, 33.

When I give the the Bridge config screen an intentionally bad path to mt-xmlrpc.cgi I get the same error, except that it is "At character #436".

That's all I've got right now.  

John

tranquileye: I agree, I am also a bit disturbed with the problems with the XML-RPC API. Another thing you might test... I recently found, in the documentation for the XML parser that I'm using, a notice that it is usable only in Perl 5.6.0 or greater. I haven't tried running it in an earlier version, but I wonder if this could be the problem? You might try checking in your webserver error logs after trying to use Radio to connect to MT (or any other tool)--see if there is an error message about mt-xmlrpc.cgi. Let me know if there is.

Ok, gonna throw another one into the fire here.

I'm also posting from http://fyuze.com/ via their implementation of the BloggerAPI into MT and I get a neutered greater-than sign error as well as less-than signs.  Only posting one message in MT though.

Thinking more about the double posting thing, I wonder if the fact that I'm using a custom version of the bridge might have something to do with Radio posting 2 times to MT?

Oh wow! Thanks, I never even noticed that. And to think, I've been pointing people at that for like 2 months. I hope this solves the problems some people have been having with it... BTW, I edited my original post so that the code is now correct. It doesn't need those backslashes you have there, and the first one should be &quot;.

I tried updating Radio.root and restarting Radio as well and the error kept coming up. Then I got a light bulb above my noggin and...
here's what happened -- in trying to figure out how to make Radio post to MovableType I had misconfigured the blogger bridge preferences and then attempted to post an article. I then fixed the prefs, posted another article and it tried to update the prior posting and generated an error. For some reason it kept doing this, even though it did not show me that initial post existed! I found it in the "ManilaBloggerBridgeData.root" file and removed it. It now works properly without any errors! Yay!

I can't get it to work either, though I can post to Blogger no problemo. The error I get is:

Poorly formed XML text, we were expecting . (At character #503.)

John

So, just to double-check--you did add the decode_html fix posted earlier in this thread?

As sent to Jeremy in email:

Weird. When do you get this error? After posting?

This error would be returned by the blogger.editPost (or blogger.deletePost) method in MT's XML-RPC implementation, because the entry ID passed is as you see there: bloggerApiTestmanilasitescomManilaWebsite#230. Now why would Radio pass in such a stupid ID? I don't know. blogger.newPost returns the ID of the new post--is the ID of that new post 230 in your MT system? That would explain that part--as for the other part, I have no idea why it would do that. It seems kind of counter-intuitive to pass in an entry ID different from the entry ID that the server just told you. :)

Getting closer... now, it's:

gm2: the encoding characters problem fix is posted earlier in this thread (post dated "Jan. 16 2002,19:43").

The key to posting from Radio8 to MT lies in two places.

One is to install the mt-xmlrpc.cgi program on your MT server.  I didn't see it mentioned in the install docs when I loaded mine.  I saw the script in the distribution files so I figured it needed to be in the same place as mt.cgi.  That's the first key; be sure you've got the mt-xmlrpc.cgi program in the same place as the mt.cgi file.

The second step is to have the proper URL set up in Radio8.  The key here is to use the same URL prefix that's used to get to your mt.cgi program.  On one of my servers this is at http://servername/mt-cgibin/mt.cgi

The prefix here is http://servername/mt-cgibin so the proper setup in Radio8 is:

Server: servername
Port:  80
Path: /mt-cgibin/mt-xmlrpc.cgi

The next three values are dependent on your local install.  Log into your MT install and make note of the number after the &blog_id= parameter.  That's the one you'll use in Radio8's Blog ID: box.  The username and password are those the same that are used to log into your MT setup.

For me it was as simple as putting the mt-xmlrpc.cgi program in the same place as mt.cgi and properly configuring Radio8.

Good luck and let us know how it goes!

-Bill Kearney

emaynard,

When you've been testing the Radio bridge, do you have more than one category selected?  Do you have a category OTHER than home selected?

Just some thoughts...

Evans

So... having waded through the whole thread... I'm still confused.  :)

What's the current verdict on either posting from Radio to both Radio and MT, or on using the XMLRPC bridge to move Radio posts to MT for good?

I've got MT 2.11 installed, and am trying to convert from Radio 8.0.7.

Thanks!

-Rick

Ok, got a response on Manila Envelope already and he says that the Blogger API support is on the to-do list. Cool.

I've gotten Newzcrawler to post to my MT installs.  It wasn't hard.  The trick was getting it to recognize one the first time.  For some reason it didn't want to do it right.  But subsequent ones have worked perfectly.

Another intersting quirk is the double posting that is occurring.

Radio -> MT yields two identical postings.

Okay, I just tested this myself, posting from Radio to MT, and it worked fine. I was able to add and edit posts. I didn't try deleting yet...

When did you receive the error that you received, Jeremy?

I really have no idea, Useland software is a law unto itself it seems. I did notice something interesting today though with Radio that might give some clue (?). I have Radio8 and use it to make a kinda 'notebook' on the web, as it's for me only I've resticted .htaccess to make the folder the sites in password protected. Now, as you know, Radio chucks RSS feeds all over the place, and I checked that these were inaccessable via my site, without the password, by asking Radio to pick up the feed. It didn't work, obviously (? again) but Radio didn't return a 'password required' message: it returned the 'poorly fomatted on line blah, blah' thing. Makes me wonder if it's simply that Radio *is* finding mt-xmlrpc ok, but simply can't/won't read it for some Userland-ish reason. Humm....

Don't worry, in version 2.0 of MT we will be able to use XML::Parser itself (rather than XML::Parser::Lite). The latter was being used to work around a UTF8 problem with Perl, but I've found another way to work around that that still allows using XML::Parser.

Your hosting provider probably has XML::Parser installed, because it's a pretty common module.

Email me if you want to test out the new version of mt-xmlrpc.cgi.

Okay, that is generally caused by an internal server error or some such on your server. You have SOAP::Lite, yes? You might also want to make sure that you have perl 5.6, as the XML-RPC support requires 5.6 in MT 1.4. (It will work with lower versions of Perl in MT 2.0.)

Wait a minute....Radio has a WYSIWYG editor, but I don't believe that fyuze.com uses one.  Matter of fact it looks pretty much like Blogger only without any HTML builder popups or anything....just a text box and a submit button.

And....I was wrong it does create double postings in MT. This is posting straight through their Blog tool to mt-xmlrpc.cgi and as metioned in previous reply, in addition to less-thans, it also mangles greater-thans as well.

I'll try non-WYSIWYG Radio posting later tonight.

Thanks Ben & Mena for a truly great system like MT.

Ok, I think this error may be due to some 'hard-coding' of some prefs in Radio. Note the name of the error and then note the name of Radio's testing website for the manila-blogger bridge:
http://bloggerApiTest.manilasites.com/
uncannily the same as the error and I bet the test blog site post is number 230 (I can't verify as I am now at work). When I get home I'll check out the prefs/settings and see what is happening. I got the error after posting two different entries, but I cannot recall now the time of the error (which Radio shows)... perhaps it was an old error that kept showing up when I made the new posts?

Well, these badly-formed messages could be due to some weird character in XML that is supposed to be encoded but isn't getting encoded in MT. Unfortunately it's rather difficult to figure out what that character *is* because I don't have access to the XML response etc.

Could you please give me a better idea of when exactly you are getting this error in Radio? As far as I know Radio only uses 3 of the blogger API methods: newPost, editPost, and deletePost. All of these methods have very short responses that shouldn't require any special encoding.

So in other words, I really need some more information. :)

I've been trying the new version for a couple of days, but it doesn't work

I'm getting the same error as before:

Poorly formed XML text, we were expecting . (At character #503.)

I don't really have a whole bunch to add - I've got it working following settings as outlined above.

Both posting and deleting are functioning OK, but I'm getting this error even so:



This is in Radio after a succesful posting

When Ben posted that inital code snippet, it was not entity encoded, or more precisely, had to expanded.

& is an &, right?
So in the regexes, the lhs has to be expanded out.
s!&amp;!&!g

So the decode function needs to look like:



At any rate, encode the LEFT HAND SIDE of the regex in the decode function as an entity and put the encoded element in instead of the ampersand character or other entity, and you should be good to go.

Its a little confusing, But not too bad.

Sorry for the ineffectual suggestion. I was hoping it would work out for you.
I kind of agree regarding Radio: it does too much in terms of just posting to MT. A simpler, leaner app would be preferable. Have you heard of Manila Envelope? Looks like it might do the trick, but I haven't been able to configure it for MT yet. I wrote the author and asked for MT support (even included the xmlrpc info for MT) so we'll see if he's game for it!

Trying to get the next page navigation to show up...

I'm seeing the exact same behavior as Evans:

[QUOTE]The weird thing is it's really only the Less Than sign and the non-breaking space. (Well, that I can see.)  The Greater Than sign gets translated fine.  Weird.
[QUOTE]

Only changes I made were those defined earlier for mt-xmlrpc.cgi  As I reported everything is flowing OK - just (how do you say?) neutering the less than and non breaking spaces when Radio posts to MT.

---

Meryl, I'm not sure what happened either.  I just now am able to see my post.  Like you said must have fallen between the cracks or something  ???