Finding plugin conflicts is one of the more painful experiences you will ever have with WordPress. Unfortunately, there are next to zero shortcuts in the way you must do this.

The WordPress core was never built with Marketing in mind. In reality, as a Marketing Platform the default configuration of WordPress is one of the worst you could use. WordPress was in fact created as strictly a writing program. It took several Versions before you could even insert an image and get it to display properly. At first, this could only be done by directly adding the HTML code directly to the post.

WordPress plugins are the only reason WordPress works as a marketing Platform at all. Plugins can be anything from a small bit of code, to an entire standalone program in the case of some feature packed plugins.

Because of this, WordPress plugins don’t always play well together.

When this happens, it’s often no easy task to figure out which plugins are causing the problem. The video below explains how to do this. The video also offers some sound advice to help you determine more easily rather or not you have any conflicts between your plugins. There is also a good tip here that will warn you when a plugin will create a conflict. 

Troubleshooting WordPress Plugin Conflicts How to find conflicting Plugins in WordPress Troubleshooting WP plugins is usually a simple process of eliminating which one bre…

Unfortunately, the great tips given in this video don’t always come into play when trying to resolve a plugin conflict. Sometimes, the conflict is so subtle, you won’t even notice for quite some time. When a plugin conflict involves one of the many WordPress plugins that does it’s work entirely “behind the scenes” it can often take weeks or months before you notice that there is in fact a plugin conflict.

This is also when resolving plugin conflicts takes up the most time. If the problem you find occurs only for instance when you Publish a post, You will either have to publish a test post repeatedly, which can become a big mistake in a hurry. Or wait until the next time you post regularly to find out if you have deactivated the culprit.

WordPress “Pings” or sends a notification that a post has been published every time you cilck the “Publish” button. Unless you have installed one of the several WordPress plugins that limit a single post to only one ping a day you can quickly get banned by the services that monitor pings and relay the message to places like Google among others. This can have a terrible effect on the amount of traffic your site gets. At best, if you have no plugins that limit pings you must not republish the same post any sooner than 15 Minutes apart. That also goes for editing an already published post, something most people never even think about twice.

As mentioned in the video, any type of warning or error message when installing a new plugin is a sure sign you really don’t want to activate that plugin. 9 times out of 10, that means there is a plugin conflict. However, it can also happen when you install a plugin with poorly written code in it as well. Either way, your best bet is to deactivate that plugin right away, and remove it from your site by deleting it.

If the plugin is not  written properly even once deactivated, it will still become a target for every hacker in the Universe. Hackers have access to lists of every single badly written WordPress plugin that ever existed. The list is updated religeously every time a new one is discovered. Leave one on your blog after deactivating it, and even if you have awesome site security your blog WILL get hacked! I know this for a fact.

I have very secure WordPress installations. I get several new notices each day by email telling me of 1 or more IP addresses being locked out or banned from one of my blogs. The lockouts are for 1st time offenders, the bans are for repeated attempts. I have gotten as many as 400 in a 2 minute span,  ( I’ll save you the Math, that’s 3.33 attempts per Second!) all from different IP addresses.

It is certainly a pain in the rear to delete that many emails. But it’s a far, far better experience than getting hacked!

But despite all this security, I had one of my blogs hacked after a plugin with crappy code was leveraged by a hacker to just Waltz right in to my WordPress admin! Besides being amazed, (this had never happened before once I had beefed up security) I was completely embarrased.

If you identify a badly written plugin, delete it at once!

If you paid for it, contact the seller and get a refund! Tell them exactly why you’re asking them for a refund as well. Most sellers of badly written plugins are only thinking about the cash they’ll make. They usually have no idea what results that bad code can have on thier customers sites.

O.K., time to climb down off my soapbox and get back to resolving plugin conflicts.

Many plugin conflicts are easy to spot. If you discover a conflict right after installing a new plugin, simply deactivate it and delete the plugin once you have verified that it was indeed the plugin causing the problem. No more conflict!

If it has been weeks or longer since you activated any new plugins, your job get’s tougher.

If that’s the case there are two additional strategies you can put to use.

1. Try to think back and remember the last few plugins you installed if possible. By starting with those, you can often save considerable time when resolving conflicts.

2. Look at exactly what the conflict is, or affects. Often plugins with similar functions are the cause of plugin conflicts. By deactivating one or more plugins that pertain to the affected function your chances of finding the plugin that’s causing the problem increase greatly. This is far better than having to deactivate each plugin you may have installed until you find the right one.

 Hopefully, these tips will save you some aggravation the next time you need to resolve a WordPress plugin conflict.