ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

ecto blogging client setup on mac

July 05, 2007 7:21am

Subscribe [4]
  • #1 / Jul 05, 2007 7:21am

    marvos

    6 posts

    Hello there,

    I’m trynig to setup my site: http://www.marvos.com with ecto:
    http://ecto.kung-foo.tv/

    Bu i can’t get it setup correctly, something is wrong with the xml-rpc file but i don’t know what that should do.
    Are there any EE users who have set it up correctly?
    Don’t know what i’m doing wrong…

    tnx,

    Marien van Os

  • #2 / Jul 05, 2007 8:12am

    Derek Allard

    3168 posts

    I’m not using Ecto personally, but we have instructions in our wiki that might help out.  Since this is third party, I’m going to move this into “how to” to get more eyeballs on it for you.

  • #3 / Jul 05, 2007 8:35am

    marvos

    6 posts

    OK great didn’t saw that, i think this will work out for me now!

  • #4 / Jul 05, 2007 8:46am

    marvos

    6 posts

    hmm i’m getting a xml error when i installed the metaweblog api
    see it over here:
    http://www.marvos.com/index.php?ACT=23&id=1

    Anybody know what’s going on?

  • #5 / Jul 05, 2007 10:24am

    Derek Jones

    7561 posts

    Your endpoint URL won’t be helpful to anyone who isn’t an registered user of your site authorized to publish to weblogs.  Can you open Window/Console and copy and paste the XML error?

  • #6 / Jul 05, 2007 10:56am

    marvos

    6 posts

    This is the error message:
      <methodResponse>

      <fault>

      <value>

      <struct>

      <member>
    <name>faultCode</name>

      <value>
    <int>105</int>
    </value>
    </member>

      <member>
    <name>faultString</name>

      <value>
    <string>XML error: Invalid document end at line 1</string>
    </value>
    </member>
    </struct>
    </value>
    </fault>
    </methodResponse>

  • #7 / Jul 05, 2007 11:05am

    Derek Jones

    7561 posts

    marvos if you’d like to email me (not PM) account information that has publishing rights on your weblog, I can try it from my installation of Ecto.  I’ve not seen that before, so the only advice I could give is to remove the Ecto account, create it anew, and make sure you select “Other” “Metaweblog API” when setting it up.

  • #8 / Jul 05, 2007 12:15pm

    Derek Jones

    7561 posts

    Ok, you are probably suffering from a PHP bug. Can you try this workaround and see if that allows you to use the API?

  • #9 / Jul 05, 2007 12:50pm

    marvos

    6 posts

    I saw that post some time earlier but it did not solve it.
    Maybe it’s a connection which is not allowed at Media Temple like described over here:
    http://expressionengine.com/wiki/MetaWeblog_API_Client_Setup/

  • #10 / Jul 05, 2007 12:57pm

    Derek Jones

    7561 posts

    It appears to be communicating fine, it’s just not receiving your XML data.  If you can email me FTP access to your site, I can try to do some additional debugging, but it’s almost certainly related.

  • #11 / Jul 05, 2007 1:47pm

    Derek Jones

    7561 posts

    Both HTTP_RAW_POST_DATA and php://input are empty.  Looks like you will need to put a ticket in with your host.  You might try setting your (mt) account to use PHP 4, as this is undoubtedly related to the PHP 5.2.2 bug.

  • #12 / Jul 05, 2007 2:00pm

    marvos

    6 posts

    Ok i’ve made a ticket of it i’ll let you now when it works (hopefully)...

  • #13 / Jul 05, 2007 6:09pm

    marvos

    6 posts

    Hi Derek,

    The switvh to php4 did the trick. Tnx for helping me out. I’m still waiting for Media Temple to come up with an answer why it doe not work with php5.. or maybe that’s not something which they can do anything about…we’ll see.

    tnx!

  • #14 / Jul 05, 2007 6:13pm

    Derek Jones

    7561 posts

    Well, it’s fixed in PHP’s cvs, so if they are insisting on running PHP5 at the current release, they can fix their installation.  Unusual that the workaround did not, well, work around it, though.  Good luck!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases