Recent Topics

[2.x] xmlsrv - LiveWriter, ScribeFire - an inventarisation

Started by on Jan 12, 2008 – Contents updated: Jan 12, 2008

1 Jan 12, 2008 02:49    

My b2evolution Version: 2.x

Hi all,

The development team is busy with the xmlsrv file. Basically that is the file where a program like Windows LiveWriter talks to when it tries to post a topic to your blog.
We want our xmlsrv to ba able to handle as much clients as possible. therefore we want you to reply to this topic if you know a program you want to be able to communicate to the blog. Do you know if the program / service function with your current blog?
From this inventarisation we will provide functioning software and a neat [url=http://manual.b2evolution.net/Desktop_Blogging_Tools]Wiki page[/url] with an installation guide.

[list]

  • [url=http://windowslivewriter.spaces.live.com/]Microsoft LiveWriter[/url]

  • [url=https://addons.mozilla.org/nl/firefox/addon/1730]ScribeFire[/url] (FireFox) addon

  • [url=http://infinite-sushi.com/software/ecto/]Ecto[/url] Mac & Win

  • [url=http://www.wbloggar.com]w.bloggar[/url]

  • [url=http://www.qumana.com/index.htm]Qumana[/url] Win & Mac

  • [url=http://www.zoundry.com/]Zoundry[/url]

  • [url=http://www.blogdesk.org/en/index.htm]BlogDesk[/url]

  • [url=http://www.blogjet.com/]BlogJet2[/url]

  • [url=http://blogtk.sourceforge.net/]BloGTK[/url] Linux - MetaWeblogAPI

  • [/list:u]

    Thanks for your help.

    *update*
    At least LiveWriter and ScribeFire will be fully (out of the box) supported by B2evo. The dev team is working on Ecto and w.bloggar. I think Quama and Zoundry will run also if I may believe their website.
    For the Techies among us: version 2.4 of B2evo does support RSD and does support four different APIs: MetaWeblog API, MovableType API, Blogger API and b2 API

    Has everybody interested in this topic read [url=http://www.smashingmagazine.com/2008/08/01/15-desktop-blogging-tools-reviewed/]15 Desktop Blogging Tools Reviewed[/url] on Smashing Magazine?

    5 Jan 14, 2008 15:56

    Thanks gr8dude,

    In B2evo the MetaWeblog API is the best supported of them all, so I think it will work out of the box in the 2.4 version.

    6 Jan 14, 2008 19:56

    Afwas, thanks for the quick response. There is one detail I must mention, an issue I described here: http://forums.b2evolution.net/viewtopic.php?t=10918

    I can't figure out what's wrong, because everything seems to be working according to the specs, yet the entire pack behaves incorrectly.

    I wrote F. Planque about it, and it seems that he cannot assign this issue a high priority. If you are currently working on this task, I can help you out by providing access to a blog where the problem shows up (I manage two b2evo-powered blogs, the issue is in both of them).

    8 Jan 14, 2008 23:50

    Is the new API supposed to work on a 1.10.x version? Or should I only try it with a 2.x setup?

    P.S. I noticed an error, the tool called "Qumana" is listed as "Quana"

    9 Jan 15, 2008 00:09

    You're not going to ruin it. Keep a copy of the original xmlrpc.php

    Good luck

    10 Jan 15, 2008 11:24

    I checked out the files from the CVS and uploaded them to the server.

    This is what is sent to the server:

    
    POST /xmlsrv/xmlrpc.php HTTP/1.1
    Content-Type: text/xml
    User-Agent: BlogDesk
    Host: lazybit.com
    Content-Length: 1552
    Cache-Control: no-cache
    
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <methodCall>
      <methodName>metaWeblog.newPost</methodName>
      <params>
        <param>
          <value>
            <string>2</string>
          </value>
        </param>
        <param>
          <value>
            <string>*****</string>
          </value>
        </param>
        <param>
          <value>
            <string>****</string>
          </value>
        </param>
        <param>
          <value>
            <struct>
              <member>
                <name>title</name>
                <value>
                  <string>tets</string>
                </value>
              </member>
              <member>
                <name>description</name>
                <value>
                  <string>sasaasdasd</string>
                </value>
              </member>
              <member>
                <name>mt_allow_comments</name>
                <value>
                  <i4>0</i4>
                </value>
              </member>
              <member>
                <name>mt_allow_pings</name>
                <value>
                  <i4>0</i4>
                </value>
              </member>
              <member>
                <name>categories</name>
                <value>
                  <array>
                    <data>
                      <value>
                        <string>Support highlights</string>
                      </value>
                    </data>
                  </array>
                </value>
              </member>
            </struct>
          </value>
        </param>
        <param>
          <value>
            <boolean>0</boolean>
          </value>
        </param>
      </params>
    </methodCall>
    
    

    The response is

    
    HTTP/1.1 200 OK
    Date: Tue, 15 Jan 2008 04:29:33 GMT
    Server: Apache/1.3.37 (Unix) PHP/5.2.1 mod_macro/1.1.2 mod_ssl/2.8.28 OpenSSL/0.9.6d
    X-Powered-By: PHP/5.2.1
    Set-Cookie: cookieb2evosession=134469_f89gJgK30B9diVbHh0uwbp3NRWj2tvEY; expires=Fri, 12-Jan-2018 04:29:35 GMT; path=/; domain=.www.lazybit.com
    Transfer-Encoding: chunked
    Content-Type: text/html; charset=iso-8859-1
    
    0
    
    

    That zero over there looks like a FALSE returned by a function.

    Is it this part?

    
    if( CANUSEXMLRPC !== TRUE )
    { // We cannot use XML-RPC: send a error response ( "1 Unknown method" ).
        //this should be structured as an xml response
    	$errResponse = new xmlrpcresp( 0, 1, 'Cannot use XML-RPC. Probably the server is missing the XML extension. Error: '.CANUSEXMLRPC );
    	die( $errResponse->serialize() );
    }
    

    As for the second server on which I had such issues; the admins migrated it to a different machine, and now everything works fine; so I only have one machine on which I can successfully repeat the problem.

    11 Jan 15, 2008 17:14

    I tried to setup BlogDesk, but to no avail. I get a persistent error

    XML Parsing Error: More than one root node found at character 11

    12 Jan 15, 2008 19:10

    Maybe you can capture the data that are sent to the server, and post the messages here? This way we can compare how the systems behave in each of the cases.

    You can use a network sniffer such as Wireshark (Ethereal), or oSpy (http://code.google.com/p/ospy/). oSpy is easier to use, because it can inject into a particular process and monitor only that process' network activity.

    You can also use a tool such as netcat ('nc', or 'netcat' if you are on Linux) to send a request and get the server's response. Netcat is like telnet, but more flexible.

    13 Jan 16, 2008 00:18

    It is confirmed to me that XMLRPC will not work with 1.10, in fact not even with 2.3. I am sorry for that. It means you'll have to wait for the release of 2.4 or get all the files of the HEAD distro from sourgeforge.
    At least your post will help the developers to get it working with BlogDesk. It does seem BlogDesk isn't handling the requests properly.

    14 Jan 16, 2008 07:58

    I slightly disagree - I have a 1.10.3 setup, and it works.

    Three things are involved: here: b2evo + BlogDesk + X
    X = the server and the software on it.

    To make it work:
    - remove the xmlrpc_debugmsg() calls in the metaweblog API
    - change something on X; I don't know what it is, because I am not a server admin and I don't know what they changed there in order to fix it. The server admins told me that "perhaps the issue is caused by PHP 5.0.5, which is known to have some bugs".

    Finally, do you mean it will not work "out of the box"? or it will not work at all (which contradicts my empirical evidence)?

    18 Jan 28, 2008 02:08

    The truth is I haven't tried it yet :oops: But it has b2evolution in its list of accepted blog services.

    19 Feb 02, 2008 23:17

    The debugged API are in version 2.4.0 and upwards.

    If b2evolution is not listed as supported by a specific desktop client, use the "MetaWeblog API" choice. Or better yet, hope that your client does auto detection via RSD (the best clients do).

    Here's the kicker: some clients will actually work better if you select MetaWeblog than if you select "b2evolution". The reason is that their b2evolution presets are designed for old versions of B2evolution with less APIs to work with.

    If you are a desktop client developer or with you are in contact with one and want to work on integration with b2evolution, please contact me directly.

    fplanque.com/contact

    20 Feb 11, 2008 01:18

    One thing that I've noticed is that live writer allows us to use tables very easily.

    The other blog desktop writers do not have this option.

    as of this writing, I'm using b2evo 2.3 rc.

    I use the standard b2evo editor except when using tables.

    21 Feb 11, 2008 01:28

    Afwas,

    To that first entry you made with the list of editors, could you add a line and tell us if those are free editors or not?

    It would be a nice addition.

    22 Jul 13, 2008 13:59

    EDIT: never mind. I'm typing the wrong xmlrpc.php URL lawlz

    23 Aug 03, 2008 17:46

    Wish Scribefire would fix their Quick Ads to work with b2 :(

    25 Aug 04, 2008 01:48

    Yeah I signed up and tried to set it up and it won't auto configure and when I tried the manual configure it won't show me the code I need. The box is just blank. I didn't see anywhere else on the site to get the code or anything about manual set up. I did file a ticket with them.

    26 Aug 05, 2008 05:51

    I changed the status of this topic from 'Global announcement' to 'Sticky'.

    27 Aug 24, 2008 10:03

    Hello,

    When I edit and published any blog from Windows Live Writer the publish date is replaced by the current date and time. Is their any way to restrict this? Please advice. I am using B2Evolution 2.4.2 and Live Writer V 2008

    Thanks and Regards
    Suman Kundu
    Website: http://www.sumankundu.info

    28 Sep 02, 2008 05:26

    For MS Live Writer, when I try to save a post with images on it, I get the following error:

    The following images cannot be published because the weblog does not support image publishing

    I checked my media folder and it has the right permissions (777).

    Do you know where Live Writer tries to save the images to?

    29 Sep 05, 2008 19:56

    You're not going to ruin it. Keep a copy of the original xmlrpc.php

    Good luck

    30 Sep 11, 2008 06:16

    Looks to me post this is more for the Wiki than for the forums.
    I will "unsticky" this post. But do add your comments suggestions and adventures in this topic.

    31 Sep 11, 2008 06:34

    Afwas,

    did you get a chance to see my question?

    For MS Live Writer, when I try to save a post with images on it, I get the following error:

    The following images cannot be published because the weblog does not support image publishing

    I checked my media folder and it has the right permissions (777).

    Thoughts?

    32 Sep 11, 2008 06:43

    Hi Edgar,

    Unfortunately I can't help you with that question. I completely moved to Linux so LiveWriter won't run on my computer.
    Looks to me like LiveWriter hasn't got this programmed correctly, but on hte other hand it may be a flaw in the htsrv that picks up the request from Live Writer.

    I hope somebody else has an idea.

    Good luck

    33 Oct 15, 2008 13:20

    I also have problem with Live writer and images, standrad text post works well. But when i try to include images I get a error message that say:

    Server error 822.
    Invalid post contents... ... Tag <img> may not have right attribute style="..." //

    I have the latest version of B2evolution (2.4.5) installed.

    My server blogg.clmedia.nu

    Anyone that have an ide of what to do to make it work?

    34 Oct 16, 2008 03:12

    I had this issue recently. The way to fix it is to disable CSS checking in the back office.

    Go to the Users tab and click on the Group for the user you want LiveWriter access. Then uncheck the "Prevent CSS tweaks" box


    Form is loading...

    Secure CMS – This forum is powered by b2evolution CMS, a complete engine for your website.