Twitter access not working
By Michael Coldwell on Saturday, 03 December 2016
Posted in General
Replies 8
Likes 0
Views 113
Votes 0
I've followed the documentation provided for EasyBlog. When I setup the Auto Posting for Twitter however, when I click the "Sign in to Twitter" button, I receive the following error message:
"Whoa there!
The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake."

I've generated a new key and secret at least 3 times and still get the same error message.
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

Can you try re-create a new Twitter app and see how it goes?

If still can't, can you update your Twitter access at your first post > click edit button > put your Twitter access into optional fields so we can better have a check?
Arlex Wong
·
Saturday, 03 December 2016 11:50
·
0 Likes
·
0 Votes
·
0 Comments
·
We have same issue - deleted app and recreated to get new credentials. Cleared all cache - restarted server etc etc.

Second set of keys fails as well. We get the exact same error message. Have turned off login via twitter for now.

Please post whatever fix ends up working?

thank you guys!

Bridgette
bridgette Patrov
·
Sunday, 04 December 2016 06:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Bridgette,

This post is actually for EasyBlog and not EasySocial Anyway can you take a screen shot of your app settings on Twitter and start a new thread please?
Mark
·
Sunday, 04 December 2016 14:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry about that - I did a search for the error message and skimmed his post. My mistake. Will post new thread.
bridgette Patrov
·
Sunday, 04 December 2016 22:23
·
0 Likes
·
0 Votes
·
0 Comments
·
No problem Bridgette
Mark
·
Sunday, 04 December 2016 23:06
·
0 Likes
·
0 Votes
·
0 Comments
·
I just got back in town, I apologize, should have clarified, I took the weekend off as well. I will work on this tomorrow and provide an update letting you know if deleting and re-creating the app fixes the issue. Thank you for the quick response though!
Michael Coldwell
·
Monday, 05 December 2016 15:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Alright, keep us update then Michael
Arlex Wong
·
Monday, 05 December 2016 18:57
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post