G’day! I am SO hoping someone here can here me. I have read all the FAQ’S, support sections etc and am understanding that my Twitter app does not currently work because I need to update
My blog is called What’s On The List
http://www.whatsonthelist.net
I cannot comment on my own blog or on other people’s blogs using my Twitter app currently as I get an error message saying:
Error: your Twitter login has expired.
In one of the forums, it suggested I needed to go into my Setting, then Twitter Widget…I could not find my Twitter widget …
Can someone please be patient with me, talk to me like I am five and walk me through what I need to update?
I have posted my question on the wordpress.com forum, but while a number of people are affected, no one seems like they know (like me) what to do!
Thank you in advance.
I had a free blog, then update, bought the name, and transferred it to wordpress.com to host
Cheers! Look forward to your replies! Joanne
Well done Twitter.
Documentation is absolute horrible, a real change log not available, nothing works awhen you stay to the documentation and the best is that the great response means that literally EVERYTHING could be wrong.
From a perfect working system to nothing in an instance. Well done Dev’s.
So…if it no longer works, what do we use to get the Twitter feed back on our websites?!
episod
#125
You’ll likely be unable to continue following feeds of Twitter users in Feedly unless they supported some other format than RSS. Our API responses require some form of auth now and return in JSON. I would let Feedly know that you’d like some way to continue reading Twitter in Feedly.
Hello, hopefully someone can tell me what I’m doing wrong here. I’m trying to use application-only authentication to retrieve the top 60 posts of a user (GET statuses/user_timeline) and I cannot get a response. I keep getting a 400: Bad Request. I followed the guide very closely, but to no avail. My code is C#:
string encodedConsumerKey = HttpUtility.UrlEncode(consumerKey);
string encodedConsumerSecret = HttpUtility.UrlEncode(consumerSecret);
string encodedConcat = String.Format(“{0}:{1}”, encodedConsumerKey, encodedConsumerSecret);
HttpWebRequest request = (HttpWebRequest) WebRequest.Create(requestCall);
request.ContentType = "application/x-www-form-urlencoded;charset=UTF-8";
//request.Credentials = new NetworkCredential(consumerKey, consumerSecret);
string credentials = Convert.ToBase64String(Encoding.UTF8.GetBytes(encodedConcat));
request.Headers[HttpRequestHeader.Authorization] = "Basic " + credentials;
UTF8Encoding utf8 = new UTF8Encoding();
string bodyOfRequest = "grant_type=client_credentials";
byte[] data = utf8.GetBytes(bodyOfRequest);
request.Method = "POST";
request.ContentLength = data.Length;
Stream newStream = request.GetRequestStream();
newStream.Write(data, 0, data.Length);
//ServicePointManager.ServerCertificateValidationCallback = new System.Net.Security.RemoteCertificateValidationCallback(AcceptAllCertifications);
HttpWebResponse response = (HttpWebResponse)request.GetResponse();
The requestCall is “https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=classactionabd&count=60”. The consumer key and secret are valid and have been stored in the application’s config file for many years.
Hi guys, I have trouble with my twitter’s search, hash tag and “follow” button,
I’m using iPhone 4s with iOS 6.1.3 and the twitter version is v3.5,
I know I’m using old version app but I’m happy with it and I don’t want to update it…thanks…
Hey guys,
I hope some one can give me some advice, i built this twitter feed a little while ago, followed from a tutorial, only problem it was uilt using API v1, I have no idea what to do to make it work with API v1.1, simply changing
twitterUrl = 'http://api.twitter.com/1/statuses/user_timeline.json</code
to
twitterUrl = 'http://api.twitter.com/1.1/statuses/user_timeline.json
does not fix it, any help would be great.
Thanks
Matt
try {
var o = { username: 'TwitterUserName', count: 4 };
var twitterUrl = 'http://api.twitter.com/1/statuses/user_timeline.json?screen_name='+o.username+'&count='+o.count;
$.ajax({url: twitterUrl, dataType: 'jsonp'})
.success(function(data) {
$.each(data, function(index, item){
var itemRenderer = sym.createChildSymbol("itemRenderer", "tweetContainer");
itemRenderer.$('tweet').html( item.text );
itemRenderer.$('image').css( "background-image", "url("+item.user.profile_image_url+")" );
itemRenderer.play( index * -100 );
});
});
}
catch(error) {
alert("Error: "+error.toString());
</code?
I built it for use in Adobe Edge Animate as the feed is supposed to show the specials on a chalk board! Is there anyway I can make this happen as it was prior to Tuesday!
If you look at http://www.diegoscafe.co.uk/ you can see the chalkboard where the feed was on the ‘specials menu’
Thanks. If you or anyone else here has any further suggestions on following Twitter feeds in RSS form, please do let me know.
is there anyway in which I can make this work?
Correct, OAuth is now a required part of the API mechanism. But, if you’re just running something for yourself you can generated OAuth access token for the app—you don’t need to actually go through the OAuth dance—and store them in your code, or you could use App-only Auth if you’re not acting on behalf of a user.
(For OAuth, see https://dev.twitter.com/apps for your registered app, and then at the bottom of the app profile page is ‘Generated my My Access Token’.)
I’m looking for some help with my twitterfeed. On my site people are posting lost and found items and these used to be tweeted straight away. Now as the v1 is retired since 11-06, this feed does not work anymore. My developer can not be reached…so I’m in the blind what to do…and loosing followers as we speak as I have “no feed” for them…;-(
Can you help me out ? and what kind of info do you require from me to be able to help me out ?
How do i fix my twitter widget, it gives a bad request. Can anyone send me the good one??
´´GET https://api.twitter.com/1.1/search/tweets.json?q=from:SporenNetNL&callback=TweetTick&rpp=50 400 (Bad Request) ´´
I have made an example in PHP of how to use the API 1.1, notably the project examples that where distributed for v1. haven’t been updated for v1.1, notably also the PHP Libraries looks like they are abandoned.
To Download the Package of PHP files for the Twitter v1.1 API Example and link to it on your pages please twitter these links are permanent:
Download: Elastic Open Objects Portal System / Code / Commit [r36]
Code: https://sourceforge.net/p/eoops/code/HEAD/tree/Example%20Script/Twitter%20oAuth%20Example/
Wiki: Elastic Open Objects Portal System / Wiki / Twitter oAuth Example
lsces
#139
Sorry - but I have JUST hit this problem with a number of customer sites and I think that who ever though up this idea needs taking out and shooting !!!
Since many of my customers are not very computer literate, the ONLY way to get their twitter feeds back up is to ask them for their password to their twitter account so I can go in and create the necessary ID to get their website feeds working again. Did NOBODY think that requiring that was going to be a result of this change ???
Hello,
like many other web designers I have this problem:
Appeared on my page my last 2 tweets using the following code:
“https://api.twitter.com/1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2” using the style of my page and not that horrible theme twitter;
But if I update the link:
https://api.twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "
https://twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "
http://api.twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "
http://twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "
I get this error:
error: {“errors”: [{“message”: “Bad date Authentication”, “code”: 215}]}
Looking around I have not found a solution to get my last 2 tweets on my site, I do not think too much to ask?
It was not at all nice and cute by Twitter API 1 block and insert the 1.1 API without even a detailed guide on how to get back to work with the API, millions of web designers have the same problem …