Troubleshooting Conflicts
Discover how to identify whether a problem comes from RepairPlugin or from another plugin or theme on your WordPress site.
What can you do with this?
- Find out whether the problem is caused by RepairPlugin or by something else on your site
- Rule out caching as the cause of unexpected behavior
- Pinpoint exactly which plugin or theme is conflicting with RepairPlugin
- Know what information to send to support so they can help you quickly
Example: Your booking form suddenly stopped working after you installed a new security plugin. By following the steps below, you discover the security plugin is blocking RepairPlugin's form submissions — and you fix it in minutes.
Why conflicts happen
RepairPlugin is tested across hundreds of active installations. When a new update introduces an issue, the team typically hears about it right away and releases a fix quickly.
Most problems that appear to be RepairPlugin issues are actually caused by other software on your site:
- Caching plugins serve outdated versions of your pages, including expired security tokens
- Security plugins block form submissions, file downloads, or external connections
- Optimization plugins break your layout by minifying or combining RepairPlugin's CSS and JavaScript files
- SEO plugins change how page content is loaded, which can interfere with shortcodes
- Page builders sometimes override styles or load conflicting scripts
- Your theme may include custom JavaScript or aggressive CSS that clashes with RepairPlugin
That's why the steps below are so important — they help you (and support) understand where the problem actually comes from.
Where to find it
The debugging process uses standard WordPress admin pages:
- Plugins: Go to WordPress Admin > Plugins
- Themes: Go to WordPress Admin > Appearance > Themes
How to isolate the problem
Follow these steps in order. Most issues are resolved by Step 1 or Step 2.
Step 1: Clear your cache and test in incognito
Caching is the number one cause of "it suddenly stopped working" situations. A caching plugin or your browser may be serving an old version of your page.
- Clear your caching plugin's cache — go to your caching plugin's settings and purge all caches (page cache, object cache, CDN cache). Common plugins: WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache.
- Clear your browser cache — or better yet, open an incognito/private browsing window (Ctrl+Shift+N in Chrome, Cmd+Shift+N on Mac)
- Visit the page where the problem occurs
- Check if the problem is gone
If the problem disappears: Your cache was serving an old version of the page. Make sure your caching plugin excludes RepairPlugin pages from full-page caching. See Form Submission Failed for step-by-step cache exclusion instructions.
If the problem is still there: Move on to Step 2.
Step 2: Deactivate all plugins except RepairPlugin
This is the most reliable way to find out if another plugin is causing the issue.
- Go to Plugins
- Select all plugins except RepairPlugin using the checkboxes
- From the Bulk Actions dropdown, choose Deactivate and click Apply
- Clear your cache again (if your caching plugin is still active, or clear server-side cache from your hosting panel)
- Open an incognito window and visit the page where the problem occurs
- Check if the problem is gone
If the problem disappears: Another plugin is causing the conflict. Continue to Step 3 to find out which one.
If the problem is still there: Move on to Step 2b.
Step 2b: Switch to a default theme
If deactivating plugins didn't help, your theme might be the cause.
- Go to Appearance > Themes
- Activate a default WordPress theme (Twenty Twenty-Four, Twenty Twenty-Three, or any other "Twenty" theme)
- Visit the page where the problem occurs
- Check if the problem is gone
If the problem disappears: Your theme is causing the conflict. Contact your theme developer, or check if the theme has settings that interfere with RepairPlugin (like aggressive CSS minification, custom JavaScript loading, or layout overrides).
If the problem is still there with all other plugins disabled AND a default theme: The issue may be related to RepairPlugin itself. Contact support (see below) — you've now confirmed it's not a conflict.
Step 3: Find the conflicting plugin
Now that you know another plugin is the cause, find out which one:
- Reactivate your plugins one at a time
- After activating each plugin, clear your cache and check the page in an incognito window
- When the problem returns, the last plugin you activated is the one causing the conflict
- Write down the name and version of that plugin
Step 4: Resolve the conflict
Once you know which plugin is causing the problem:
- Check for updates — both RepairPlugin and the conflicting plugin may have newer versions that fix the issue
- Adjust the conflicting plugin's settings — common fixes include turning off CSS/JS minification, excluding RepairPlugin pages from optimization, or adding
*.repairplugin.comto a firewall whitelist - Find an alternative — if the conflict can't be resolved, consider replacing the conflicting plugin
- Contact support — share your findings so the team can investigate
Contacting support
The support team can help you most effectively when you've completed the steps above first. Here's what to include in your message:
- Email support@repairplugin.com
- Include:
- A description of the problem and when it started
- Which steps you completed from this guide and what you found
- The name and version of the conflicting plugin or theme (if you found one)
- Screenshots or a screen recording showing the issue
- A temporary WordPress admin account so the support team can investigate
- The support team can look into the issue directly on your site if you give them access
Tip: The more information you share upfront, the faster support can help. A message like "my form doesn't work" is hard to diagnose — but "my form stopped working after I installed Wordfence, and the problem goes away when I deactivate it" gives the team a clear starting point.
Frequently asked questions
What are the most common types of conflicts?
| Plugin type | What typically goes wrong | What to try |
|---|---|---|
| Caching plugins | Form submissions fail because of cached security codes | Exclude RepairPlugin pages from cache (see Form Submission Failed) |
| Security plugins | Downloads or form submissions get blocked | Add *.repairplugin.com to your firewall whitelist |
| Optimization plugins | CSS/JS minification breaks the layout | Exclude RepairPlugin files from minification (see Caching & Performance) |
| SEO plugins | The shortcode doesn't display correctly | Check if the SEO plugin changes page content output |
| Page builders | Layout looks broken or overlapping | Use the shortcode block or HTML widget in your page builder |
Do I have to test on my live site?
It's best to use a staging environment if your hosting provider offers one. That way your customers won't notice while you test. If you don't have staging, test during quiet hours and keep a backup ready.
How do I know if it's a conflict or a RepairPlugin bug?
Follow Steps 1 through 2b above. If the problem goes away when you clear your cache, deactivate other plugins, or switch to a default theme — it's a conflict. If the problem remains even with a default theme, no other plugins active, and a cleared cache — it may be a RepairPlugin issue. Contact support@repairplugin.com with your findings.
Do I really need to do all these steps before contacting support?
Yes — and here's why. RepairPlugin is tested across hundreds of installations, and the team monitors for issues after every update. If something breaks because of a RepairPlugin update, they usually know within hours and push a fix quickly. In most cases, the problem is caused by another plugin or a cached page. By completing these steps first, you help support skip the guesswork and jump straight to solving your specific situation.