Conflict Resolution

Suite vs Standalone conflicts

Four products ship in both forms: Exams, Admissions Engine, Index Engine, EasyPost. You can only run one at a time — they share database tables and shortcodes.

Connect enforces this automatically:

• If the Suite module is active and you try to install the standalone, you'll see a red SafeGuard verdict with a "Deactivate Suite module first" button
• If the standalone is active and you try to install the Suite module, same pattern in reverse

To swap (e.g., standalone → Suite):

1. Install the Suite module first (it won't activate yet)
2. Deactivate the standalone in Plugins → Installed Plugins
3. Activate the Suite module from Connect's Suite tab
4. Uninstall the standalone (data is shared, so uninstall after activation — nothing is lost)

SafeGuard preflight blocked an install

If SafeGuard shows a red verdict for a plugin you want to install, expand the verdict card to see why. Typical reasons:

• Conflicts with plugin X — another plugin creates the same tables, hooks, or shortcodes
• Requires PHP X.Y — your server's PHP is too old
• Database table collision — an existing table with the same name would be overwritten
• Malware pattern detected in uploaded zip — very rare; indicates a corrupt or tampered download

Each reason includes a suggested action. Follow it, then click Recheck.

Third-party plugin conflicts

Sometimes a plugin that isn't in our registry conflicts with a Wigmorean product. Symptoms:

• White screen after activating both plugins
• Fatal error in wp-content/debug.log
• Admin menus disappearing

Diagnose by deactivating everything except Wigmorean products, then reactivating one-by-one until the symptom returns. The last one you turned on is the culprit. Report it to us — we'll add a SafeGuard rule so future users get warned.

Theme conflicts

Some themes override core WordPress functions in ways that break plugin rendering. If a Wigmorean admin page looks broken under your theme:

1. Switch to a default theme (Twenty Twenty-Four) temporarily
2. If the admin page renders correctly, the theme is the problem
3. Check the theme's functions.php for unhooking of standard WP actions
4. Consider switching to the Wigmorean Theme, which is designed for compatibility

Staging environment conflicts

If you're testing on staging and something behaves differently from production:

• Confirm both sites have the same PHP, MySQL, and WordPress versions
• Confirm staging has the same plugins at the same versions as production
• Confirm staging's WP_DEBUG isn't on in production (or vice versa)

Wigmorean Cloud staging environments auto-clone production, so these usually match — but after a few days of independent editing, they can drift.

Rolling back a bad update

If a plugin update breaks something:

1. Go to Connect → Product card → "..." menu → Rollback
2. Pick a previous version
3. Connect re-downloads that version and reinstalls

All Wigmorean products keep the last three versions available for rollback.