Skip to content
This repository has been archived by the owner on Dec 4, 2018. It is now read-only.

Adding support for posting a status with media #169

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

rinogo
Copy link

@rinogo rinogo commented Mar 1, 2013

@RWAP added support for posting a status with attached media. However, his changes were based off of the 1.0 API. This pull request combines @RWAP's changes with @aaronwaldon's proposed 1.1 API pull request.

aaronwaldon and others added 6 commits February 19, 2013 13:28
The search endpoint is no longer a separate URI (https://dev.twitter.com/docs/api/1.1). Everything else seems to work as expected, as long as the user authenticates. I have tested this with almost all GET endpoints, but not for any POST endpoints.
This change allows version 1.1 to work, while still allowing the default (version 1.0) to work as expected.
Will use the search version 1 API URI if applicable, but will use the normal API URI otherwise.
…om) for version 1.1 (while still pointing at upload.twitter.com for version 1.0).
@mrahmadt
Copy link

In Twitter API 1.1 they recommend to use url api.twitter.com for media upload https://dev.twitter.com/docs/api/1.1/post/statuses/update_with_media

also after I switch the code to support 1.1 I get this error every time I try to upload media

{"errors":[{"message":"Status creation failed: The text of your tweet is too long.","code":190}]}

[code]
$twitterObj->post('/statuses/update_with_media.json', array('@media[]' =>"@{$media};type=".$extension_mime_type[$extension].";filename={".$pathinfo['basename']."}", 'status' => $tweet));

[/code]

@mrahmadt
Copy link

I found the issues, just need to change EpiOAuth.php

https://github.com/jmathai/twitter-async/pull/148/files

@jmathai
Copy link
Owner

jmathai commented May 2, 2013

A simple merge of this caused some of the unit tests to fail. I assume it's got to do with the URL changes for 1.1.

I'll have a look later but if you want pull from upstream master and you should be able to reproduce.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants