• I’m in the process of developing a photon-like upload mechanism for Picasa. Okay, now that I have your attention…

    The metaweblog.newMediaObject function appears to be broken in WP 2.0, which is what I’m primarily developing on. It doesn’t have the function wp_upload_dir(), which I assume is because of the new paradigm for uploads associated with posts. At any rate, it’s broken.

    On WP 1.5.1, the newMediaObject call goes through okay, and it saves a file on the other end, but it doesn’t seem to be base64-decoding it.

    Are these issues with know workarounds?

    Thanks,

    Mike

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter mikepurvis

    (@mikepurvis)

    On WP 1.5.1, the newMediaObject call goes through okay, and it saves a file on the other end, but it doesn’t seem to be base64-decoding it.

    This has been corrected, it was a problem in the client. Uploads now work correctly with WP 1.5.x, and also with Typo, but WP 2.0 is broken.

    Is there any possibility of getting back WP-1.5-like upload behaviour in 2.0? Or is every upload going to have to be associated with a post?

    Hi Mike.
    I have the same behavior. I think a “bug” in the xmlrpc.php isn’t fixed in the svn for now.

    The bugfix is documented here:
    http://trac.wordpress.org/attachment/ticket/1008/base64.diff

    The RFC for MetaWeblog-API and the newMediaObject-Call says:
    “[..]bits is a base64-encoded binary value containing the content of the object.[..]”
    http://www.xmlrpc.com/metaWeblogApi
    so i think you should send a base64-encoded-string which must be decoded from xmlrpc.php.

    I don’t now why it isn’t commited so far? Can anyone tell us please?

    Thanks
    kelloggz

    Ups, haven’t seen the date from your post 😉

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WP 2.0 Upload-by-XMLRPC’ is closed to new replies.