lianpb
(@lianpb)
WCBRS 2019 Contributor
Hello caleb1,
In the first instance I would be check your PHP version and memory limit. Your PHP version needs to be PHP5.6 and higher. Previously when I was greeted with a blank screen i found the issue was memory related.
Try
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
in your wp-config.php file this will display an error for the memory limit if this is the issue.
If your question has been answered, we would love if you would mark this topic as resolved in the right hand sidebar. This helps our volunteers find the topics that still need attention.
-
This reply was modified 7 years ago by
lianpb.
wp_recovery_mode is defined in wp-includes/error-protection.php, so be sure that that file (and everything in wp-includes) is from 5.2 *and* that all PHP files in the root of your site are also 5.2 files.
Thread Starter
caleb1
(@caleb1)
I will try the memory checking thing.
How can I identify what my php version is?
All the PHP files in wp-includes is updated to v5.2
I tried updating the files in the root to 5.2 ones and when I did that I could not access the site at all so I had to restore my backup of the root folder files to get the site to work again.
Is there any way I can get a manual download of the *5.1* wordpress files so I can at least get my site and admin to work even if it means not updating?
Thread Starter
caleb1
(@caleb1)
Tried adding the lines of code @lianpb mentioned to the bottom of the wp-config.php in the root. Nothing changed I get no additional errors.
Also it’s not a completely blank screen. its the wordpress logo with a rectange and rest blank. Just no text. See picture at https://imgur.com/rQryoo4
At this point I am mostly interested in rolling back to 5.1.
-
This reply was modified 7 years ago by
caleb1.
-
This reply was modified 7 years ago by
caleb1.
Ignore the advice about the PHP version. It’s not relevant.
Do a manual update of WordPress: https://codex.ww.wp.xz.cn/Updating_WordPress#Manual_Update
You need to have file and database backups that can be restored when something goes wrong.
If you have backups before the disaster or to perform the manual installation correctly, read the following article https://codex.ww.wp.xz.cn/Updating_WordPress#Manual_Update
If you have not already made the backups proceed as this article https://codex.ww.wp.xz.cn/WordPress_Backups
furthermore after the backup I suggest you to repair all the wordpress database tables https://hosting.review/tips-tools/repair-wordpress-database/ do not do repetitions by setting something on your wp-config.php and make sure that if you have the define for home and site they have the right path, in your case the installation is in the blog folder.
For wordpress 5.2 you must have php 5.6.20 or later.
Some old wordpress installations were adapted by your host, if you did not enter wordpress in the blog folder it is time to ask for more information from your host and possibly if they have previous backups or they will tell you what would be the right way to update wordpress since they have optimized it.
sometimes through the phpinfo(); function you can see the php version, always if it applies the right version.
Thread Starter
caleb1
(@caleb1)
Thanks for getting back to me
I had no backups before this problem. I should have though.
I backupped the database and the site then followed the database repair procedures you linked.
I had the ‘The storage engine for the table doesn’t support repair’ errors on some tables so I tried the “alternitave method”
When I got to step 7 (Navigate to http://sitenamegoeshere.com/wp-admin/maint/repair.php, replacing ‘sitenamegoeshere.com’ with your site’s URL) I get a 404 error.
I confirmed I modified the wp-config.php correctly and I did.
Any ideas here?
Is there any way I can get the repair.php that it is trying to access to exist if it doesnt?
Thanks.
Did you do the manual update that I linked?
Thread Starter
caleb1
(@caleb1)
Ok doing the update based on those instructions fixed the problem. I thought I did that before but I might have missed something.
Everything works fine now. Thanks for your help everyone.