Fixed Twitter API v2 Client ID vs Consumer key

[i_n_k]

Affected version

2.2.12

It looks like Twitter made a change affecting the API, which seems to be pushing people to v2 which seems to use a Client ID vs a Consumer Key. Are there any upcoming plans to add that as an option in the "Connected Accounts" area in a coming update? It looks like a recent change on their end broke the integration, which now seems to require this other option.

 

[digitalpoint]

Looks like the Twitter connected accounts are broken even here in XenForo.

 

[drastic]

I get this trying to do twitter or google integrations.

There is no valid connected account request available. Please try ag...

It doesn't even finish the word Again LOL

 

[XF Bug Bot]

Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.3.5).

Change log:

Fix X (formerly Twitter) connected account

There may be a delay before changes are rolled out to the XenForo Community.