Skip to content

Troubleshooting

“Culprit Finder couldn’t add its small helper file”

Section titled ““Culprit Finder couldn’t add its small helper file””

When you press Start, Culprit Finder copies a helper file into wp-content/mu-plugins/ and removes it when you’re done. If the folder isn’t writable, Start stays disabled. To fix it:

  1. With FTP or your host’s file manager, create wp-content/mu-plugins/ if it doesn’t exist.
  2. Copy wp-content/plugins/culprit-finder/mu-loader/culprit-finder-loader.php into it.
  3. Reload the Culprit Finder page.

Or ask your host to make the folder writable for WordPress. If the folder stays read-only, Culprit Finder can’t remove the file when you’re done; it does nothing without your troubleshooting cookie, and you can delete it with FTP whenever you like.

“A different file named culprit-finder-loader.php already exists”

Section titled ““A different file named culprit-finder-loader.php already exists””

Something other than Culprit Finder put a file with that name in wp-content/mu-plugins/. Culprit Finder never overwrites or deletes files it didn’t create, so it won’t start. Check what the file is, and rename or remove it yourself if you don’t need it.

Culprit Finder only switches plugins off for logged-in administrators with its session cookie, and marks those pages as not cacheable. Most caching plugins and hosts never cache pages for logged-in users anyway, so visitors keep getting the normal, full pages.

A server-level cache that ignores login cookies could in theory store a page meant only for you. If you use one, check with your host that logged-in pages aren’t cached, or exclude requests with the wp-culprit-finder cookie.

On a multisite network, Culprit Finder shows a notice and won’t start, and it can’t be network-activated. Support may come later.

“Your Site is Experiencing a Technical Issue” emails

Section titled ““Your Site is Experiencing a Technical Issue” emails”

When a step makes a page crash, WordPress may email you about it. That’s expected while troubleshooting: the crash only happened in your browser, with some plugins off. You can ignore these emails during a session.

While your session runs, the Plugins screen shows a notice and won’t let you activate or deactivate plugins. The list you see there is the shortened list for your browser, and saving it would change your real site. Exit first, then manage plugins as usual.

“Step 3 of about 7” is an estimate. If the search needs to look for a second plugin, the total grows a little.

See the FAQ, or contact us with your support report.

If your question is about the problem on your site rather than Culprit Finder itself, the guides cover the common ones: critical errors, plugin conflicts, a site that broke after an update and broken WooCommerce checkouts.

WordPress is a trademark of the WordPress Foundation. Culprit Finder is not affiliated with or endorsed by the WordPress Foundation.