“Sync” can mean several different things. PI WP Suite separates them so an administrator knows what is refreshed, when it happens, and where the result is stored.
The four important flows are:
- Account metadata discovery
- Login-time WordPress user synchronization
- Cached live listings
- Background directory indexing
1. Refresh Groups and Account Metadata
Open Member Data & Roles → Member Access & Roles and click Refresh this account’s metadata.
This refreshes the available groups, member types, statuses, and attributes for the configured MC Professional organization. It updates the lists used by role mapping and field selection.
Run it when:
- A group is created or renamed.
- A new member type is introduced.
- A status changes.
- Profile attributes are added.
- The API connection is changed to another organization.
Metadata refresh does not rewrite every WordPress user. It refreshes the administrator’s available configuration choices.
2. Synchronize a Member at Login
When a member signs in, PI WP Suite can:
- Create a WordPress user when no matching user exists.
- Update supported WordPress user fields.
- Store the MemberClicks Profile ID.
- Store supported name, email, group, type, status, creation, and expiration values.
- Assign a fixed or mapped WordPress role.
- Enforce configured status and redirect rules.
This keeps the current member’s WordPress account aligned with the profile returned during authentication.
It is different from directory synchronization because it updates the signed-in WordPress user, not the entire searchable profile index.
3. Cache Events, Groups, and Live Profiles
Live API output is cached with WordPress transients. Safe defaults reduce repeated calls and improve page speed.
Business provides configurable caching presets. Developer provides more granular durations, resource-specific controls, shortcode overrides, and manual clearing.
Resources can include:
- Events
- Groups
- Directory results
- Profile details
- Search sessions
- Education records
- Organizations
Choose a cache duration based on how often the source changes.
A practical policy:
- Groups: one to six hours
- Events: one hour
- Profile details: one hour
- Directory results: one to six hours
- Education: one hour unless rapid updates are required
Longer caching reduces API traffic. Shorter caching shows source changes sooner.
4. Synchronize the Directory Index
Synchronized directory mode creates a private WordPress profile index used for faster search and resilient display.
Open Member Directory → Synchronization and configure:
- Hourly, twice-daily, or daily schedule
- Maximum profiles processed
- Initial Synchronize Now run
The “Last sync” line records the most recent run and the number of indexed profiles.
For organizations over 1,000 profiles, the API may require multiple pages and multiple cron passes.
Incremental Sync and Retry Queues
Developer adds operational controls for larger directories:
- Saved API cursor or page
- Incremental continuation
- Exponential retry queue
- Created, updated, and failed counts
- Synchronization health report
If an API page fails, the job does not have to discard all completed work. It can record the failure, retry it, and continue from saved progress.
What WordPress Cron Means
Scheduled jobs depend on WordPress cron being triggered. Low-traffic websites may run scheduled work later than expected.
For a large or time-sensitive directory, configure a real server cron to call WordPress cron at a reliable interval. Ask the hosting provider to confirm that loopback requests and scheduled events work.
Troubleshooting a Missing Group
If a new group does not appear:
- Confirm it exists in the connected MC Professional organization.
- Run Test API.
- Run Profile Attribute Check.
- Refresh account metadata.
- Clear the groups cache if your license exposes that control.
- Confirm the member profile actually contains the group.
- Sign in again to refresh that member’s WordPress role.
If the group listing is correct but the user role is not, review the Visual Role Mapping table and the role source under Member Sync & Access.
Troubleshooting a Stale Directory
For live mode:
- Clear the directory and profile caches.
- Confirm API availability.
- Confirm attribute visibility.
For synchronized mode:
- Check the last synchronization time.
- Run Synchronize Now.
- Review the Developer health report.
- Check WordPress cron.
- Review the retry queue.
Recommended Screenshots
- Refresh account metadata
- Member Login & Sync
- Caching controls
- Directory sync health
Alt text: “Refresh MemberClicks groups, member types, statuses, and attributes in WordPress.”
Alt text: “Configure WordPress account creation, profile synchronization, and role assignment.”
Alt text: “Choose MemberClicks API cache durations for groups, events, profiles, and directories.”
Alt text: “Monitor incremental MemberClicks directory synchronization and retry status.”
The key is knowing which refresh operation solves which problem. Metadata controls the available choices, login sync updates a member’s WordPress account, caching controls API freshness, and directory synchronization maintains the searchable local index.
