Fix WordPress Critical Error
Budget: $10 – $30 USD
Every time I click “Edit” on any page, WordPress throws the familiar “There has been a critical error on this website” message and boots me straight out of the editor. The front-end still renders and I can log into the dashboard, so the issue seems isolated to the page-editing workflow. The site is built with WPBakery, and I haven’t pushed any plugin, theme, or core updates recently, so whatever is breaking arrived quietly in the background.
I need someone to jump in, turn on WP_DEBUG or comb through the server error logs, pinpoint the exact conflict or fatal PHP call, and get the editor working again without touching live content or design. You’ll have full WordPress admin credentials and cPanel/FTP access the moment we start.
Acceptance is simple:
• Pages open and save normally inside WPBakery, without triggering the critical-error screen.
• A quick note summarising what caused the crash and the fix, so I can prevent a repeat.
If you’re comfortable tracing PHP errors, de-conflicting plugins, or rolling back broken hooks, this should be a straightforward rescue job.
I need someone to jump in, turn on WP_DEBUG or comb through the server error logs, pinpoint the exact conflict or fatal PHP call, and get the editor working again without touching live content or design. You’ll have full WordPress admin credentials and cPanel/FTP access the moment we start.
Acceptance is simple:
• Pages open and save normally inside WPBakery, without triggering the critical-error screen.
• A quick note summarising what caused the crash and the fix, so I can prevent a repeat.
If you’re comfortable tracing PHP errors, de-conflicting plugins, or rolling back broken hooks, this should be a straightforward rescue job.