Can you post (or private message) us a specific URL you're testing with so we can investigate further?
Please go into the JFBConnect -> Channels area, edit any Facebook channels you have and click "Save". That should update the permissions request properly so that the owner of the channel is requested the correct permissions the next time they attempt to login.
You're correct, we could make it more clear that you need to save the channel first before you re-authenticate. The message for "this token has expired" isn't very accurate either. I'm unsure where that text came from, but we'll look into getting it updated.
Thanks for your feedback,
There isn't a generic 'step-by-step' instruction we can provide for each permission on how it would be visible on your site. Every site is different.
The publish_pages, manage_pages and user_posts permissions all relate to pulling in or posting to a wall feed from Facebook. If you're showing the SCSocialStream module on your site, show where you are showing that feed.
The user_friends permission is not something JFBConnect should be requesting. Can you tell us where the Scope Review section is showing that permission being requested?
I hope that helps answer your question, but if you need anything else, please let us know.
Please re-authenticate one more time on the front-end of your site after you setup the Channel. We don't request all permissions from every user by default, that would prevent users from authenticating. We only request the needed permissions for each user. So, after you setup the Channel, JFBConnect knows to request the additional permissions required to get and post to your Company feed the next time you login.
Save the channel and authenticate on the front-end and let us know if that helps.
As for the settings in the Usermap area, those are Facebook-specific settings that don't apply to any other network. They probably need to be cleaned up and/or removed in the future, but for now, that seems right.
Sorry for the delay in getting back to this. I'm glad to hear the Facebook posts work after your initial setup issues.
I'm unsure why the text came out wrong. JFBConnect should be respecting the encoding of the page or your post. We have logic in our Open Graph tag generation to properly respect the encoding of the page, which is used when your content is shared/liked. That text should be the same as what's used when an auto-post happens. Since it's not, we'll need to understand what's actually going on.
Can you let us know:
* The URL of a page that posts incorrect? We'll run it through the Facebook URL Debug Tool to check if there's issues there. You can try it as well.
* Just to confirm, the issue is with the auto-generated text for the post, correct? If you are using the "Create Post" button and it's your custom comment that's coming in with the wrong encoding, let us know that.
We haven't heard any recent issues with LinkedIn authentication. I'm unsure why this happened "Then I logged off in the front end and logged back in with Linkedin and nothing happned. ".
If you remove the channel and try to login on the front-end with your LinkedIn credentials, you aren't actually logged into the site? Does the page reload or anything else happen when you try? Are you prompted for your linkedin email, password and shown the permissions prompt? Any details you can provide here would be helpful. We'll need to understand why linkedin login isn't working by itself before trying to get a channel setup.
One thing I would suggest is setting the "Debug Mode" setting in JFBConnect to 'Yes'. That may show extra details when authentication fails. If so, definitely let us know that as well.
1. The Login button or text are hidden within the site's black banner and no one can see it in order to lik.
Your template is overriding many of the styles in the SCLogin template file by using the !important tag. You can see in the image below what I'm talking about. This is an image highlighting the styles for the "Log in" button.
At the top of the styles, the /media/sourcecoast/themes/sclogin/default.cssdefault.css file is setting the font color to white, which would show
Further down though, /templates/theme1621/css/template.css is forcing the font color to black with the !important tag
We can't override that, it's something you'd need to do by modifying your template or altering our SCLogin theme file.
2. When I search and locate the text, the pop-up form pops up only for a few micro seconds and then disappears before anyone has a chance of filling it.
I see it disappearing quickly. Can you please enable the "Include jQuery / Bootstrap" setting in JFBConnect. That will include a namespaced version of those libraries which will only work with JFBConnect. That also should prevent other extensions from conflicting with our popup functionality. If that still doesn't work, leave it enabled and let us know so we can investigate further.
3. (Please note that a button never shows either in the Modal Popup or Always Visible state. Is there a way to include own custom button then?).
I'm unsure what you mean here. What button are you talking about?
For clarification, the category they are talking about isn't for your Facebook Page, it's for your App. Please edit the App category in the Facebook Developer Area where you submit your app for review.
1. Why would our JFBC apps only work in the Games Category?
2. What other categories may be chosen?
3. Having checked Sourcecoast’s own Facebook Tab, it does not seem to be within the Games category.
I think you're mis-reading what they wrote (what you quoted):
"The Games category you selected for your app does not appear to represent its core functionality. Please update your category in App Settings and resubmit for review." (emphasis mine)
It sounds like your app is in the Games category and they are recommending you select a better-fit category for your app type.
4. As the app’s developer, it would be good if you were to make up more detailed exact sample of words submit-able for each scope and not just for a few. This be helpful indeed.
We're working on updated guides and more information for going through the review process. The review process has been around for years, but in the last few months they've tightened it up a lot while making it more difficult to even allow them to test some of the permissions for approval.
If the only reason above is the category, then there may not be anything else wrong with the submission. Generally, what we've seen, is that a reviewer will stop at the first roadblock they run into. Clear that up, submit again, and you may hit another roadblock, but you should at least be further along.
JFBConnect already has AltaUserPoint integration. Unfortunately, Facebook has been removing many abilities to track the user's behavior on your site. You used to be able to award points for sharing or liking content. Those features have been removed by Facebook recently.
Currently, you can award points for a user leaving a Facebook Comment only.
I'm unsure what "AMPZ" is, but I hope the above helps answer your question.
So.. yeah, we cross posted. Melissa's answer is probably better Start there!
Sorry for the confusion, but hopefully hers gets you going. It covers more cases than I thought through.
The limit can be added in the /components/com_jfbconnect/librarires/provider/facebook/channel/page.php file. Around line 32, you'll see:
$accounts = $this->provider->api($uid . '/accounts', $params, true, 'GET');]
Right above that, please try adding:
$params['limit'] = 100;
When done, it should look like:
$params = array();
$params['access_token'] = JFBCFactory::usermap()->getUserAccessToken($jid, 'facebook');
$params['limit'] = 100;
$accounts = $this->provider->api($uid . '/accounts', $params, true, 'GET');
I hope that helps, but if not, let us know!
Can you let us know what you're looking to accomplish? That may help answer more.
Some issues that can crop up are that the jfbc.login.facebook_onlogin() call can redirect the user to authenticate on the site. If that happens, the page will reload and any callbacks will be ignored.
That onlogin call is already a callback that occurs when Facebook changes to the 'logged in' state for the user. We use that to redirect the user to actually log them into the site with their Joomla account.
If you need a separate callback to validate something or do some prechecks for the user before they login to their Joomla account, there are other ways that is likely possible and ways that would work for all social networks, not just Facebook.
JFBConnect and the SCLogin module do use jQuery and Bootstrap. Please set the "Enable JQuery / Bootstrap" setting in JFBConnect and the SCLogin module to 'yes'. When our extensions add those libraries explicitly, we do it in a specially namespaced way so that other extensions shouldn't be able to break our compatibility.
When that setting is 'no', we rely on the defaults included in Joomla, which can be overridden by other extensions as you've seen.
Hopefully, flicking that switch should fix your issues with JFBConnect. Please let us know how it goes.
Does this mean that the username and password are encrypted (https) as they travel to the URL where they are posted?
Correct. The credentials are transmitted securely.
The issues that browsers have nowadays is that even if they are transmitted securely, if you're entering them on a non-secure page, there's additional risk that some malicious file running on the page could still be scraping the data before the "login" button is actually clicked. That's a more minimal risk, but at this point, it's SSL or bust to be seen in a good light in a browsers eyes.
I mentioned it above, but I'd recommend (and we use) Cloudflare. It's a CDN for your website that can add SSL to all your pages automatically. We get no benefits from you looking into them, just an easy solution.
All the best,
I think your message may have been cut off for some reason, but I'll answer the one question you have..
Usually, for any social network, the first time you login with your social credentials you have to give authorization for your website to connect to the user's social network account. After that first login, further authorization prompts won't appear when trying to login again. So, if you're already logged into Instagram on another tab and then hit the Instagram login button on your site, you'll be logged in automatically... no other prompts.
I hope that helps explain, but should you need anything else, just let us know.
I posted a new update there. Since these are related, it's best to track the issue and quick solutions there:
https://www.sourcecoast.com/forums/jfbc … ons#p64434
I hope that helps and sorry for the trouble.
We're investigating the problem. It definitely is related to channels that were created before JFBConnect v8.x that weren't updated properly with the update. To be clear, that's JFBConnect's issue, not something you may have done during wrong during the installation.
We are working on an updated release which will automatically fix these permissions. That may take a few days to implement, validate and test. The safe and quick way to fix this now is:
* Delete any Facebook Channels you have setup
* Go to the JFBConnect -> Usermap area
* Find your Facebook user
* Delete that user - This will only delete the link between your Facebook user and Joomla user. It will not effect your Joomla account
* Re-authenticate on the front-end with Facebook.
** Do this while already logged into Joomla or,
** If your Facebook and Joomla email addresses are the same, the accounts should be automatically linked
* Re-configure your Facebook Channel
The above will clear the permissions that are set on your Facebook user for logging in and should get things back to normal. We apologize for the trouble but hopefully this will get you going now instead of waiting for the update.
SCLogin is a module. It can't force the actual page it's on to be https. In many cases, users will put the SCLogin module on every page of their site, not just one specific page as well.
If you want to make a specific page of your site always load via https, that should be done with an .htaccess rule, an SEO or other routing extension.
As Melissa hinted at above, the Encrypt Login Form setting in the SCLogin module ensures that the form is *submitted* to a secure/https URL. The page it's placed on is out of the module's control.
One final note, it's becoming more en vogue nowaydays to have every page of your site load over https, whether there's a security reason to do so or not. Browsers and search engines are starting to promote pages that use https more and penalize (in some small way) pages that only load over http. If you have the ability to make everything https (and services like Cloudflare make this exceptionally easy), we'd recommend you do so.
I hope that helps explain further,
Your site looks to be a Wordpress site. We make a social networking extension for Joomla. We're not going to be able to help you. I'd recommend posting your question in your theme's support area or worrdpress.
I hope that helps,
We just had another post about this issue earlier today. Please take a look at the response there and let us know if it helps you:
https://www.sourcecoast.com/forums/jfbc … ons#p64421
We've looked into the code a little bit further and do see where the publish_actions permission from an earlier installation may not have been properly removed and replaced with the newer permissions Facebook requires. With that said though, it should be as simple going into the Channel and clicking the 'Save' button. That should update the permissions that are being requested of the owner of the Channel.
James - You're case is odd though. If you deleted the Channel, then your user should not be getting that permission request. Please let us know what the Scope Review area shows. If the publish_action permission isn't in there, it means something funky is going on with the Channel you deleted. We'll have to investigate further to understand though.
Responding this again as a 'bump'. We had an issue with our email provider today that caused some notifications to not go out. Just wanted to make sure you got an email about the update above.
Good news and bad news here...
The good news is that those social buttons are *not* from JFBConnect. They look to be included from an extension called 'fastsocialshare'. We don't have any control over that.
The bad news is that I'm unsure why the JFBConnect social sharing buttons aren't showing. Can you verify that you have the JFBCContent plugin enabled? That's required for the settings in the Social admin area to work.
I hope that helps explain things, but if you need anything else, please let us know.