Topic-icon Twitter channel reports no posts after Twitter migrated me to API v2

The subject kinda says it ;)

Twitter has deprecated v1.1 and my app is now basic permissions on v2. When this happened, my channel for dispaying posts in the social stream module stopped working and the config now says: No Stream Data found.
  • Channel may be configured incorrectly. Please make sure your channel is published and review settings for any possible errors.
  • There may be no current posts available from the social network.
I deleted and recreated the channel and logged in with the associated user just to see if that would do it, but no joy.
 
The topic has been locked.
Support Specialist
1 year 4 weeks ago - 1 year 4 weeks ago #68528 by mel
First and foremost, can you:
1. Go into your JFBConnect backend > Configuration > Advanced area and set Cache Duration to 0. Then refresh and see if that has an effect.
2. Verify that you've switched your client ID and secret to the new application.

[Edited to add] Make sure to re-authenticate on the front-end of the website. Your user will not be mapped since it's a new application. Please make sure to enable "Automatically Link Users by Email" so the Twitter account will be mapped to your existing account. Are there any error messages on logging in with the new app?

If the cache setting does not help, in your user authentication settings for the app on developer.twitter.com, can you tell me what your
* App permissions are set to (Read/Write), and if you have Request Emails from users checked (should be yes)
* Type of app - should be Web App
* Redirect URLs and Website URL

-Melissa
Last edit: 1 year 4 weeks ago by mel.
The topic has been locked.
1 year 4 weeks ago - 1 year 4 weeks ago #68529 by chramb1
I set the cache from 15 to 0 and refreshed everything. No change.

App permissions are read/write. See attached screen grab.

The user is mapped. As you can see in the second screen shot, it shows up as an option for the channel (if it weren't mapped, it would be there).

The API key/secret have been verified to be correct.

Third screen shot shows the other items you asked for.

Redirects:
Attachments:
Last edit: 1 year 4 weeks ago by chramb1.
The topic has been locked.
User mapping... screen grab attached.
Attachments:
The topic has been locked.
1 year 4 weeks ago - 1 year 4 weeks ago #68531 by chramb1
One other thing - when I re-authenticate, it works, and upon redirection back, I get this error:

0 Class "JFBConnectUtilites" not found

I wonder if there is a step being missed because of the error? Something's not getting written because the callback halts the flow?

This (typo?) appears only once, in plugins/jfbconnect/provider_twitter/provider/twitter.php in the getUserScope() function.

Fixing the typo and re-trying login, I now get: 0 Call to a member function getStatusCode() on bool
Last edit: 1 year 4 weeks ago by chramb1.
The topic has been locked.
Support Specialist
Yes that was a typo for JFBConnectUtilites not found. I've checked in the correct spelling for the next release.

In plugins/jfbconnect/provider_twitter/provider/twitter.php on line 65 and line 85, replacing
if (JFBConnectUtilities::getResponseCode($creds) == 200)
with
if (is_object($creds) && JFBConnectUtilities::getResponseCode($creds) == 200)

-Melissa
The topic has been locked.
Okay, but even after I fixed it, the problems persist.
The topic has been locked.
Support Specialist
I was able to authenticate on your site with Twitter without seeing any errors on the front-end. Hopefully those changes at least fixed the errors on auth for call to member function not found.

Can you use our Contact Us form to provide the following? a) your twitter username so I can look at your public posts b) backend access so I look can see how things are configured/plugins/etc and c) FTP access to your site - this will be the quickest way to debug since I'm not able to reproduce this on my J4 test site with twitter api 2 app.
The topic has been locked.