The error message indicates a server-side error. This should be visible in the error log of your hosting. Have a look at it. The support of your hoster can help you if necessary.
Please enable the WordPress debug log. This will allow us to see if any PHP errors are being produced.
1. Edit wp-config.php and insert the following lines:
define( 'WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true);
define( 'WP_DEBUG_DISPLAY', false);
2. Reproduce the issue.
3. Locate the debug log in: /wp-content/debug.log
4. Paste the latest lines here. No need to paste the entire log file. Just 20 lines or so will do. Please censor any sensitive information.
https://codex.wordpress.org/Debugging_in_WordPress
Hi Ahammad,
Below see what was generated on screen when I just turned wp debug to true (I also did what you said later and it produced debug file which is the same as below). Note, I deleted my host and site name with xxxxxx below
Can you tell me what must I do now? Please assume I know very little about wordpress coding, when answering. Thanks a lot
Warning: require(/home/xxxxxxxxx/public_html/xxxxxxxxx.com/wp-includes/html-api/class-wp-html-attribute-token.php): failed to open stream: No such file or directory in /home/xxxxxxxxxx/public_html/xxxxxxxxxx.com/wp-settings.php on line 237
Fatal error: require(): Failed opening required ‘/home/xxxxxxxxxx/public_html/xxxxxxxxxx .com/wp-includes/html-api/class-wp-html-attribute-token.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in /home/xxxxxxxxxx/public_html/xxxxxxxxxx .com/wp-settings.php on line 237
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/xxxxxxxxxx/public_html/xxxxxxxxxx.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/xxxxxxxxxx/public_html/xxxxxxxxxx.com/wp-includes/functions.php on line 5835
There has been a critical error on this website
Apparently your installation is missing some files from the WordPress core. Therefore my advice would be the following:
Download from https://wordpress.org/download/releases/ the ZIP that matches your WordPress version. Unzip it locally and upload the unzipped wp-includes directory via FTP to your hosting. Thereby the files should be available again.
I went ahead and downloaded my sites wp version locally but even from the default version of my release (6.1.3) I do not see such directory and file
require(/home/xxxxxxxxx/public_html/xxxxxxxxx.com/wp-includes/html-api/class-wp-html-attribute-token.php
No I did not download the wrong package. I checked the wp version of my site from its backup, the version before I tried to upgrade to latest version. It was 6.1.3. And in 6.1.3 no such file., Or by saying “your wp version” you meant the version I am trying to upgrade to? Well obviously that would be the latest version. That confused me
You should use the package to the WordPress version that is currently installed on the hosting. If you tried to update to 6.2, it might have been saved incompletely, which is why this file is missing (and probably others). Go with the package for the 6.2 times as described.
Okay I checked the version in the public html folder (in other words my hosting) and checked the version.php file. and it still says 6.1.3. Regardless I uploaded the html-api folder and all its contents. And this time, instead of the 4 lines as I pasted above, the error log had hundreds of errors, Then I removed the html-api folder and refreshed the site but altghough the debug log was supposed to return to what I pasted above, it continues having hundreds of errors
And what are the error messages now? To me it still looks like the previous update to 6.2 went wrong. Otherwise no core component would know about this file.
Error messages are similar to before and ALL of them contain line 237. I paste one of them out of hundreds… See below
[01-Jun-2023 01:52:30 UTC] PHP Fatal error: require(): Failed opening required ‘/home/xxxxxxxxxxxx/public_html/xxxxxxxxxxxx .com/wp-includes/html-api/class-wp-html-attribute-token.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in /home/xxxxxxxxxxxx/public_html/xxxxxxxxxxxx .com/wp-settings.php on line 237
[01-Jun-2023 01:52:30 UTC] PHP Notice: Function is_embed was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. Please see <a href=”https://wordpress.org/support/article/debugging-in-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 3.1.0.) in /home/xxxxxxxxxxxx/public_html/xxxxxxxxxxxx .com/wp-includes/functions.php on line 5835
so this line 237 , i open wp-settings.php right under main folder, and look at line 237 and see something like
require ABSPATH . WPINC . ‘/html-api/class-wp-html-attribute-token.php’;
so what should I do now?
You clearly have files that are from 6.2, but some files from that version are missing. In line 237 of wp-settings.php the file html-api/class-wp-html-attribute-token.ph is included only since 6.2.
So my recommendation: upload the wp-includes from 6.2.2 and overwrite all existing files in wp-includes. If necessary you have to do the same for wp-admin.
I did what you told me and uploaded wp-includes and the site started working. Then I tried to login to admin cp and that still didn’t show up so this time I uploaded wp-admin folder and now that works too. Thanks very much !
Now in the admin cp it says : “An automated WordPress update has failed to complete – please attempt the update again now.” I should just ignore this message and this will disappear by itself later correct?
Also just for my learning… this means during a wordpress update nothing is done to database correct? Because we did not do anything to database in this exercise….
Yes, during a WordPress update there can be changes to the database. That’s where this warning message comes from.
To solve this go to Updates and click on the button to reinstall the current version. That should solve this I think. By clicking this button, an update to the current version is executed again without changing anything in the existing web.
honestly i dont want to install anything now until the next wordpress update, as i do not want problem again. may be when the next package comes this will disappear?
