Support » Fixing WordPress » Ecto Image Upload: Still No Fix?

  • I’m unable to upload images using ecto 2.4.2 with either WP 2.0.x or 2.1. I get the following error message:

    Could not parse response for file upload. Please check the console log for more information.

    And here’s the content of my console log:
    Request with URL:
    http://fivethousand.net/blog/xml-rpc.php
    and data:
    <?xml version="1.0" encoding="UTF-8"?>
    <methodCall>
    <methodName>metaWeblog.newMediaObject</methodName>
    <params>
    <param>
    <value><string>1</string></value>
    </param>
    <param>
    <value><string>******</string></value>
    </param>
    <param>
    <value><string>******</string></value>
    </param>
    <param>
    <value><struct>
    <member>
    <name>bits</name>
    <value>REMOVED</value>
    </member>
    <member>
    <name>name</name>
    <value><string>wp-content/uploads/2007/01/designer.jpg</string></value>
    </member>
    <member>
    <name>type</name>
    <value><string>image/jpeg</string></value>
    </member>
    </struct></value>
    </param>
    </params>
    </methodCall>
    Response:
    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <HTML><HEAD>
    <TITLE>406 Not Acceptable</TITLE>
    </HEAD><BODY>
    <H1>Not Acceptable</H1>
    An appropriate representation of the requested resource /blog/xml-rpc.php could not be found on this server.<P>
    </BODY></HTML>

    Some Googling looks makes it looks like this is an outstanding WP issue, not an ecto issue, but I can’t figure out if it’s ever been resolved or if there’s a fix for it. Does anybody have any input?

Viewing 6 replies - 1 through 6 (of 6 total)
  • One other thing…I forgot that I had to change the name of my xmlrpc.php file because of securty restrictions from my host. I changed it to “xml-rpc.com.” Is there something within the xml-rpc.php file that I need to change as well?

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    If you renamed the xml-rpc.php file, then you probably broke it. Change the name back to make it work correctly.

    What ‘security restrictions’ did your host have? If my host told me that sort of thing without explaining it, then they would no longer be my host. You might try switching hosts, to one with a clue.

    Thanks, Otto. Your comment is so self-satisfied and ridiculously unhelpful that it’s almost painful to read. If you decide you want to join in a productive discussion instead of using your keyboard to intellectually masturbate I’ll still be here trying to solve a problem.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Huh? I answered your question as plainly as I know how.

    1. Renaming the file will break that functionality. Really. I’m not kidding.

    2. If your host says that they wanted it named differently for “security reasons” then they are either a) idiots, b) deluded idiots, or c) misreading some kind of security bulletin somewhere. There is no valid reason to rename the xml-rpc.php file. The whole reason it exists is specifically so both you and others have access to its functionality.

    How is this unhelpful? I gave you the best answer possible.

    When you’re ready to listen to the actual answer, even though you may not like it, I’ll still be here, helping people who actually are capable of receiving help.

    Your opinion of my host’s intellectual acuity is of no help. Regardless of what you think of them (and you have no idea who they are, or what I’ve discussed with them), they’ve disallowed access to files named xmlrpc.php so glib answers like “change the name back” are likewise unhelpful.

    I couldn’t care less whether there’s a valid reason to rename the xmlrpc.php file unless that discussion is part of you giving constructive feedback about finding a solution or at least concretely isolating the problem. I am interested in the status of an ongoing ecto/WP issue that’s affecting plenty of other users most of which haven’t had to change a file name, which you’d know if you looked into it at all.

    More focus, fewer attacks.

    Thanks.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Ecto Image Upload: Still No Fix?’ is closed to new replies.