Fix: Neve Child Theme Causes a Critical Error or Site Crash

If your site becomes inaccessible after activating the child theme or after editing child theme files, the crash is almost always caused by custom code in the child theme — not by Neve itself.

Common causes:

• A syntax error or invalid PHP in functions.php
• A copied template file that is outdated after a Neve or WordPress update
• A conflict between custom code in functions.php and an active plugin

Recovering access when you cannot reach wp-admin

Use your hosting file manager or an SFTP client to regain access without needing to log in to WordPress:

1. Log in to your hosting control panel or connect via SFTP.
2. Navigate to wp-content/themes/.
3. Rename the child theme folder — for example, rename neve-child to neve-child-disabled. WordPress will fall back to the parent Neve theme and your site will become accessible again.
4. Once you have access to wp-admin, rename the folder back to neve-child, then diagnose and fix the cause before reactivating the child theme.

Isolating the cause

1. In wp-admin, go to Appearance > Themes and switch temporarily to the parent Neve theme to confirm the child theme is the source of the problem.
2. Deactivate plugins one by one to rule out a plugin conflict.
3. Open functions.php inside your child theme folder using your hosting file manager or SFTP client, and comment out recently added code blocks by wrapping them in /* ... */. Save and test after each change.
4. Check your PHP error log if your hosting provider makes it available — it will usually identify the exact file and line number that triggered the error.

⚠️ Important: Reinstalling Neve or upgrading to Neve Pro will not repair errors inside your child theme. The child theme folder is separate from Neve's files and is never overwritten by Neve updates or the Neve Pro plugin.

For safe alternatives to editing functions.php directly, see Theme File Editor Missing from WordPress Dashboard.