Topic-icon I HAVE BEEN PAYING FOR YEARS - STILL HAS NOT WORKED CORRECTLY

Active Subscriptions:

None
6 months 2 days ago - 6 months 2 days ago #69266 by chrpar
PLEASE SEE THESE NOTES FROM YEARS AGO - [Edited to remove private credentials from public forum]

At the time I was casually working on things as I had a psonal suregy and was trying to do some productive things,  this component NEVER worked propoerly and for all cases I just turned it off because support was un responsive for months at a time sometime not repsonding at all.

Currently I need ( really need ) assistance beceuse I am not able to go back to work and this interest project needs to translate into real income ASAP.

I have ben screwing around with so many things that I figured the best  course of action would to be to try support again.

I am cioncerened that its the notes in the autotune that suggeests that the other comoponents that have Socail connect or Temaplte is the issue,  please find access doc here to look at the enviornemtn and help me solve the issues, this is not an option for me anymore its a must , I beg you to assist. 

[Edited to remove private credentials from public forum]
Last edit: 6 months 2 days ago by mel.
The topic has been locked.
Support Specialist
Chris,
Thanks for reaching out again. We opened your document, but it's over 8 pages long and describes a lot of how your website works and a ton of details we don't fully understand.

Can you tell us specifically what issues you are having with JFBConnect? We can gladly investigate specific issues, but our goal isn't to understand every aspect of how your site works.. just what help you need.

Regarding "autotune that suggeests that the other comoponents that have Socail connect or Temaplte is the issue", I just ran Autotune on your site (comm...ce.ca) and all tests passed. There was not any messages about conflicts. Are you still seeing a warning and, if so, on what site and what is the specific warning?

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
Yes the Doc was in depth and of great interest but was not executed ever because of failed responses of support - it was a difficult time for everyone during the lock downs and I understand that all tech people where under pressure, Lets start with the connectivity of the social networks to start, and we can go step by step, I have not reviewed the doc in detail I sent it as reference.

These Social Connections have not worked ever and this needs to be resolved first so we can proceed with the auto sharing via channels especially.

This is a description that AI gave me, I am using AI to help with my conative disability, I am sorry for the length but I think its better than ongoing back an fourth - start out with all the info.

top-tier email to send directly to Alex at SourceCoast (JFBConnect), covering:

✔ The issue
✔ Your multi-site + MightySites architecture
✔ The requirement for unique login modules per slave site
✔ Automatic assignment to JomSocial groups
✔ Social login channels
✔ Auto-posting requirements
✔ Additional questions and support items he should address

You can copy/paste and send as-is.


EMAIL TO ALEX – JFBCONNECT / SOURCECOAST

Subject: Request for Technical Support – JFBConnect Social Login + MightySites Multi-Site Integration

Hi Alex,

I hope you’re doing well. I’m reaching out for support on a multi-domain setup using JFBConnect, MightySites, and JomSocial. We are trying to finalize correct login behavior across all slave sites, and I want to outline the issue and requirements clearly so we can resolve this with your guidance.

---

CURRENT SETUP

Master Site:
CommunityMarketplace.ca

Slave Sites (examples):
– MyCommunityTV.org
– givebackmom.com
– Allseasonsolutions.com
-CommunitySportsMatters.com
- LevelUpforLocal.com
– Many additional domains using MightySites (shared user table)

All sites share the same Joomla database user table, but each slave site represents a specific local community with its own JomSocial group, J-BusinessDirectory category, and unique branding.

We are using JFBConnect for all social logins.

We already created a custom plugin to detect the domain and assign the user to the correct JomSocial group based on the site they register from — but this plugin isn’t firing consistently because the JFBConnect login module isn’t loading properly on some slave sites.


---

THE ISSUE

On multiple slave sites, the JFBConnect login module or provider callback fails or does not redirect properly:

Example callbacks:
localcommunityhero.com/index.php?option=...ck&provider=facebook
legionbranch43.ca/index.php?option=com_j...ck&provider=facebook

The component appears to be installed globally, but the callback and provider configs don’t open properly on many slave domains under MightySites.

Additionally, Facebook/Google refuse validation unless all domains are configured properly — and we want to confirm the best way to configure multi-domain callback URLs under JFBConnect.


---

WHAT WE NEED JFBCONNECT TO DO

1. Per-Domain Login Modules

Each slave domain requires its own dedicated login module instance so the user logs in from that site's URL and is then:

✔ Redirected back to the correct domain
✔ Assigned to the local JomSocial group
✔ Tracked correctly by JFBConnect

We want to confirm with you the proper JFBConnect configuration under MightySites to support:

– Multi-domain return URLs
– Multi-domain callback URLs
– Auto-detection of domain in the provider callback
– Correct module placement on each slave site


---

2. Auto-Assign JomSocial Group by Domain

This already exists via our plugin, but we want confirmation on:

– Which JFBConnect triggers we should hook into
– Whether JFBConnect provides a clean event to detect provider callback completion
– Best practice for mapping domain → JomSocial group ID
– Support for both social login & username/password login

This is essential for our environment.


---

3. Social Login Channel Requirements

We intend to enable:

✔ Facebook
✔ Google
✔ LinkedIn
✔ Twitter / X
✔ Instagram (if possible)
✔ TikTok (if supported through custom provider config)

