Said It Here

Plugin causes fatal error and breaks WordPress admin area

Activating the plugin triggers an endless file scanning loop and breaks the post editor layout, preventing users from accessing settings. Some users also experience fatal backend errors that completely crash the WordPress Customizer and lock them out of routine site management.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    increasing PHP memory limit
  2. 2
    disabling other plugins one by one to find conflicts
  3. 3
    testing on a staging site first
  4. 4
    Rolling back the plugin to a previous compatible version
  5. 5
    Disabling automatic plugin updates
  6. 6
    Outsourcing the code refactoring or fix to an experienced developer
  7. 7
    Testing fixes and restores using a staging site copy

In their words

Unedited, most upvoted first, each linked to the thread it came from.

“The WordPress Customizer (Appearance > Customize) throws a fatal/backend error and won't load.”source ↗

“Right now I'm trying to weigh my options to do a bandaid fix (roll it back), to try to remove the plugin dependency myself, or to ultimately outsource to another developer with more experience.”source ↗

Mindless-Surround-81 · r/Wordpress · 10 upvotes

“I installed the premium plugin, and when I activated it, it wreaked havoc in the post admin area. It also kept looping me around in circles while scanning my files, so I never got to set it up.”source ↗

a2annie · r/Wordpress · 5 upvotes

Where this came up

r/Wordpresssoftware bugstroubleshootingweb developmentwordpress

People with this problem also raised