How to Fix Critical Error in WordPress

What is a WordPress Critical Error?

A WordPress critical error (also known as the "White Screen of Death") occurs when your website encounters a fatal PHP error that prevents it from loading properly. Instead of your normal website, visitors will see a generic error message or a blank white page.

Step 1: Enable WordPress Debug Mode

Before fixing the error, you need to see what's actually causing it. WordPress debug mode will show you the specific error details and the exact file path causing the problem.

Accessing Your Files

You can access your website files through:

• cPanel File Manager: Login to your iFastNet client portal at https://ifastnet.com/portal/clientarea.php and access cPanel, or go directly to https://yourdomain.com/cpanel (replace "yourdomain.com" with your actual domain)
• FTP client (if you prefer)

Enable Debug Mode

1. Navigate to your website's root directory (usually public_html)
2. Find the wp-config.php file
3. Open it for editing
4. Look for the line that says define('WP_DEBUG', false);
5. Change it to: define('WP_DEBUG', true);
6. Add these lines just below it:

   define('WP_DEBUG_LOG', true);define('WP_DEBUG_DISPLAY', true);
   

7. Save the file

View the Exact Error Details

After enabling debug mode:

1. Refresh your website
2. WordPress will now display the specific error message with the exact file path causing the problem
3. Focus only on FATAL ERRORS - ignore any warnings or notices, as these won't cause the critical error

The error message will show something like:

• Fatal error in /home/yourdomain/public_html/wp-content/plugins/problematic-plugin/file.php
• Fatal error in /home/yourdomain/public_html/wp-content/themes/your-theme/functions.php

Step 2: Identify the Exact Plugin or Theme

Once debugging is enabled, WordPress will show you the exact path to the problematic file. Look for:

Plugin Errors

The path will include /wp-content/plugins/plugin-name/ - this tells you exactly which plugin is causing the issue.

Theme Errors

The path will include /wp-content/themes/theme-name/ - this tells you exactly which theme is causing the issue.

Step 3: Disable the Specific Plugin or Theme

Method 1: Disable the Specific Plugin (Recommended)

When you know the exact plugin from the error message:

1. Access cPanel File Manager through your iFastNet client portal
2. Navigate to /public_html/wp-content/plugins/
3. Find the specific plugin folder mentioned in the error
4. Rename only that plugin folder by adding -disabled to the end
   • Example: Change contact-form-7 to contact-form-7-disabled
5. Refresh your website - it should now load normally

Method 2: Disable the Specific Theme

When the error points to a theme file:

1. Navigate to /public_html/wp-content/themes/
2. Find the specific theme folder mentioned in the error
3. Rename the theme folder by adding -disabled to the end
   • Example: Change your-theme to your-theme-disabled
4. WordPress will automatically switch to a default theme
5. Your site should now work normally

Method 3: Disable All Plugins (Last Resort Only)

Only use this method if:

• The debug output doesn't clearly show which plugin is causing the issue
• You see multiple plugin errors
• The error message is unclear about the specific plugin

To disable all plugins:

1. Navigate to /public_html/wp-content/
2. Rename the entire plugins folder to plugins-disabled
3. Check if your site loads normally
4. If it works, you'll need to reactivate plugins one by one to find the culprit

Finding the Problematic Plugin After Mass Deactivation

1. Rename plugins-disabled back to plugins
2. Inside the plugins folder, enable plugins one at a time:
   • Rename each plugin from plugin-name-disabled back to plugin-name
   • Check your website after each activation
   • When the error returns, you've found the problematic plugin
3. Keep that plugin disabled and delete it

Step 4: Re-upload WordPress Core Files (If Plugin/Theme Not Identified)

If no specific plugin or theme is identified as the cause, the WordPress core files themselves may be corrupted. This is an excellent fix because corrupted WordPress core files can cause mysterious critical errors that don't point to any specific plugin or theme.

Why this works:

• Server issues, failed updates, or file transfer problems can corrupt WordPress core files
• Corrupted files may not show clear error messages in debug mode
• Fresh core files restore all WordPress functionality to working condition
• Your content, themes, plugins, and settings remain completely untouched

Step-by-step instructions:

Step A: Download Fresh WordPress Files

1. Go to wordpress.org/download
2. Download the latest WordPress zip file to your computer
3. Extract/unzip the files on your computer
4. You'll see a folder called "wordpress" with all the core files inside

Step B: Access Your Website Files

1. Login to your iFastNet client portal: https://ifastnet.com/portal/clientarea.php
2. Access cPanel File Manager
3. Navigate to your website's root directory (usually public_html)

Step C: Backup Your Important Files (Optional but Recommended)

1. Download a copy of your current wp-config.php file
2. This ensures you can restore your database connection if needed

Step D: Upload the Core Files Using cPanel File Manager

Method 1: Delete and Replace (Recommended)

