The MU forums have moved to WordPress.org

xmlprc problems with digg.com (5 posts)

  1. joshhighland
    Member
    Posted 17 years ago #

    one of the reasons i went with wpmu 1.2.1 was to make blog posts right from digg.com

    to do this you have to fill out a form with basic information about you wordpress blog

    URL, username, password.

    I do this, not problem. I get the following responce back from digg.com
    "ERROR

    There was an error accessing your blog. Please check the settings below. One of them may be incorrect. The error returned from your server was: Array"

    I check my error logs, and I dont see any errors, so I assume that digg is hitting the xmlrpc.php file just fine, but my WPMU 1.2.1 is pushing back something that is wrong.

    any idea on how to help? I have some server searches but im not finding anything on this subject.

  2. miyauchi
    Member
    Posted 16 years ago #

    Maybe, it is the same problem as our experience.

    The cause
    <data><value>
    response XML
    <data><value>...
    It solves and I think that it is because of becoming.

    I corrected it as follows.
    xmlrpc.php line 581 to 596

    $host = ereg_replace("^www\.","",$_SERVER['HTTP_HOST']);
    foreach ( $blogs as $blog ) {
    if($blog->domain == $host){
    $blog_id = $blog->userblog_id;
    switch_to_blog($blog_id);
    $is_admin = current_user_can('level_8');
    $struct = array(
    'isAdmin' => $is_admin,
    'url' => get_option('home') . '/',
    'blogid' => $blog_id,
    'blogName' => get_option('blogname')
    );
    break;
    }
    }
    if($struct){
    return array($struct);
    }else{
    return $this->error;
    }

    In NameVirtualHost, it operates above without trouble.

    Because I am Japanese, I'm sorry my English ???

  3. drmike
    Member
    Posted 16 years ago #

    If it works, I'd suggest submit a fix to trac. :)

  4. miyauchi
    Member
    Posted 16 years ago #

    When this correction was done, it came to be able to contribute with the xmlrpc client such as ecto.

    I will happy submit a fix to trac.
    thanks.

  5. Taylor0330
    Member
    Posted 16 years ago #

    Has this error been corrected in the latest version 1.3?

About this Topic

  • Started 17 years ago by joshhighland
  • Latest reply from Taylor0330