Closed davidwolfpaw closed 5 years ago
I'm looking at this now, and I tried connecting using an old application configuration. I got the same error:
When I checked the error log, I see a message about "Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings", so I went to the app configuration details on Twitter (https://developer.twitter.com/en/apps) and noticed that my callback URL was https, while my current dev URL was http. I added the http version (and had to update some other details) -- note that I had to use the full sample URL that the Twitter configuration screen in Keyring gives you (ending in /wp-admin/tools.php
). After doing that, I was able to connect as normal, using the current version of Keyring + Importers.
I updated my Twitter account recently and yesterday went to clean up connections. I deleted the Twitter connection, which was still pulling tweets in, but listed with the old account. When I tried the test feature on the service connections page, it returned the error "This connection is NOT working correctly."
I tried to reconnect with the current app, and with a new app that I created. Each time that I've tried I've received the error "There was a problem connecting to Twitter to create an authorized connection. Please try again in a moment."
I understand that Twitter is making yet more API changes. I'm not sure if this is related. My other connections still work, and I was able to reauthenticate where needed. Some custom connections that I wrote are also still working; Twitter is the only connection that I had active that is no longer working.