Response Time
24 — 48 hours
A number of people on this forum have had this exact problem. In each case, t has been fixed by staff going into their systems. I hope hat enough has been learned as to the causes so that I can fix it with advice.
I have the latest Joomla 3.4 and latest EasyBlog.
When trying to set up autopost to twitter I get the following message when I try to authorize via the Twitter acct:
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.
1. Twitter autoposting was working fro me back in 2012/13 but then I turned it off.
2. Re-enabled it with latest version of Easyblog, regenerated and re-entered the keys. When clicking the authorise I get the above messae every time.
3. Tried setting up a whole new app. Same result.
4. Many times regenerated keys. Same result.
5. Looked at easyblog_oauth. The entry for twitter has null for each of consumer key and secret. This record is updated when I click save in easyblog. Always null but I do not know f he info is supposed to be null untl the authorise happens ....or not. I am sure someone can tell me.
6. Tried deleting the record (I an=m nw up to about record 11 or 12). No difference. No improvement.
Would appreciate some help.
Thanks,
David
I have the latest Joomla 3.4 and latest EasyBlog.
When trying to set up autopost to twitter I get the following message when I try to authorize via the Twitter acct:
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.
1. Twitter autoposting was working fro me back in 2012/13 but then I turned it off.
2. Re-enabled it with latest version of Easyblog, regenerated and re-entered the keys. When clicking the authorise I get the above messae every time.
3. Tried setting up a whole new app. Same result.
4. Many times regenerated keys. Same result.
5. Looked at easyblog_oauth. The entry for twitter has null for each of consumer key and secret. This record is updated when I click save in easyblog. Always null but I do not know f he info is supposed to be null untl the authorise happens ....or not. I am sure someone can tell me.
6. Tried deleting the record (I an=m nw up to about record 11 or 12). No difference. No improvement.
Would appreciate some help.
Thanks,
David
10 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
