Twitter - "Enable Callback Locking" not available

cwalls
Offline

Active Subscriptions:

None

5 years 9 months ago #64278 by cwalls

Twitter - "Enable Callback Locking" not available was created by cwalls

I am experiencing the same problem as described at www.sourcecoast.com/forums/jfbconnect/jf...request-token#p50990.

I have followed all of the steps on setting up the Twitter app, and have double-checked the API keys.

The one step I could not implement was disabling "Enable Callback Locking". I did not see an “Enable Callback Locking” option in the App Settings tab on Twitter:

From the set-up instructions:
1. Please ensure that the "Enable Callback Locking" setting is disabled in the "Settings" tab. When enabled you may receive errors when trying to authenticate with Twitter.

Could this be causing the problem?

The topic has been locked.

alzander
Offline

Support Specialist

5 years 9 months ago #64280 by alzander

Replied by alzander on topic Twitter - "Enable Callback Locking" not available

Sorry for the confusion. The documentation was out of date with the changes you linked to in the other forum post. The option to Disable callback locking is no longer available. It's always enabled. We've removed that step from the guide.

If you're getting a 'bad token' message when you try to login with Twitter, that's usually caused by your Callback URLs being incorrect. Please make sure you've:
* Set all variations of your domain that can be reached. That means both http:// and https:// and with or without www (or other subdomains)
* Each of those variations ends in /index.php
* If there's a path to your site, like "example.com/joomla", that should be included like example.com/joomla/index.php

I hope that helps, but if not, let us know as there are a few other possible causes, but those are less common.

Thanks,
Alex

The topic has been locked.

ritchie93
Offline

Active Subscriptions:

None

5 years 9 months ago #64311 by ritchie93

Replied by ritchie93 on topic Twitter - "Enable Callback Locking" not available

im having the same issue.

When you say every variation of your site and you give this example:
* If there's a path to your site, like "example.com/joomla", that should be included like example.com/joomla/index.php
do you mean every single page on my websites menu? or do you mean every variation of the home domain url?

Ive been trying to fix this issue for 3 days on and off and really need this to work.

Im on the latest joomla if that helps

The topic has been locked.

alzander
Offline

Support Specialist

5 years 9 months ago #64315 by alzander

Replied by alzander on topic Twitter - "Enable Callback Locking" not available

ritchie93,
No, not every variation of the pages on your website.. just the 'root' of your website. That's usually just your domain name. So, if you're site is ours (sourcecoast.com), you may need all of the following:

http://sourcecoast.com/index.php
https://sourcecoast.com/index.php
http://www.sourcecoast.com/index.php
https://www.sourcecoast.com/index.php

That covers *all* pages on our site.

If you have your Joomla installation in a subdirectory of your domain, you should use that as the root. So, for example.com/joomla you'd use:

http://example.com/joomla/index.php
https://example.com/joomla/index.php
http://www.example.com/joomla/index.php
httpw://www.example.com/joomla/index.php

Finally, if you redirect all requests to www (or non-www), then you don't have to put both variations in. Just choose the one your site actually uses. Same for http vs https (though you should always have https as an option)

I hope that helps explain,
Alex

The topic has been locked.

Start
Prev
1
Next
End

SourceCoast Login

Twitter - "Enable Callback Locking" not available