This guide helps you identify and troubleshoot plugin compatibility problems on a WordPress site hosted on Pressidium.

Plugin conflicts can cause site errors, broken features, performance issues, JavaScript errors, or settings that do not save correctly. They can occur when plugins provide overlapping functionality, conflict with the active theme or hosting environment, or become incompatible after an update.

Use this guide when:

  • Your site shows errors after installing, updating, or activating a plugin.
  • Your site shows a white screen or fatal error.
  • A plugin feature does not work as expected.
  • Site performance drops after a plugin change.
  • JavaScript errors appear in the browser console.
  • Plugin settings do not save.
  • Cache, security, or optimization behavior changes unexpectedly.
  • You suspect a plugin conflicts with another plugin, the theme, or platform-level features.

Prerequisites

Before you start, make sure you have:

  • Access to the Pressidium Dashboard.
  • Access to WordPress admin, if the site is still accessible.
  • A recent backup before disabling, updating, or replacing plugins.
  • A list of recent plugin, theme, or WordPress core changes.
  • A staging environment, if you need to test changes safely.

Common symptoms

Plugin compatibility problems usually appear in one of these ways:

  • Site errors: The site shows PHP errors, fatal errors, or a white screen.
  • Feature not working: A plugin, theme, form, checkout, search, or admin feature stops working.
  • Performance degradation: The site becomes slower after a plugin is installed or updated.
  • JavaScript errors: Browser console errors appear after enabling a plugin or optimization feature.
  • Settings not saving: Plugin or WordPress settings fail to save correctly.
  • Unexpected cache behavior: Pages show stale content or cache does not clear as expected.
  • Admin issues: WordPress admin becomes slow, partially broken, or inaccessible.

Common causes

Caching conflicts

Multiple caching layers can interfere with cache purging, dynamic content, logged-in sessions, or other WordPress behavior.

This may cause stale content, login issues, broken dynamic pages, or inconsistent frontend behavior.

Security plugin conflicts

Security plugins can overlap with platform-level security controls or other security plugins.

Firewall rules, login protection, IP blocking, rate limiting, geo-blocking, or similar functionality may block legitimate users or expected WordPress requests.

Optimization and asset conflicts

Plugins that modify CSS, JavaScript, images, fonts, or other frontend assets can conflict with each other or with the active theme.

Common examples include:

  • CSS or JavaScript minification
  • JavaScript defer or delay
  • Asset concatenation
  • Lazy loading
  • Image optimization
  • Font optimization

These conflicts can cause broken layouts, missing styles, JavaScript errors, forms that do not work, or other frontend problems.

Plugin update conflicts

A plugin update can introduce a compatibility problem with:

  • WordPress core
  • The active theme
  • Your PHP version
  • Another plugin
  • Custom code

This is more likely after major plugin, theme, WordPress, or PHP version changes.

Abandoned or unsupported plugins

Older or unmaintained plugins may no longer be compatible with current WordPress or PHP versions.

Plugins that have not been updated for a long time, generate recurring errors, or are no longer maintained should be reviewed and replaced when appropriate.

Diagnostic steps

Step 1: Confirm when the issue started

Identify what changed immediately before the problem appeared.

Check for:

  • Newly installed plugins
  • Recently updated plugins
  • Theme updates
  • WordPress core updates
  • PHP version changes
  • New cache or optimization settings
  • New security or firewall settings

If the problem started immediately after one change, investigate that change first.

Step 2: Check the error details

Collect available error information before making changes.

Check:

  • Frontend error messages
  • WordPress admin error messages
  • Browser console errors
  • PHP error logs
  • Plugin-specific logs, if available

Keep a copy or screenshot of relevant error messages.

Step 3: Reproduce the issue on Staging

Whenever possible, reproduce the problem on Staging before changing Production.

Use Staging to:

  • Deactivate plugins safely
  • Test plugin updates
  • Change plugin settings
  • Test optimization or security features
  • Check whether the issue occurs with the same theme and plugin stack

Step 4: Isolate the conflicting plugin

To identify the plugin causing the issue:

  1. Confirm that you have a recent backup.
  2. Use Staging whenever possible.
  3. Deactivate the suspected plugin.
  4. Test the affected page or feature.
  5. If the problem continues, reactivate the plugin and test the next suspected plugin.
  6. Repeat until you identify the conflict.

If you do not have a clear suspect, deactivate non-essential plugins one at a time and test after every change.

Step 5: Determine the conflict type

After identifying the plugin, determine which functionality is causing the problem.

Check whether it relates to:

  • Cache behavior
  • Security or access control
  • CSS or JavaScript optimization
  • Image or media handling
  • Database activity
  • Admin screens
  • Login or user sessions
  • WooCommerce, LMS, or membership functionality

Step 6: Review plugin settings

