Critical Error
-
Hello dear Everyone,
Owno! My website gives the following sentence if you visit the url:
‘There has been a critical error on your website. Please check your site admin email inbox for instructions.’
But I do not know how to login because putting /wp-admin behind it does not work.
I never logged in, in a different way?
Help would be really appricated!Thank you SO much.The page I need help with: [log in to see the link]
-
Did you check your site’s admin email account? Did you find the email? If so, what does the email say?
Note that the above is about the EMAIL account used on your WordPress site. So you need to open your EMAIL to check, not WordPress.
Please check your mailbox (including your Spam folder). If you do not find the email, please report back so we can suggest alternative solutions. (Please really check your mailbox, as any other option we suggest is going to be 10x more difficult to do.)
Thank you George for your reply! I appreciate it.
I unfortunately did not find any email 🙁
Is there someone I can email to email it again?Oooh ! I found an email, but from my website url hoster: because from 31 Dec websites they will run on PHP 8.02 (something like that). I could put it back for just 2 days to PHP 7.04.
To make it ready to PHP 8.04, so do you have any advice to make my website save in two days before we go to 8.02, and I am able to login anymore 🙂To make it ready to PHP 8.04, so do you have any advice to make my website save in two days before we go to 8.02, and I am able to login anymore 🙂
WordPress itself works with PHP 8. It’s either your theme or one of the installed plugins that is not compatible and broke the site. You need to isolate the culprit!
For starters, now that you can access your dashboard, check to be sure every theme and plugin is up to date. For instance, you’re running version 1.1.1 of the Roseta theme, whereas the latest version is 1.3.0.
After updating your theme and ALL plugins, try the PHP 8 again and report back.
Standing by.
Thank you so much George. So it is not a problem that it says on ‘Site Health’ -> info -> server, that the Server is version PhP 7.4.33 ?
I updatend everything and I have to make it maybe more safe, while it says ‘not save website’. And no need to update anything else?
Sorry and, these are the critical errors:
1. A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.
But maybe because I switched back?
2. `The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.
When testing the REST API, an error was encountered:
REST API Endpoint: https://www.alissarees.com/wp-json/wp/v2/types/post?context=edit
REST API Response: (http_request_failed) cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received`What to do? <3
Please concentrate on solving one problem at a time.
If I understood what you wrote earlier, you have just 2 days to ensure your site works with PHP 8.0, as your host is going to force a PHP update. I think you should focus on this problem with a lingering deadline… before anything else.
So forget about Site Health errors and warnings for now. And let’s deal with the fatal error that broke your site completely.
I asked you to update your theme and all plugins, then switch your PHP version to 8, and report back. Did you do this? And what was the result?
You are totally right.Focus is key.
Okey so my theme was already updated (the brother and sister themes, as they say, are not but they are not active) Can I update them without activating them?.
And I updated all my plugins, but it still not run with 8.02 🙁
I get the same error sentence.
And I updated all my plugins, but it still not run with 8.02 🙁
I get the same error sentence.
OK, now we need to isolate exactly what’s causing the fatal error.
With the site still running under PHP 8, turn on WordPress debugging.
This will display additional information on screen, pointing to the root cause of the “critical error”.
Do this and report back the full error message you see. (Be sure you have PHP set to 8, so the “critical error” can be seen and reported.)
Standing by.
UPDATE: By the way, I don’t know what’s going on… but you said you’ve updated your theme and all plugins, yet I’m still seeing your site runs Roseta theme version 1.1.1, while the latest version is 1.3.0.
Yes thank you, yes sorry I am not very clear: that’s what I meant with brother and sister thema, it is not my activated main theme but WordPress recommend not to delete those like ‘Roseta’ while it is the brother theme. But I was ‘scared’ that I will activate the thema when updating.
So I dit it now, the theme update and still get the error.
I am now figuring out what you mean with turn on ‘WordPress debugging’. :
)Your
Codextheme is a child theme of theRosetatheme. That means Codex cannot be used alone: it depends on its parent Rosata theme, and Roseta needs to be present and updated all the time.I am now figuring out what you mean with turn on ‘WordPress debugging’. 🙂
I linked to the official support page that should give you step-by-step instructions.
Dear nice George,
A very late reply while I got stuck in the WordPress debugging. The combination of English and Codes got me dizzy. The good news is that I have until 31 January, the bad news is that I started to late and it is still in a couple of days (things came in between).One more question, there are different debugging plugins which one to download, I got confused.
I hope you are still there 🙂
AlissaI installed WP debugging. I got the following messages when I got online with 8.1 :
Fatal error: Array and string offset access syntax with curly braces is no longer supported in /home/public/sites/www.alissarees.com/wp-content/plugins/dropbox-backup/libs/wpadm.server.main.class.php on line 81 Notice: Function is_home was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_post_type_archive was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_front_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_home was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_singular was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_front_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_home was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_singular was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/public/sites/www.alissarees.com/wp-includes/functions.php on line 5835 There has been a critical error on this website.One more question, there are different debugging plugins which one to download, I got confused.
If you don’t know for sure which debugging plugin you need, then you probably don’t need one 😀
And, for now, you don’t really need a plugin. The basic thing to do is open your
wp-config.phpfile and ensure you have the following line:define( 'WP_DEBUG', true );This will “print” the details of the error on the screen, which will very likely point to the source of the problem (eg the specific plugin).
And this is all explained in the debugging link I provided earlier.
Oh, I saw that my last post is held for moderation. I think because I send all the errors in one post. But!
I managed to installe Wp debugging. I put on PHP 8.2, and it gave more errors like:‘Function is_home was called incorrectly and ‘ function is_front_page was called incorrectly.’
And many more, is this what we need to fix the problem? 🙂
- The topic ‘Critical Error’ is closed to new replies.