1. In cPanel File Manager, select all files and folders in your WordPress root directory EXCEPT:
   • wp-config.php (do not select this)
   • wp-content folder (do not select this)
   • .htaccess file (do not select this)
2. Click "Delete" to remove the selected files and folders
3. Click the "Upload" button in File Manager toolbar
4. Click "Select File" and choose the WordPress zip file you downloaded
5. Wait for the upload to complete
6. Right-click on the uploaded zip file and select "Extract"
7. Open the extracted "wordpress" folder
8. Select all contents inside the "wordpress" folder
9. Click "Move" and move them to your root directory (public_html)
10. Delete the empty "wordpress" folder and the zip file

Method 2: Individual File Upload

1. On your computer, open the extracted WordPress folder
2. Select all files and folders EXCEPT:
   • wp-config-sample.php (don't upload this)
   • wp-content folder (don't upload this - keep your existing one)
3. In cPanel File Manager, click "Upload"
4. Select and upload all the chosen WordPress files
5. When prompted about overwriting existing files, choose "Yes" or "Overwrite All"
6. Wait for all files to upload completely

Step E: Test Your Website

1. Visit your website - it should now load without the critical error
2. Login to WordPress admin to ensure everything works properly
3. Your posts, pages, themes, and plugins should all be exactly as they were

What gets replaced:

• All WordPress core files (wp-admin folder, wp-includes folder, root PHP files)
• Any corrupted or missing WordPress system files

What stays the same:

• Your website content (posts, pages, media)
• Your themes and plugins (wp-content folder)
• Your database connection settings (wp-config.php)
• Your permalink structure (.htaccess file)

This fix resolves many "mystery" critical errors where the debug output doesn't clearly identify a specific plugin or theme as the cause.

Step 5: Other Possible Fixes

Memory Limit Issues

If the error mentions memory limits:

1. Edit your wp-config.php file
2. Add this line: ini_set('memory_limit', '256M');
3. Save the file

.htaccess Problems

1. Navigate to your website root directory
2. Find the .htaccess file
3. Rename it to .htaccess-backup
4. Check if your site loads
5. If it works, regenerate permalinks from WordPress admin

File Permissions

Ensure correct file permissions on your iFastNet CloudLinux cPanel server:

• Folders: 755 or 750
• Files: 644 or 640
• wp-config.php: 600

Step 6: Clean Up After the Fix

Delete the Problematic Plugin/Theme

Once you've identified the issue:

1. Instead of just disabling, delete the entire problematic plugin or theme folder
2. This prevents the issue from recurring
3. You can search for alternative plugins or contact the developer for a fix

Reactivate Other Plugins

If you disabled all plugins:

1. Reactivate the good plugins through WordPress admin (if accessible)
2. Or rename the plugin folders back to their original names via file manager

Step 7: Disable Debug Mode

Once you've fixed the error:

1. Edit wp-config.php
2. Change define('WP_DEBUG', true); back to define('WP_DEBUG', false);
3. Remove or comment out the debug log lines
4. Save the file

Getting Additional Support

If these steps don't resolve your critical error, iFastNet support can help you diagnose and fix the issue:

When to Contact Support

• The debug mode doesn't show clear error information
• You're not comfortable making file changes yourself
• The error persists after trying the above solutions
• You need help re-uploading WordPress core files safely
• You want a professional to investigate the root cause

What to Include in Your Support Request

• The exact error message from debug mode (if available)
• Steps you've already tried
• When the error first appeared
• Any recent changes made to your website

Accessing Support

• Visit: https://support.ifastnet.com/login.php
• First-time users: You'll need to register for a support account
• Create a support ticket with all the details above
• iFastNet's technical team can access your server to help resolve complex issues

Accessing Your Hosting

• Client Portal: https://ifastnet.com/portal/clientarea.php
• Direct cPanel Access: https://yourdomain.com/cpanel (replace with your domain)

Prevention Tips

1. Always backup before installing plugins or themes
2. Test plugins on a staging site first
3. Update gradually - don't update everything at once
4. Monitor your site after any changes
5. Keep WordPress core, themes, and plugins updated
6. Enable debug mode temporarily when troubleshooting issues

Important Notes for iFastNet Hosting

• Your hosting uses CloudLinux cPanel servers, which provide stable performance
• File manager access is available directly through cPanel
• Most critical errors can be resolved using the file manager without needing FTP
• Always use the exact file path from debug mode to identify the problematic plugin or theme
• Contact support if you're unsure about making file changes

Key Takeaway

Debug mode is your best friend - it tells you exactly which plugin or theme is causing the problem. Always enable it first and use the exact file path to disable only the problematic component. If no specific plugin or theme is identified, re-uploading WordPress core files often resolves mysterious critical errors. Only disable all plugins as a last resort when the debug output is unclear.

Remember: When in doubt, create a backup before making any changes to your website files.