undergroundbee.com/wp-admin/index.php is returning a 200 code for me.
It’s most likely something on your site or server that’s changed (corrupted file for some reason?). You can try this: undergroundbee.com/wp-login.php
That will bring up the login dialog, but may or may not let you in. If it appears to let you log in and then just goes to a blank screen, try undergroundbee.com/wp-admin/options.php from your address bar and see if that gives you dashboard access. The alternative is to take a look at your files using your ftp client and see if anything looks suspicious or has changed at all.
Hi. When I go to undergroundbee.com/wp-login.php, I do get the log-in dialogue, but then after that, it gives me a blank page.
And undergroundbee.com/wp-admin/options.php also gives me a blank page.
So I suppose that I may have a corrupt file or something like that, as you suggest, but I really have no idea where to look for the problem.
I did recently install WordPress version 3.5.1, so that may have something to do with this.
I would appreciate any suggestions. Thanks!
Hi. I changed my wp-config.php file to include the line “define(‘WP_DEBUG’, true);”
Now, when I try logging in to the admin page, I see these 2 error messages:
Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /var/www/un/underg15/public_html/wp-includes/functions.php on line 2925
Warning: Cannot modify header information – headers already sent by (output started at /var/www/un/underg15/public_html/wp-includes/category.php:176) in /var/www/un/underg15/public_html/wp-includes/pluggable.php on line 876
… But I’m not sure what to do to fix this problem. Line 2925 in that functions.php file is the following:
trigger_error( sprintf( __(‘%1$s was called with an argument that is deprecated since version %2$s with no alternative available.’), $function, $version ) );
…Line 876 in that pluggable.php is the following:
header(“Location: $location”, true, $status);
Should I replace these 2 files? Or change something in them?
This is assuming you have been making regular backups of your files and database, and you have valid backups stored locally before you proceed.
You might try using your ftp client to re-upload just the /wp-admin directory from a fresh download of 3.5.1 first, and see if that makes any difference. If that fails, a complete manual update might do the trick; but again, before doing anything, you should make sure that you have reliable database and file backups stored safely away, and don’t do anything you aren’t comfortable with. It’s also possible that your host may offer some support in the area of backup and restore as well – just as a last resort.
[edit] the manual update procedure might be an option on this one. Please read the instructions completely, and be mindful of your /wp-content directory and your wp-config file.
