[MokoJoomSocialLogin] feat: Replace CB integration with MokoJoomCommunity sync #7
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Update
plg_user_mokojoomsocialloginto sync social profile data to MokoJoomCommunity instead of Community Builder. MokoJoomSocialLogin is a required dependency of every MokoJoomCommunity deployment -- no detection checks needed.Current State
The user plugin currently:
isCommunityBuilderInstalled()then syncs to#__comprofiler#__user_profilesfor Joomla-only installsRequired Changes
1. Replace CB sync with MokoJoomCommunity sync
Replace
syncToCommunityBuilder()withsyncToMokoJoomCommunity():#__mokojoomcommunity_profiles.avatar#__mokojoomcommunity_field_values(EAV)2. Remove CB detection
isCommunityBuilderInstalled()method#__comprofilerreferencessyncToMokoJoomCommunity()directly (no conditional)3. Log activity on social login
Call
ActivityHelper::logActivity()after successful social login to log the event to the activity stream.4. Update plugin params
Replace CB field mapping params with MokoJoomCommunity field names:
cb_avatar_field,cb_provider_field,cb_social_username_fieldcommunity_sync_avatar(bool, default 1)community_provider_field(field name, defaultsocial_provider)community_username_field(field name, defaultsocial_username)MokoJoomCommunity Side
No code changes needed. The existing schema supports external writes:
#__mokojoomcommunity_profiles.avatar-- VARCHAR(255) for avatar URL#__mokojoomcommunity_field_values-- EAV table accepts any field/value pairCommunityHelper::getProfile()-- public static, callable from any extensionOptional: Create default custom fields
social_providerandsocial_usernamein the community component install script.Acceptance Criteria
#__mokojoomcommunity_profiles.avatar