Setting up channels

Thanks for the credentials. Unfortunately, the user you created for me doesn't have permissions to configure the channels, so I can't access that area at all. Please either upgrade my user group or change the permissions in JFBConnect to allow my user to be able to configure different areas of JFBConnect.

As for the user token in general, what happens is that when a user authenticates using JFBConnect on your site, Facebook issues a special ~100 character secret code. That code can be used to make requests on the users behalf back to Facebook. We store the 'token' in the database and use it to post to the Channel or read data from the Facebook Page. It has nothing to do with the user's email address or anything like that, it just matters that the user has authenticated.

As noted, we're updating the Channels interface and have found a few odd bugs that are rare, but it's possible you're running into one. If my user has installation permissions on your site, we may try to update some of the files to see if the new version helps fix some of these issues you're having.

Thanks,
Alex

I'm unsure what's happening, but I'm still unable to access the Channels area of JFBConnect. The permissions *do* look correct, so something funky is happening that we haven't seen before. I'm still not of a high enough level to actually install a new release of JFBConnect to test it though, or I'd do that. So, right now, I'm a bit stuck. If you can escalate my group to Super Users, that would likely fix both issues.

As to your other questions:

Could it be that the API key stored in database still reflects the previous key to the previous App that I deleted and recreated? I copied the new API key and new Secret code to the Facebook configuration page and saved the new configuration. I did that twice just to make sure that the correct keys were entered in the DB.

It wouldn't be the old API / Secret key from Facebook that would be causing the problems. However, Facebook uses a unique user ID for each user based on the API key. So, if you configured the Channel for user 'A' and then changed the API key, Facebook won't recognize user 'A' anymore as their new ID would be 'B'.

I did change the Social Media channels manager a couple of times. Perhaps that set a token in the database that is no longer valid because the Channel Manager is no longer the same. Is there a way to reset that 100 character secret code so that JFBConnect updates that token to the new one returned by a Facebook request.

We did just find a bug where JFBConnect could store the token in the database and not update it properly. It's a weird scenario, but it could frankly be what you're running into. This will be fixed in the next release, which is one of the reasons I'd like to be able to install that release on your site.

With the above 2 points combined, here's what I'd recommend doing on your end:
1) Delete the Channel you've created in JFBConnect. This will delete the wrong token stored with that channel (if you're experiencing that bug).
2) Have the Facebook user that owns the Facebook Page authenticate on the front-end. This will get the proper User ID from Facebook for that user for your current App ID. Make sure that a new account wasn't created.. or, if it was, make sure you use this account in step #3.
2) Re-create the Channel from scratch and select the same user from 2.

Hopefully, that will clear any pipes that may have gotten clogged along the way. Of course, if not, let us know and we can update to the upcoming release which should improve things as well.

Thanks,
Alex

We're working on it. I installed the new beta release that's going through testing, but still running into issues.

At this point, yes, if you can Private Message FTP credentials, that may help us just add some additional debug code to try and narrow down what could be happening.

Thanks,
Alex

Alright.. made some progress tonight. Having FTP access helps greatly.

The problem with the user that you are trying to use to own the channel is that his access token was set to the Application ID and not the user's unique token. That's not normal and shouldn't happen, and I'm not sure why it was configured like that.

I used a SQL query and deleted the token that was setup for that user. Can you re-authenticate using Facebook as that user? That will hopefully fix the Channel, but if it doesn't, it will at least let us check what token is set.

For the other 5 or so users that have authenticated using Facebook (including myself), the access token looks correct. So, something is setting the wrong token for that user.. hopefully clearing it will let it be set correctly when you re-authenticate.

Thanks for your patience,
Alex