We need clarity on:

– The correct master callback domain
– Whether separate app credentials are needed per domain
– Recommended architecture for MightySites multi-domain social login
– Any changes required in provider configs for Facebook’s recent policy updates



4. Social Auto-Posting

We also want to utilize JFBConnect's social auto-posting capabilities for:

– JomSocial activities
– J-BusinessDirectory events, companies, offers
– Community articles (com_content)

We need clarification on:

– Whether auto-posting can be domain-specific under MightySites
– If each domain requires its own social app credentials
– Whether JFBConnect can auto-post based on category or group ID
– Best practices for multi-brand social auto-posting


5. What We Need From You / SourceCoast

To resolve this correctly, we need:

1. Confirmation of the correct JFBConnect configuration for a MightySites multi-domain shared-users environment

2. Instructions for proper callback URL structure for social login providers

3. Guidance on whether each domain must have its own Facebook/Google app, or if we should use one app with multiple domains in the settings

4. Recommended JFBConnect event triggers to tie into our plugin that assigns JomSocial groups after login

5. Steps to ensure the JFBConnect login module loads properly on slave domains

6. Any patches or known issues with MightySites + JFBConnect

7. Your recommended “full feature utilization checklist” so we can implement everything from SourceCoast correctly




---

OPTIONAL (IF AVAILABLE)

If SourceCoast has:
– A multi-site guide
– Recommended module configuration
– Example plugin for post-login user group or community assignment
– Known best practices for callback URLs

…we would appreciate those resources.



Once working, this will be the login engine used across domains under


---

Thank you, Alex
The topic has been locked.
Support Specialist
6 months 2 days ago - 6 months 2 days ago #69269 by alzander
We’ve tried to answer most of your questions below. We think that the initial step should be focusing on getting social login working on the one main domain and one social network before moving on to all slave domains and the full list of social networks. The glaring issue is the incorrect callback URIs but a review of each social network application should be done compared with our application setup guides as well. Once we think one social network is logging in correctly, then we can expand to the other networks and then on to the subsequent domains.

2. Instructions for proper callback URL structure for social login providers

The callback is incorrect in your example. Instead of task=provider.callback, it should be task=authenticate.callback and then just change the provider name depending on the social app.

The format:
https://YOUR_SITE.com/index.php?option=com_jfbconnect&task=authenticate.callback&provider=PROVIDER_NAME

Where YOUR_SITE Is like localcommunityhero.com, etc
Where PROVIDER_NAME can be
- facebook (for a Facebook consumer application for user login)
- facebookbusiness (for a Facebook business application for channels and posting)
- linkedin
- twitter
- google

For instance localcommunityhero.com/index.php?option=...ack&provider=twitter

3. Guidance on whether each domain must have its own Facebook/Google app, or if we should use one app with multiple domains in the settings

The social network applications support multiple domains, so you should just need one social application for each social network platform. However, for Facebook, you will need two - one for business posting (to allow JFBConnect to post to your Facebook Page) and one for consumer login.

- For each of the applications, you can then set multiple redirect URIs. In other words, one for each of the slave domains. So you’d list one for legionbranch43.ca, localcommunityhero.com, etc. We do this often with our social network applications to test multiple websites with different versions of Joomla. 
- For Facebook there is an additional step of adding domains in the App Settings > Basic area. 

In general, for each of the social networks that you want to use, there are many steps to configure it. We have a guide for each at www.sourcecoast.com/jfbconnect/docs/social-network-applications that you will need to review. There are several other settings in each besides the callback URL that will need to be configured.

4. Recommended JFBConnect event triggers to tie into our plugin that assigns JomSocial groups after login

When JFBConnect logs a user in with social credentials, the standard Joomla events will be fired (onUserLogin). Assuming that you’ve created a user plugin, in your plugin, we’d advise you to listen for the correct event (such as onUserLogin or onUserAfterLogin) and order your plugin in the Plugin Manager after the ‘User - Joomla!’ and ‘User - JFBConnect Social Integration’ plugins.

5. Steps to ensure the JFBConnect login module loads properly on slave domains

Let’s get it working properly on a main site first and then we can work through any issues on other domains.

6. Any patches or known issues with MightySites + JFBConnect

Not aware of any issues.

– Any changes required in provider configs for Facebook’s recent policy updates

In general, the social network applications change quite a bit. We’d recommend periodically reviewing our application setup guides to double-check the apps have been set up correctly.

We also want to utilize JFBConnect's social auto-posting capabilities for:
– JomSocial activities
– J-BusinessDirectory events, companies, offers
– Community articles (com_content)
We need clarification on:
– Whether auto-posting can be domain-specific under MightySites


The autoposting should support com_content and JomSocial (events and groups) when our corresponding Open Graph - Content or JomSocial plugins are enabled. We don’t currently have J-Business Directory open graph plugin.We will have to give some thought and discuss on how to best accomplish auto-posting for each domains.

We intend to enable:
Facebook, Google, LinkedIn, Twitter / X, Instagram (if possible), TikTok (if supported through custom provider config)


We do not support TikTok. Instagram had been integrated into Facebook Login, but we need to review that we have the correct implementation for this still.
Attachments:
Last edit: 6 months 2 days ago by alzander.
The topic has been locked.