Problem with Twitter autoposting
By David William Kerr on Monday, 16 November 2015
Posted in Technical Issues
Likes 0
Views 668
Votes 0
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
FOUND AND FIXED!

I use ACESEF on my website. I disabled it and then I was able to authorise the App!!!!!

I have now re-enabled it and hope that autoposting will work.

Dave
David William Kerr
·
Monday, 16 November 2015 20:13
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi David,

Can you provide us with the following credentials so we can have a closer look on your issue here?
1) Joomla backend access
2) FTP access
3) Twitter access
Ezrul Fazwan
·
Monday, 16 November 2015 18:22
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,
I am rather reluctant to hand over such in-depth access. Surely there are some suggestions I can follow? I am an experienced computer guy.
Regads,
Dave
David William Kerr
·
Monday, 16 November 2015 18:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi David,

Have you tried to regenerate access token inside your twitter apps? You can further refer to our documentation here regarding on twitter autoposting setup, http://stackideas.com/docs/easyblog/administrators/autoposting/setting-up-twitter-autoposting .
Ezrul Fazwan
·
Monday, 16 November 2015 19:03
·
0 Likes
·
0 Votes
·
0 Comments
·
See item 4. in first post= yes, have not only regenerated several times I also generated a whole new application and regenerated the token and pw inside that several times.

I also followed the link you referenced exactly.

Please note that the easyblog_oath record contains the following. Tis record is generated each time I click the sign in with twitter button. I assume it is supposed o contain the token and secret key returned from twitter if it is successful? Presumably this record simply means that it failed given the nulls and the lack of a timestamp:
id 11 [naturally increments each save for a new record.
user_id 62 (which is correct)
type twitter
auto 0
request token is {"token":null,"secret":null}
access_token null
message null
created: 0000-00-00 00:00:00
private 0
parameters null
system 1

Regards,
Dave
David William Kerr
·
Monday, 16 November 2015 19:27
·
0 Likes
·
0 Votes
·
0 Comments
·
By the way, my site is SSL and the url therefore is

https://www.kerr.net.au

I assume easyblog->twitter integration works okay with SSL?

Regds,
Dave
David William Kerr
·
Monday, 16 November 2015 19:29
·
0 Likes
·
0 Votes
·
0 Comments
·
A further comment. The URl when I get the error is:



it seems strange that there is no token and/or secret key sent. How can twitter know what to do in that case? Or is it simply that the whole URL is not being displayed?
Regds,
Dave
David William Kerr
·
Monday, 16 November 2015 20:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Dave,

Thanks for the heads up on this and glad to hear you found the issue that causes the autoposting not working. Do let us know your autoposting to twitter working fine or not.

Thanks.
Sam
·
Tuesday, 17 November 2015 11:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Autoposting worked fine to both Twitter and Facebook.

With ACESEF, I think you are better off configuring easyblog to use the acesef router rather than the component router (which is what I had used). They have actually released a paid extension for Easyblog but a couple of their other paid routers that I have purchased have had massive problems with little (indeed almost zero) interest by the authors in fixing. So, do not recommend purchasing the ace router for ACESEF and easyblog.


Regards,
Dave
David William Kerr
·
Tuesday, 17 November 2015 15:22
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi David,

Thanks for the heads up on this and glad to hear that your issue has been resolved now. Currently our components can only support sh404sef extension and joomsef artio sef extension as sef alternative for easyblog. We will keep this in mind and hopefully will be able to fully integrate with ace sef in the future.
Ezrul Fazwan
·
Tuesday, 17 November 2015 18:39
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post