Plugin Safety and Conflicts: What to Know and How to Diagnose Them

Oct 21, 2026

How PerfectReputations Plugins Are Built to Be Safe

Every PerfectReputations plugin is built to do its job without getting in the way of anything else on your website. We follow WordPress coding standards, test each plugin before release, and design every one around a few firm rules. These rules protect your website, your visitors, and your data.

  • No changes to WordPress itself. Our plugins never edit WordPress core files or your theme’s files. Everything they do happens through the official WordPress systems built for plugins, so a WordPress update does not break them.
  • Their own names for everything. Each plugin gives its settings, functions, and database tables names unique to that plugin. This keeps our plugins from colliding with names other plugins use.
  • Security checks on every action. Admin actions check that the person is logged in with the right permissions and that the request truly came from your dashboard. Information people type in is cleaned before it is saved and again before it is shown.
  • Heavy work only when you ask. Scans, checks, and other demanding tasks run only when you click a button, never on a timer and never while visitors load your pages. Your website stays fast for the people using it.
  • Clean removal. When you delete one of our plugins, it removes its own settings and data, leaving your website as it found it.
  • Updates on your terms. We never push updates to your website. You are notified when a new version is ready, and you choose when to install it.

These rules make our plugins safe to install and safe to remove. They cannot, however, control how other plugins on your website behave, which is where conflicts come from.

Why Plugin Conflicts Still Happen

A WordPress website is a shared space. Your theme and every active plugin run together on every page, and they all draw on the same WordPress systems, the same page, and the same server. A well-built plugin follows the rules for sharing that space. A poorly built one does not, and when it breaks a rule, other plugins can suffer for it.

Conflicts usually come from a few common habits in less carefully written plugins. Some load their own copy of a shared script library, such as jQuery, in an older version that replaces the one WordPress provides. Some use generic names for their functions or styles, which then clash with another plugin using the same name. Some add broad styling rules that change the look of every button or table on your website, not just their own. Others run heavy work on every page load, which slows everything down and can cause timeouts.

Your server and theme play a part too. An outdated PHP version, a low memory limit, or an aggressive caching or security plugin can block or change what another plugin is trying to do. Heavily customized themes, including page builders such as Avada, sometimes handle scripts and layouts in their own way.

None of this means your website is broken or that a conflict is your fault. It means that when many pieces of software from many authors share one space, sometimes two of them disagree. The steps below show you how to find out which two.

Signs of a Plugin Conflict

A conflict rarely announces itself by name. Instead, something that worked yesterday stops working today, usually right after you install, update, or activate a plugin. Watch for these signs:

  • A blank white screen, or a message saying “There has been a critical error on this website,” on the front end or in the dashboard.
  • Buttons, menus, sliders, or forms that stop responding, often because a script failed to load or another script broke it.
  • A layout that suddenly looks wrong, such as shifted columns, oversized buttons, or missing styling, when one plugin’s styles override another’s.
  • The page builder or editor will not load, or it spins without opening.
  • Pages that load much more slowly than before, or time out completely.
  • Error messages in the dashboard naming a plugin file, a function, or a memory limit.

Timing is your best clue. If the problem began right after a specific change, that change is the first place to look.

How to Diagnose a Plugin Conflict

Diagnosing a conflict is a process of elimination. You switch things off until the problem disappears, then switch them back on one at a time until it returns. Work through these steps in order, and stop as soon as you find the cause.

  1. Back up first. Take a fresh backup of your website before you change anything. If a step makes matters worse, you can restore it in minutes.
  2. Clear every cache. Clear your caching plugin, your host’s cache, any content delivery network such as Cloudflare, and your browser. Many problems that look like conflicts are really old copies of pages and scripts. Reload the page and check whether the problem is still there.
  3. Read the error. If WordPress shows a critical error, check the email address on your WordPress account; WordPress usually sends a message naming the plugin or theme that caused it, with a special link to log in safely. For buttons or menus that stopped working, press F12 in your browser, open the Console tab, and reload the page. Red error lines often name the exact plugin folder at fault.
  4. Undo the latest change. If the problem began right after you installed or updated a plugin, deactivate that plugin first. If the problem disappears, you have found your answer.
  5. Turn everything off safely. Install the free Health Check & Troubleshooting plugin from WordPress.org. Its Troubleshooting Mode switches off all plugins and switches to a default WordPress theme for you alone, while your visitors keep seeing the normal website. If the problem disappears in Troubleshooting Mode, a plugin or your theme is the cause.
  6. Turn things back on one at a time. Still in Troubleshooting Mode, enable your plugins one by one and check for the problem after each. When the problem returns, the plugin you just enabled is half of the conflict. To find the other half, keep that plugin on and switch the others off and on again until you find the pair that fails together. With many plugins, save time by enabling half of them at once, then narrowing down within whichever half shows the problem.
  7. Test your theme. If every plugin works with the default theme but fails with yours, the conflict is with your theme. Note which plugin and which theme feature fail together.
  8. Check your server’s health. Go to Tools, then Site Health, to see your PHP version, memory limit, and any warnings. An outdated PHP version or a low memory limit causes errors that look like conflicts, and your host can fix both.
  9. Confirm the result. Repeat the failing combination once more to be sure it is the true cause. Then exit Troubleshooting Mode, and keep the conflicting plugin deactivated until a fix is available.

Write down what you find as you go: the plugins involved, their version numbers, what you clicked, and any error messages. Those notes turn a vague complaint into a problem a developer can fix quickly.

If Something Goes Wrong

The good news is that if any plugin installs and has an issue, you can undo it either by deleting the plugin from WordPress’ own listing of plugins, or, worst case, just go to your website hosting provider’s dashboard (such as Plesk) and delete the plugin from the Plugins folder.

You will find that folder at wp-content/plugins, with one folder for each plugin. When WordPress can no longer find a plugin’s folder, it switches that plugin off automatically, and your website returns to normal on the next page load. If you would rather keep the plugin’s settings while you investigate, rename its folder instead of deleting it, for example by adding -off to the end of the name. Renaming it back later and reactivating the plugin brings everything back as it was.

Report the Conflict So It Gets Fixed

Once you know which plugins conflict, tell the people who can fix it. If a PerfectReputations plugin is involved, open a ticket at our help desk and include your notes: both plugin names and versions, your WordPress and PHP versions, your theme, the steps that cause the problem, and any error messages or screenshots. We look at every conflict report, even when the cause sits in the other plugin, because we want our plugins to work smoothly alongside the tools you rely on.

Send the same details to the author of the other plugin as well. A clear, specific report gets a faster fix than a general complaint, and it helps every other website using the same combination. In the meantime, keep the conflicting plugin switched off, or ask us whether a setting can work around the problem until a fix arrives.

Never send the actual plugin zip file to either party as this violates license terms and may also be a copyright violation.