search

christianwach / civicrm-wp-member-sync

CiviCRM WordPress Member Sync plugin keeps a WordPress user in sync with a CiviCRM membership by granting either a role or capabilities to a WordPress user who has that membership.
https://wordpress.org/plugins/civicrm-wp-member-sync/
GNU General Public License v2.0
17 stars 10 forks source link

Member sync between separate Wordpress installations #42

Closed jessefrissekom closed 2 years ago

jessefrissekom commented 2 years ago

We are currently working on a site new site for a client that uses CiviCRM data. The CiviCRM installation they currently have is rather large and we would like to keep it in a separate Wordpress installation so it does not impact the speed and stability of the site we are building. For this particular site CiviCRM contacts need to be able to sign in to Wordpress user accounts, thus we came across your plugin. Could you help us establish synchronisation between the CiviCRM contacts in one Wordpress installation and the Wordpress users on a Wordpress website?

christianwach commented 2 years ago

@jessefrissekom So, to confirm, your set up is something like this?

This plugin will only sync CiviCRM Memberships to WordPress Users on the WordPress install that it is activated on. So, in this case to https://members.example.com.

Are you saying you want it to sync to https://example.com as well?

jessefrissekom commented 2 years ago

@christianwach Thank you for responding so quickly. The setup is exactly as you described it. Yes, we would very much like to have all the CiviCRM contacts from the member site synced as users on the main site.

Main site -> Used as front-end for visitors and used by members to sign up for events etc. Membership site -> Used as CRM to manage members of an organisation

Ideally an admin would add a new contact in CiviCRM and overnight the contact gets synced with the main site so the contact can login to Wordpress and sign up for events.

christianwach commented 2 years ago

@jessefrissekom Okay, I see. Personally, I'd advise against this sort of architecture. I see little benefit in it and many problems. Why not simply host the events on the members site if that's where sign-ups occur? And if they need to be on the main public site, why not hang CiviCRM off that? What speed and stability issues have you encountered?