How to Access WordPress Admin When There’s a Fatal Error

If your WordPress website is showing a fatal error and you can’t access the admin dashboard (wp-admin), don’t panic. This guide shows you how to regain access and fix the issue, even when WordPress won’t load.

Understanding WordPress Fatal Errors

A fatal error stops WordPress from loading completely. You’ll typically see:

• A blank white screen (the “White Screen of Death”)
• An error message on your site
• “There has been a critical error on this website”
• Your wp-admin login page won’t load

Common Causes

Fatal errors are usually caused by:

• Plugin conflicts – A plugin that’s incompatible with your WordPress version or another plugin
• Theme issues – A faulty or outdated theme
• PHP version incompatibility – Your hosting PHP version doesn’t match what the plugin/theme needs
• Corrupted files – Files that were damaged during an update
• Memory limit exceeded – WordPress ran out of allocated memory

Example Fatal Error

You might see errors like this in your logs:

PHP Fatal error: Uncaught ReflectionException: Method ElementorPro\Modules\ThemeBuilder\Documents\Section::get_site_editor_type() does not exist in /home/username/public_html/wp-content/plugins/elementor-pro/modules/theme-builder/documents/theme-document.php:45

This example shows an Elementor Pro plugin error, but the fix process is the same for any plugin or theme.

Quick Navigation

Choose your method:

→ Method 1: Rename the Plugins Folder (Fastest – disables all plugins)
→ Method 2: Rename Individual Plugin Folders (When you know which plugin is causing the issue)
→ Method 3: Switch to a Default Theme (When it’s a theme issue)
→ Method 4: Enable WordPress Debug Mode (Find the exact cause)
→ Method 5: Restore from Backup (If nothing else works)

Method 1: Rename the Plugins Folder (Fastest Fix)

Renaming the plugins folder disables all plugins at once, allowing you to access wp-admin.

Steps

1. Log in to Ecenica Dashboard
2. Open File Manager
3. Navigate to public_html/wp-content/ (or wherever your WordPress is installed)
4. Find the plugins folder
5. Right-click the plugins folder and select Rename
6. Rename it to plugins-disabled or plugins-old
7. Try accessing your WordPress admin at yourdomain.com/wp-admin

What Happens?

• WordPress can’t find the plugins folder, so it loads without any plugins
• You can now log in to wp-admin
• All your plugins are deactivated but not deleted

After You’re Logged In

1. Rename the folder back to plugins
2. Go to Plugins in WordPress admin
3. All plugins will show as “Inactive”
4. Activate plugins one at a time to identify which one caused the error
5. When the error returns, you’ve found the problematic plugin
6. Leave that plugin deactivated and contact the plugin developer or find an alternative

Method 2: Rename Individual Plugin Folders

If you know which plugin is causing the issue (e.g., from error logs), you can disable just that plugin.

Steps

1. Log in to Ecenica Dashboard
2. Open File Manager
3. Navigate to public_html/wp-content/plugins/
4. Find the folder for the problematic plugin (e.g., elementor-pro)
5. Right-click the plugin folder and select Rename
6. Rename it by adding -disabled to the end (e.g., elementor-pro-disabled)
7. Try accessing your WordPress admin at yourdomain.com/wp-admin

What Happens?

• WordPress can’t find that specific plugin, so it’s disabled
• Other plugins continue working normally
• You can now log in to wp-admin

After You’re Logged In

Option 1: Delete and reinstall the plugin
1. In WordPress admin, go to Plugins
2. The problematic plugin will show an error
3. Click Delete
4. Reinstall the plugin from the WordPress repository or download a fresh copy

Option 2: Keep it disabled
1. Leave the folder renamed
2. Find an alternative plugin
3. Delete the disabled plugin folder when you no longer need it

Method 3: Switch to a Default Theme

If the error is caused by your theme, you can switch to a default WordPress theme.

Steps

1. Log in to Ecenica Dashboard
2. Open File Manager
3. Navigate to public_html/wp-content/themes/
4. Find your active theme folder (e.g., your-theme)
5. Right-click and select Rename
6. Rename it to your-theme-disabled
7. WordPress will automatically fall back to a default theme (like Twenty Twenty-Four)
8. Try accessing your WordPress admin at yourdomain.com/wp-admin

What Happens?

• WordPress can’t find your theme, so it uses a default one
• Your site will look different, but you can log in
• Your theme files aren’t deleted

After You’re Logged In

1. Go to Appearance > Themes in WordPress admin
2. Activate a default WordPress theme temporarily
3. Rename your theme folder back to its original name
4. Either fix the theme or switch to a different one

Method 4: Enable WordPress Debug Mode

Debug mode shows detailed error messages that help identify the exact problem.

Steps

1. Log in to Ecenica Dashboard
2. Open File Manager
3. Navigate to your WordPress root directory (usually public_html)
4. Find and edit the wp-config.php file
5. Look for this line:
   php
define('WP_DEBUG', false);
6. Change it to:
   php
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
7. Save the file
8. Try to load your website

What Happens?

• WordPress logs all errors to wp-content/debug.log
• Errors aren’t shown on your public site (because WP_DEBUG_DISPLAY is false)
• You can review the log file to find the exact cause

Checking the Debug Log

1. In File Manager, navigate to wp-content/
2. Find and open debug.log
3. Look for recent errors that mention:
   • Plugin names
   • Theme names
   • File paths
   • Line numbers

This tells you exactly which plugin, theme, or file is causing the problem.

After Fixing the Issue

Turn off debug mode:
1. Edit wp-config.php again
2. Change back to:
php
define('WP_DEBUG', false);
3. Delete the debug.log file (optional)