Check whether the problem can be resolved by disabling functionality that overlaps with another plugin or the Pressidium platform.

Disable one overlapping feature at a time and test the site after each change.

Common issues and solutions

A caching plugin conflicts with platform caching

Likely causes:

  • Multiple page caching layers
  • Conflicting cache purge behavior
  • Dynamic pages being cached incorrectly
  • Logged-in, cart, checkout, or session pages being cached unexpectedly

Resolution steps:

  1. Identify which plugin provides page caching.
  2. Disable duplicate page caching functionality where appropriate.
  3. Clear all relevant caches.
  4. Test the affected pages in a private browser window.
  5. Keep only the caching functionality required for your setup.

A security plugin blocks legitimate access

Likely causes:

  • IP blocking
  • Login protection
  • Rate limiting
  • Firewall rules
  • Country blocking
  • Overlapping bot protection

Resolution steps:

  1. Check whether the issue affects specific users, IP addresses, or countries.
  2. Review the security plugin logs, if available.
  3. Identify the rule or feature responsible for the block.
  4. Disable or adjust that specific feature.
  5. Test access again.

If legitimate traffic is still blocked and you cannot identify the cause, open a support request.

An optimization plugin breaks the layout or scripts

Likely causes:

  • CSS minification
  • JavaScript minification
  • JavaScript defer or delay
  • Asset concatenation
  • Lazy loading
  • Font optimization

Resolution steps:

  1. Disable the most recent optimization change.
  2. Clear the relevant caches.
  3. Test the affected page.
  4. Re-enable optimization features one at a time.
  5. If supported by the plugin, exclude the affected script, stylesheet, or page from optimization.
  6. Keep only the settings that work correctly with the site.

A plugin update causes errors

Likely causes:

  • A bug in the updated plugin
  • WordPress version incompatibility
  • PHP version incompatibility
  • Theme compatibility issue
  • Conflict with another plugin

Resolution steps:

  1. Identify the plugin that was updated.
  2. Review the error message and available logs.
  3. Reproduce the update on Staging if possible.
  4. Roll back to a known working version if necessary.
  5. Contact the plugin developer if the problem is isolated to the plugin itself.

The site shows a white screen or fatal error

A plugin PHP error, version incompatibility, or plugin/theme conflict can cause a white screen or fatal error.

  1. Review the error logs.
  2. Identify whether a plugin name or file path appears in the error.
  3. Deactivate the affected plugin if you can do so safely.
  4. Test the site again.

For complete troubleshooting steps, see White Screen of Death.

Plugin settings do not save

Likely causes:

  • JavaScript errors in WordPress admin
  • A security plugin blocking admin requests
  • REST API or AJAX conflicts
  • A plugin bug
  • Browser cache or session issues

Resolution steps:

  1. Test the setting in a private browser window.
  2. Check the browser console for JavaScript errors.
  3. Review recent security, optimization, or admin-related plugin changes.
  4. Reproduce the issue on Staging.
  5. Deactivate suspected plugins one at a time and test again.
  6. Contact the plugin developer if the issue is isolated to that plugin.

Verification

After applying a fix, verify that:

  • The original error no longer appears.
  • The affected page or feature works correctly.
  • WordPress admin loads normally.
  • Relevant browser console errors no longer appear.
  • Site performance has returned to expected levels.
  • Cache clearing and content updates behave correctly.
  • Required plugins can remain active without reproducing the problem.
  • The fix works in both normal and private browser sessions.

If you made the change on Staging, reproduce the same configuration on Production only after verification is complete.

Best practices

  • Test new plugins and significant updates on Staging before applying them to Production.
  • Keep plugins updated, but avoid updating several critical plugins at the same time.
  • Avoid using multiple plugins that provide the same functionality.
  • Remove plugins that are unused, abandoned, or duplicated.
  • Replace unsupported plugins with actively maintained alternatives.
  • Enable only the optimization and security functionality you need.
  • Review plugin changelogs before significant updates.
  • Document plugin and configuration changes so you can trace problems more quickly.
  • Monitor important website functionality after installing or updating plugins.

Need help?

Open a support request if:

  • You cannot identify the conflicting plugin.
  • The site shows critical errors after a plugin change.
  • WordPress admin is inaccessible.
  • A plugin conflict affects checkout, membership, LMS, or another business-critical feature.
  • You need help reviewing logs.
  • The problem continues after deactivating the suspected plugin.
  • You are unsure whether it is safe to deactivate a plugin.

Include:

  • The affected domain
  • Environment: Production or Staging
  • Plugin names and versions involved
  • Affected URLs or functionality
  • Exact error message or screenshot
  • Approximate time the issue started
  • Recent plugin, theme, WordPress, or PHP changes
  • Troubleshooting steps you already completed
  • Relevant error log entries, if available

Where to go next