Checking for a Plugin Conflict

Share on facebook
Share on twitter
Share on linkedin

Step 1: Note Any WordPress Plugin Conflict Symptoms

Before you can start resolving a plugin conflict, you have to realize whether there is one. When there’s a problem or error on your site, it’s usually fairly easy to spot. However, the cause of the problem is not always evident right away.

There are a few symptoms to watch for that might indicate a plugin conflict is occurring on your site:

  • The plugin isn’t working as it should. If one of your plugins isn’t functioning the way it’s supposed to, it could be because its code is conflicting with your theme, another plugin, or WordPress’ core.
  • Some element of your site is broken. A ‘broken’ WordPress site can take on many different forms. Your site’s appearance may be off, certain functions may not work, or you could see full-blown errors. These issues could be the result of a plugin conflict.
  • You’re seeing the White Screen of Death (WSoD.) One of the most infamous WordPress errors, the White Screen of Death, often occurs because of a plugin conflict. This is one of the most serious symptoms, as it prevents users from accessing your site.

If you’re seeing one of these issues on your site, you’ll want to proceed with the next steps to determine it is indeed due to a plugin conflict.

Step 2: Restore Your Last Backup

Your first course of action should be to restore a backup of your site, especially if you aren’t able to access your WordPress dashboard. This will clear up the effects of the plugin conflict so your site is useable again.

How you carry out this step will depend on how and where you’ve saved your backups. However, if you’re experiencing a plugin conflict there’s a fair chance you may not be able to access your site’s back end. In this case, you’ll need to restore your backup manually.

Step 3: Determine Which Plugin Is Causing the Problem

Although restoring a backup will clear up the symptoms of your plugin conflict, you probably made the changes that led to the issue for a reason. So, it’s important to do a little more digging to find the root of the problem and get your website in tip-top shape.

This means tracking down the plugin causing the conflict. If your site broke immediately after a specific installation or upgrade, you probably already know which tool is the culprit. However, automated and bulk updates may leave you in the dark.

If this is the case, the best place to start is deactivating all your plugins except for any Wilcity related plugins. To do so without access to the back end, you’ll need to connect to your server via FTP. Then, navigate to wp-content > plugins.

There are two ways to deactivate your plugins from here. You can either create a backup of all the files and delete them from your server, or you can simply rename the files on your server:

Renaming a plugin file via FTP.

Step 4: Delete, Replace, or Roll Back the Conflicting Plugin

Once you’ve determined which plugin (or plugins) is causing the conflict on your WordPress site, you have a few options for dealing with it. If it’s not integral to the function of your site, you may want to consider simply deleting it and going without.

If you do need the functionality the plugin provides, you can always search for an alternative. It’s pretty rare to not be able to find two plugins that provide similar features, so this shouldn’t be too difficult.

Finally, if a recent update instigated the plugin conflict on your site, you can roll it back. This simply means you’ll revert to the previous version of the plugin. One of the easiest methods for accomplishing this is with the WP Rollback plugin:

The plugin rollback option.

Leave a Reply

Your email address will not be published. Required fields are marked *

WilCity Guide Bug Report