Method 5: Restore from Backup

If nothing else works and you have a recent backup, restoring is the quickest solution.

Using Ecenica Backups

If you have Ecenica hosting with automatic backups:

1. Log in to the Ecenica Dashboard
2. Go to your hosting service
3. Look for Backups or Restore
4. Select a backup from before the error occurred
5. Choose to restore just your WordPress files or the entire site
6. Confirm the restoration

Note: This will overwrite current files, so any changes made since the backup will be lost.

Using a Plugin Backup

If you created backups with a plugin (e.g., UpdraftPlus, BackupBuddy):

1. Use Method 1 to regain wp-admin access
2. Go to your backup plugin
3. Choose a backup to restore
4. Follow the plugin’s restore process

Manual Backup Restoration

If you have manual backups:

1. Download your backup files
2. In Ecenica Dashboard, open File Manager
3. Delete the current WordPress files (or rename the folder)
4. Upload your backup files
5. Restore your database using phpMyAdmin (if included in backup)

Preventing Future Fatal Errors

1. Always Backup Before Updates

Before updating plugins, themes, or WordPress:

1. Create a full backup of your site
2. Store it somewhere safe (not just on your hosting)
3. Test the update on a staging site if possible

2. Update One Thing at a Time

Don’t update all plugins and WordPress at once:

1. Update WordPress core first
2. Test your site
3. Update one plugin at a time
4. Test after each update
5. If something breaks, you know exactly what caused it

3. Check Plugin Compatibility

Before updating:

1. Read the plugin’s changelog
2. Check if it’s compatible with your WordPress version
3. Look for known issues in reviews or support forums
4. Wait a few days after a major release to let others find bugs first

4. Use a Staging Site

Ecenica hosting supports staging sites where you can:

1. Test updates safely
2. Try new plugins
3. Make changes without affecting your live site
4. Push changes to live only when everything works

5. Keep PHP Updated

1. Check which PHP version your site uses in Ecenica Dashboard
2. Use PHP Selector to upgrade to a supported version
3. Test on staging first
4. Most modern plugins require PHP 8 or higher

6. Monitor Your Error Logs

Regularly check your WordPress error logs:

1. Enable debug logging (as shown in Method 4)
2. Review debug.log weekly
3. Fix small issues before they become fatal errors

Common Fatal Error Scenarios

Scenario 1: Error After Plugin Update

What happened: You updated a plugin and the site broke.

Solution:
1. Use Method 2 to disable the updated plugin
2. Reinstall the previous version of the plugin
3. Contact the plugin developer about the issue
4. Wait for a bug fix update

Scenario 2: Error After WordPress Core Update

What happened: You updated WordPress and the site broke.

Solution:
1. Use Method 1 to disable all plugins
2. Check which plugins are incompatible with the new WordPress version
3. Update those plugins or find alternatives
4. Reactivate plugins one by one

Scenario 3: Error After Theme Update

What happened: You updated your theme and the site broke.

Solution:
1. Use Method 3 to switch to a default theme
2. Contact your theme developer
3. Either wait for a fix or switch themes
4. Consider using a child theme to preserve customizations

Scenario 4: Random Fatal Error

What happened: The site broke without you changing anything.

Possible causes:
– Your hosting updated PHP version automatically
– A plugin auto-updated
– Server configuration changed

Solution:
1. Check your Ecenica hosting for recent PHP version changes
2. Use Method 4 to enable debug mode and find the cause
3. Contact Ecenica support if it’s server-related

When to Contact Ecenica Support

Contact Ecenica support if:

• You’ve tried all methods and still can’t access wp-admin
• The error is related to server configuration (not plugins/themes)
• You need help restoring from a backup
• You see errors mentioning “memory limit” or “execution time”
• You suspect the server is experiencing issues

What to include in your support request:
– Your domain name
– A description of what happened before the error
– Any error messages you’re seeing
– What you’ve already tried
– Contents of your debug.log file (if available)

Frequently Asked Questions

Will renaming the plugins folder delete my plugins?
No. Renaming just disables them temporarily. All your plugin files and settings remain intact.

I renamed the plugins folder but still can’t log in. What now?
The issue might be with your theme. Try Method 3 to switch themes, or enable debug mode to see the exact error.

Can I fix this without File Manager access?
Yes, if you have FTP access. The steps are the same, just use your FTP client instead of cPanel File Manager.

My entire website is blank. Is it a fatal error?
Probably. A blank screen (White Screen of Death) is usually a fatal PHP error. Follow Method 1 to fix it.

How do I know which plugin caused the error?
Check your error logs (in wp-content/debug.log) or reactivate plugins one at a time after using Method 1. The error returns when you activate the problematic plugin.

Can I prevent fatal errors completely?
Not completely, but you can minimize them by: backing up regularly, testing updates on staging sites, keeping everything updated, and using quality plugins from trusted developers.

Will I lose data by renaming plugin folders?
No. Plugin data is stored in your WordPress database, not in the plugin folders. Renaming folders just disables plugins temporarily.

The error mentions “memory limit”. How do I fix that?
Memory limit errors require increasing PHP memory. Contact Ecenica support to increase your memory limit, or add this to wp-config.php:

define('WP_MEMORY_LIMIT', '256M');

Should I delete the problematic plugin?
After disabling it, try reinstalling first. If that doesn’t work, look for an alternative plugin. Always backup before deleting.

Need Help?

If you’re unable to fix the fatal error or need assistance accessing your WordPress admin, contact Ecenica support. Our technical team can help diagnose the issue and get your site back online quickly.

Include your error logs and details about what happened before the error occurred for the fastest resolution.