When you find a critical error on a website, often displayed as “There has been a critical error on this website,” it is a serious problem that prevents the website from functioning properly. Then how to solve it? Learn from this blog post.
Introduction: Navigating the “There Has Been a Critical Error on This Website” Message
You’re sipping your morning coffee and you’re all set to make a few changes to your WordPress site, but instead, you’re greeted with this scare-tactic message: “This website has a critical error.” Panic sets in. I have been there, and I know how frustrating it can be.
This isn’t just any old error; it is WordPress’ way of telling you that something has gone amiss. It doesn’t matter if it’s a plugin conflict, a theme problem, or that pesky PHP issue you can never remember how to fix, the end result is always the same — your site is down and you’re reaching for answers.
Getting to Grasp With a Fatal Mistake
When you receive WordPress critical error message it mostly means that there’s a fatal PHP error on the website which is stopping the site from loading. Common culprits:
Plugin conflict: If plugins are not compatible or are outdated, these can mess up your website.
Theme problems: Sometimes it is the theme or a recent update that is creating the problem.
PHP Errors: This message can be caused by errors in your site code or going over the PHP memory limit.
Database Corruption: Issues in your WordPress database could also cause critical errors.
Email That Never Arrives:
Generally speaking, WordPress will send an email to the site admin with information about the error- and provide a link to recovery mode. But what if that email never comes? You’re not alone. A lot of users report not getting this critical email, effectively stranding them with no direction over what to do next.
Real-Life Scenarios
I recall once on WordPress when I updated a plugin, it took my entire site down. No mail, no dashboard, just a terrible critical error. (It was the plug-in which didn’t work with the latest WordPress version) I got access by the FTP and renamed the plugin folder which made me get access again and which I could then solve the problem.
Looking at another case, for example, we had a client who had just installed a new theme, and then their site crashed. And again, no emails were handed over. We had to go to the hosting control panel and change the active WordPress theme to the standard default at the time (and today), which brought the site back online.
What does this guide cover?
In this ultimate guide, you’re going to learn:
Discover the root of the problem: Find out if the source of a critical error is a code error or not.
Step-by-step fixes: If it’s a plugin, theme, or PHP problem, we’re going to guide you through the solutions.
Special cases: How I debug WooCommerce or Elementor issues.
If Emails are not coming: Steps you can go through when trying to revive your site but haven’t received any recovery mode email.
Prevention tips: How not to hit this error in the future.
At the end of this guide, you should have the power and tools to directly correct the error “This website has encountered a critical error” with the least amount of downtime and as satiny as a ride on a freshly slicked slide on WordPress.
Section 1: What Does “There Has Been a Critical Error on This Website” Actually Mean?
If you’ve ever seen the error message “This website has encountered a critical error” while you’re working on a WordPress site, you’re not alone. This type of error is usually accompanied by a blank screen and means if there is a server-level error WordPress can’t work properly.
Understanding the #### Error
This white screen of death error message is WordPress’s way of telling you that a fatal problem has occurred, mostly with regard to the processing of PHP code. Common causes include:
Plugin Incompatibilities (Depreciated or Badly Coded): A plugin conflict can destroy the functionality of the site.
Theme Issues: Corrupt theme files in an active theme can cause crashes.
PHP Memory Limits: Hits the wall and stops the process if too much memory is asked.
Corrupted Core Files: If some of your WordPress core files is missing or modified, you may face a similar error.
Sometimes the error message will tell you to check your site admin email for further explanation. This email often includes details about the particular problem and a link to recovery mode. But if the email is not sent properly from your site, you will not get this message.
Typical situations that result in the #### error
Considering the user-reported experiences and community discussions, the following causes usually result in this crucial error:
Plugins updates: A plugin update may cause conflicts if not checked for compatibility first. (Reddit)
Theme modifications: Modifications of themes without proper testing for compatibility may cause errors.
Bespoke code: Implementing code practices that have not been fully tested can cause site downtime.
Server settings change: Changing server configuration settings like PHP versions without knowing what you are doing can cause issues.
Effects on User Experience and SEO
A site that shows these critical errors will not show up for visitors, which may cause a bad user experience and loss of confidence. Long downtimes can also lead to some SEO consequences:
Crawl problems – Although this is simply guesswork for me, there is a possibility that search engine bots are unable to crawl your site properly.
Search Rank Changes: Increased accessibility may cause search ranks to drop.
Higher Bounce Rates: Error-ridden pages drive site visitors away, suggesting to search engines that your quality is low.
Action to Take
To fix this error:
Step Written guide for WordPress wp-config debugging: Open up your wp-config. php file so you might be seeing debug info.
Check The Internal Logs: Log in to your cpanel and access the error logs on your server, or contact your hosting provider’s support to find what is causing this.
Deactivate Plugins/Themes: Use an FTP client or your host’s file manager to rename the Plugins or Themes folders to deactivate them.
Restore from Backup: Restores your site from a backup, if available.
Get in Touch with Hosting Support: If you can’t seem to figure out the problem, reach out to your host to ask for help.
Take caution, after all, since most of these problems can be avoided by having regular backups and applying updates with care. Make sure to always test things on a staging site before doing it live.
Section 2: How to Find the Cause of a WordPress Critical Error
If you’re hit with the dreaded message and headline “This website has encountered a critical error,” it’s not all doom and gloom, so don’t panic. This issue usually occurs due to reasons such as plugin conflicts, theme glitches, or corrupted core files. We can go through and diagnose the problems and get them fixed so come on in.
🔍 1. Link to error logs in cPanel or hosting provider
You can typically access error logs in your hosting control panel (for example, cPanel). Go to “Errors” to view recent logs. Being able to trace which file or plugin has an issue at a given moment can be traced down with these logs. If you are unsure of how to retrieve these logs, refer to your hosting provider’s documentation or support.
🐞 2. Enable WP_DEBUG Mode
Or you can enable WP debug mode to see if that uncovers any hidden errors:
Log into your site’s root directory using FTP or a file manager.
Open the wp-config.php file.
Append or modify the following lines:
“php
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define( ‘WP_DEBUG_DISPLAY’, false );
@ini_set(‘display_errors’,0);
Save the file and go back to your site. Errors will be recorded in the wp-content/debug. log file to assist you in identifying the offender.
📧 3. If there’s a recovery email link (if they’re available)
From WordPress 5.2, when a critical error arises, the recovery mode feature will send a mail:
Look in your admin email (including your spam) for an email that says “Your site is experiencing a technical issue.”
Click the link below to go to your recovery dashboard.
Disable the offending plugin or theme as directed.
If you do not receive the email, it may be because the email settings are misconfigured. You may find that it’s worth setting up SMTP on your site so that future email gets delivered properly.
🔌 4. Most likely offenders: Plugins, themes, and core files
According to the developers and support sites/forums: reflected in some comments include:
Plugin conflicts**: After updates in particular. Try disabling all the plugins, and enabling them one by one to find which one is causing the issue.
Theme Issues**: Change to the default theme (e.g. TwentyTwenty-One) to check whether the issue persists.
Corrupt Core Files**: Re-install WP core files without losing your content.
Sometimes a hard error can be hard to work with, but through systematic troubleshooting, you can diagnose and resolve the issue. Doing regular backups, testing all updates of plugins or themes, and monitoring it will lessen the chances of happening.
If you need more support or have more questions, do not hesitate and ask!
Section 3: Step-by-Step Guide to Fix “There Has Been a Critical Error on This Website”
🔧 How I Fixed the “There Has Been a Critical Error on This Website” in WordPress (Step-by-Step)
One morning, I opened my WordPress site and was greeted with a terrifying message:
“This website has encountered a critical error.”
No dashboard access, no email notification—just a blank screen.
After some trial and error, I found a simple method to fix this problem. Here’s how you can fix it:
🛠️ Step 1: Restore from a recent backup
If you have a backup, you can quickly fix the problem by restoring it.
- Using a plugin: If you use a plugin like UpdraftPlus, navigate to your hosting control panel or use FTP to access your site files. Locate the backup files and restore them.
- Hosting provider backup: Most hosting providers offer automatic backups. Check your hosting dashboard for backup options and restore your site to a previous state.
Note: Always make sure you have a recent backup before making significant changes to your site.
🔌 Step 2: Deactivate all plugins via FTP or file manager
If restoring a backup is not an option, the next step is to deactivate all plugins:
- Access your site files: Use an FTP client like FileZilla or your hosting provider’s file manager to access your site files.
- Navigate to the plugins folder: Go to the
/wp-content/
directory and locate theplugins
folder. - Rename the plugins folder: Right-click on the
plugins
folder and rename it toplugins_deactivated
. This will deactivate all plugins. - Check your site: Visit your website to see if the error is resolved.
- Reactivate plugins one by one: Rename the
plugins_deactivated
folder back toplugins
. Then, reactivate each plugin one by one through the WordPress dashboard to identify the culprit.
🎨 Step 3: Switch to the default theme
If deactivating plugins doesn’t fix the problem, your theme might be the problem:
- Access the themes folder: Navigate to
/wp-content/themes/
via FTP or file manager. - Rename the active theme folder: Find your active theme folder and rename it (e.g.,
mytheme_old
). - Activate Default Theme: WordPress will automatically revert to the default theme, such as Twenty Twenty-Four.&x20;
- Check Your Site: Visit your website to see if the error is resolved.
📬 What to do if you don’t receive the recovery email
Sometimes, WordPress fails to send the recovery email. Here’s what you can do:
- Check Spam/Junk Folder: Make sure the email didn’t end up in your spam or junk folder.
- Access Recovery Mode Manually: Add
/wp-login.php?action=entered_recovery_mode
to your site URL (e.g.,yoursite.com/wp-login.php?action=entered_recovery_mode
) to access recovery mode. - Configure SMTP Settings: Use a plugin like WP Mail SMTP to configure your site’s email settings to ensure that future emails are delivered correctly.
By following these steps, I was able to fix a critical error on my WordPress site. Remember, regular backups and careful plugin/theme updates can prevent such issues in the future.
If you need further help or have any questions, feel free to ask!
Section 4: WordPress-Specific Fixes
🛠️ WordPress-Specific Fixes for the “There Has Been a Critical Error on This Website” Message
It can be nerve-racking to see the infamous “This website has encountered a critical error” message. From my experience, this is usually a result of a WordPress core problem. Here are a few useful tricks.
🔄 1. Reinstall WordPress Core Files Without Jeopardizing Your Site
Critical errors can be caused by corrupted core files. To fix this:
Use a backup service like UpdraftPlus to back up your site.
**Get the latest WordPress version from WordPress.org.
Unzip the file and upload everything except the wp-content folder and the wp-config. php file via FTP.
This procedure refreshes the default files and does not bother the contents or settings.
⚙️ 2. Fix wp-config. php and. htaccess issues
As you know, poorly-settings in these files can cause big problems!
wp-config. php: Check database credentials & remove any syntax errors.
. htaccess – Once renamed you can “refresh” this screen that you are about to click on and it should come up blank, you hit the save button since it will default back to WordPress rewriting itself to do this automatically.
These Could Solve Your Trouble with Wrong Setup.
🧩 3. To resolve issues with WordPress version compatibility
The incompatibility might also be a result of updating your WordPress or PHP. If you recently updated:
Try to deactivate all plugins and change to the default theme to see if there is a conflict.
See if the issue continues. If not, reactivate your plugins one by one until you find the cause.
This is a way of determining which plugin or theme is causing a fatal error.
🕵️ 4. Use error logging plugins
Trending your error logs yields the following insights:
Error Log Monitor: Show PHP errors on the Dashboard and send them via email.
Debug Log Manager: Now you can view the error log in real time without editing files.
Easy Error Log: For frontend widgets that allow for real-time debugging.
They aid in the identification and resolution of root problems.
By following these things step by step, you will be able to fix the fatal error and get your WordPress site back online.
🔧 Section 5: Plugin-Specific Fixes for Elementor & WooCommerce Critical Errors
Have you been plagued by the vomitous “This website has a critical error” message? You’re not alone. It’s a problem that has been plaguing a lot of WordPressers, myself included, and is associated with popular plugins like Elementor and WooCommerce. Here’s how to diagnose and solve these plugin-specific problems. (Support – Rank Math)
🧱 Elementor: How to Navigate through Critical Errors
How Elementor Causes Fatal Errors?
As strong as Elementor is, it can conflict with other styles or plugins and give you a fatal error. From my experience, it’s issues with older versions or add-ons. For instance, the dropping of the “Schemes” feature from Elementor 3.26 has caused a lot of headaches for users still currently dependent on that legacy feature.
Q: What are the steps to troubleshoot and resolve?
Deactivate Elementor manually: If you can’t open your dashboard, you can use FTP or file manager in your container to go to wp-content/plugins/ and then rename the element or folder to elementor-deactivated in your file directory. This will deactivate the plugin.
Try default theme times the problem can be the theme. Switch to a default WordPress theme (like TwentyTwenty-Four for testing).
Update Elementor (or reinstall it): If you’re not, try upgrading or reinstalling Elementor to the latest version. If you’re still having issues, try uninstalling and reinstalling this plugin. Don’t forget – your content is saved in the database and deleting and reinstalling the app is not going to remove your designs.
Check for add-on conflicts: Try disabling all of the Elementor add-ons and then re-enable them one by one to find the ones causing a conflict.
Boost PHP memory limit: It’s possible that Elementor may require more resources. The website does not have enough allocated php memory. Add define(‘WP_MEMORY_LIMIT’, ‘256M’); in your wp-config. php file. (WPML).
✨ WooCommerce: How to fix critical errors
Common Triggers
WooCommerce is a solid e-commerce solution, but clashes will happen, especially after you update it. In my case, I updated WooCommerce, and that caused a fatal error because of a conflict with the payment gateway plugin.
Troubleshooting Steps
Plugin Conflict Test Deactivate all of your plugins except for WooCommerce. If the issue is fixed, enable the plugins one by one, to look out at the issue giver.
Change Theme: If all else fails, try changing the theme temporarily to the default theme to eliminate any theme-specific problems.
Verify WooCommerce Logs: Browse your Dashboard to WooCommerce > Status > Logs. Check out the ‘Fatal-Errors’ log to find that issue.
Review Custom Code: If you inserted any custom code in the function. php file and ensure it complies with the newest version of WooCommerce.
Update Plugins and Themes: Ensure all of the plugins and themes used on the website have been updated to prevent any incompatibilities.
Critical bugs are scary, but they can be tackled one step at a time. Always have your plugins and your themes up to date, and think about creating a staging site where you can test all changes before deploying them on your live site.
If you have something to add to the story or a different problem to share, please drop a comment below. Let’s learn and grow together!
🛠️ Section 6: Hosting and PHP Issues – My Journey to Resolving WordPress Critical Errors
Ah, the dreaded “There has been a critical error on this website.” I remember when I first came across it — my whole site had disappeared in an instant. After a little digging I found outdated PHP versions and server configurations to be the usual suspects. Here’s a closer look at how I managed these problems, and how you can, too.
⚠️ The Risks of Using Old PHP Versions
Running an out-of-date PHP version, say 7.4 or lower, can cause compatibility issues with today’s advanced WordPress themes and plugins. I learned that lesson the hard way when my site went down after a plugin update. Luckily, after upgrading to PHP 8.1, the issue went away, though not without the bumps of a major upgrade. There were also some plugins that weren’t compatible, which caused additional errors. You need to make sure that all elements of your site are compatible with the PHP version to which you are updating.
🔄 How to Switch PHP Version in cPanel
Here is the process I went through to update my PHP version:
Log in to the cPanel: Log in to the cPanel dashboard of your hosting account.
Go to MultiPHP Manager: Click on “MultiPHP Manager” from the “Software” section.
Choose your domain: Select the domain that you’d like to make changes to.
Select PHP Version: From the dropdown, choose the PHP version (eg PHP 8.1).
Step 3: Save Changes Click “Apply” to save the new settings.
After did the changes, I went to visit my site to make sure everything working well. You will have to test it out after these updates to make sure that you catch mistakes before it could get messy.
From time to time, these errors also appear when you have the newest PHP version “Allowed memory size exhausted” or “maximum execution time exceeded.” These errors mean that your site is toughing out more than the amount of resources that you are allowed to use.
To address this:
Access php. ini file, which you’ll usually find in your hosting account’s root directory.
Enhance Memory Limit: Insert/Change line memory_limit = 256M, to get more memory.
Increase Maximum Execution Time: Add or edit the line max_execution_time = 300 to give more time for scripts to execute.
If you cannot get php. ini file, you can make similar changes in your wp-config. php file by adding:
define('WP_MEMORY_LIMIT', '256M');
set_time_limit(300);
These changes helped me stabilize my site and prevent those pesky errors.
If you’re not sure how to deal with hosting and PHP issues, it can sound a bit intimidating, but there’s nothing to panic about: you can resolve critical errors and optimize your site’s capabilities in the process. Of course, it’s always advisable to keep your PHP version up to date and check your site components for compatibility. Increasing memory limits and execution times could also get your site the resources required to run efficiently.
Just don’t forget: maintenance and updating are important for a healthy WordPress site. Take charge of your hosting environment before an issue strikes, and manage your hosting environment proactively to keep your site running like a well-oiled machine.
Section 7: How to Prevent Critical Errors in the Future
I remember the first time I encountered the dreaded “This website has encountered a critical error” message. My heart sank. This happened immediately after I updated a plugin and didn’t have a backup of my blog. I learned from that to be proactive to avoid that type of thing.
🔄 Regular Backups: Your Safe Zone
Following that scare, I began to run UpdraftPlus, for fully automated daily backups. It’s easy to use and can store backups off-site, like on Google Drive. I also make manual backups before any big ones, Just to my on the safe side. Doing so allows me to revert my site in case of any problems.
🧪 Use a Staging Environment
Live site testing, it turns out, was one of those things where I learned my lesson late at night, the hard way. These days I use WP Staging to make a duplicate of my site for testing updates/new plugins. It’s a good way for me to see problems before they happen on the live site.
🔄 Update everything
Obsolete plugins and themes are among the usual suspects when it comes to critical errors. I maintain WordPress core, themes, and plugins up to date. I also make sure that all plugins are compatible with the most recent WordPress version prior to updating to prevent conflicts.
🧪 Pre-deployment testing
I test the updates on a stage environment before I push them to my live site. I do this to catch possible problems early. I also check error logs with plugins like WP Debugging so that I can catch and address issues sooner rather than later.
To prevent such mistakes from being there the first in your WordPress website, you need to do: regular backups, use a staging environment, update everything, and test the changes before they get life. These techniques have saved me countless headaches and kept my site stable.
But remember — it’s not just a matter of troubleshooting errors when they happen, but also of putting practices in place to avoid mistakes in the first place.
Section 8: When to Contact Support
Oh, the “This website has a critical error” error. I’ve been there — staring at that foreboding screen, heart pounding, wondering what happened. Over the years, I’ve learned that, though some issues can be fixed on your own, the most intelligent thing to do is ask for support. Let’s examine the when and how of that help that you really can be getting.
📞 When to Call Your Hosting Company
If you’ve taken some other basic troubleshooting steps such as disabling plugins or swapping themes, and the error continues to pop up, it’s time that you reach out to your hosting company. They can look at server logs and configurations that are outside the WordPress dashboard and can sometimes illuminate issues. For instance, I have seen a fatal error due to a mismatch of server-side PHP versions. My host’s help desk zeroed in on the problem right away and there was a fix available.
All reliable hosts always provide 24/7 support through live chat, phone, and email. Inquiry with details when you contact:
- Description of the problem.
- The following recent changes to your site
- Troubleshooting steps you’ve already taken
- This information can assist the support team in more quickly diagnosing and resolving the issue.
🧩 Interacting with Plugin and Theme Developers
Occasionally a critical error can be attributed to a plugin or a theme. In these situations, reaching out to the developer may be the best course of action. Many developers provide support on things like:
Support forums on WordPress. org
Contact forms on their official web pages
Dedicated support emails
Include the following in your message to the developer you will need:
- Exact error message
- Steps to reproduce the issue
- Your version of WordPress and any other information that could help us help you.
- Been super helpful for me to win arguments fast with anything paid for plugins or themes.
🚀 Thinking of Managed WordPress Hosting for Better Support
If you don’t want to deal with technical problems on a regular basis or prefer to concentrate on producing and sharing content more than maintenance, managed WordPress hosting might be a good option. Services like these take care of technical details such as updates, backups, and security so you get peace of mind.
Best Managed WordPress Hosting Companies:
Kinsta: Featuring speed and expert support.
WP Engine: Strong performance and the world’s best support.
SiteGround: With good customer support and uptime.
Migrating to a managed host has revolutionized my workflow as I can now concentrate on the content without being afraid of any technical mishap.
Dealing with a major error on your WordPress site can be a nightmare but knowing how and when to ask for help can make all the difference. Whether it is your hosting provider, a plugin developer, or a managed hosting service, give them a call. And remember, asking for help is not a sign of defeat but of concern.
If you nip these problems in the bud and make the most of the help channels at your disposal, you protect your website as a safe place for your community.
🔧 Section 9: Common FAQs About the “There Has Been a Critical Error on This Website” Message
If you’ve ever come across the dreaded “This website has encountered a critical error” message, you’re not alone. This mistake is so annoying especially when it appears without any email and it is really hard to pinpoint what caused it. Check out these common questions to help steer you in the right direction in solving this problem.
❓ Why did I not get a recovery email?
WordPress would generally send a recovery email to the admin address if there was a fatal error. But it doesn’t always work as it should, as there might not be this email at all:
Incorrect admin email – If your site’s admin email is set up incorrectly in the WordPress settings.
Email deliverability: Server configuration and spam filters can occasionally stop emails from being delivered to your inbox.
To resolve this you may want to try a SMTP plugin like WP Mail SMTP to increase your email deliverability. This way you will not miss any important Notifications in the future.
🔌 Can I resolve this error without FTP?
Sure. If you can’t log in to FTP, use your host’s file manager:
File Manager In Hosting cPanel Login to your hosting and go to file manager.
Disable Plugins: Navigate to the wp-content directory and simply rename the plugins folder to plugins_old. This disables all plugins.
Test Your Site: Reload your site to find out if the issue is still there.
If the website opens properly, then it is one of the plugins that is the culprit. Now, rename the folder to plugins again and re-activate your plugins one by one, until you find the one that triggered the error.
🐞 Is this a WordPress bug or is it just my site?
“Critical Error” is a generic warning that something didn’t work. Common causes:
Plugin Conflicts: Conflicting or out-of-date plugins can also lead to errors.
Theme Issues: This can occur due to a bad theme or if the theme has been recently updated.
Custom Code Errors – Errors in the custom code added to your site may be the reason.
To find the issue, turn on the WordPress debug, and go to wp-config. php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
This will create a debug. log file inside your wp-content directory which will have details about errors in order for you to pinpoint the issue.
🔒 Is this an error that puts my security at risk or is it an indication of a hack?
Although a “Critical Error” notice isn’t necessarily a sign of a hack, it does mean you should remain on guard:
Security Scans: Scan your site for malware with security plugins such as Wordfence or Sucuri.
Keep WordPress Up-to-Date: Update your WordPress core, themes, and plugins to protect against known vulnerabilities.
Back-Up Your Site: It pays to back your site up regularly to get it up and running quickly in case something goes wrong. (WPZOOM)
If you suspect that something dodgy is going on, get in touch with your host or a WordPress security consultant and they can check your site and clean any malware.
Just don’t forget that being confronted with a critical error can be distressing — however, following an organized approach to puzzle through the issue, and the help of the proper tools, you’ll get your site back in good working order.
✅ Conclusion: Don’t Panic—You’ve Got This!
When I first saw the “This website has a critical error” dreaded message, my heart dropped. I had updated a plugin and bam no access to my site. I wasn’t receiving any emails so I was super lost.
But here’s the good news: The majority of critical WordPress errors can be resolved, often in just a few steps. Whether it was a bad plugin, a theme that broke it, or a PHP memory error, there’s a fix.
Here’s a quick summary:
Find the culprit: Deactivate any recent plugins or themes you’ve installed or updated. You can do it either via FTP or your hosting control panel by renaming the plugin folder.
Turn on debugging: Modify your wp-config. php file to enable WP_DEBUG. This will help you determine exactly what the problem is.
Check PHP Memory Limits: Occasionally, adding PHP memory limit to your wp-config. php file can fix the error.
Reupload core files: If the core WordPress files are the culprit, you can download a fresh copy of WordPress. org by default, then uploaded the core files, excluding wp-content and wp-config. php) can help.
Ask for help: With certain plugins such as WooCommerce or Elementor, their support forums are a gold mine. For instance, Elementor support does tend to fix such problems.
Your turn:
Did you get a fatal error just now? How did it get resolved? Tell us in the comments. If you are still having problems, then write your situation in a comment and I will help you.
More to read:
How to Resolve “There Has Been a Critical Error on Your Website” Error
Advice WordPress Critical Error: How to Login With No Email
How to Fix the Critical Error on Your WordPress Website (Step by Step)
Always know that there is a resolution to every problem. Your website will be live in no time and with patience, and the right mindset. You’ve found it!