WordPress Error 500 in Wp-Admin

allanc

Well-Known Member
Reaction score
387
Location
Toronto, Ontario, Canada
First, let me say that I am not very knowledgeable about Word Press or its technicalities.
I would appreciate help with the following WordPress issue:

The wp-admin of our web site seems to be broken whereas the site itself is fine.

A brief history is that the wp-admin was working OK until a couple of months ago.
When I logged into the wp-admin at that time there was a Word Press update available and I clicked on something similar to 'install automatically'.
The process started and then shortly afterward an error message popped up on the screen which I did not have a chance to record before it disappeared.
Now, when I try to log into the wp-admin (http://www.proven-solutions.com/wp-admin):
Firefox - redirects to the following with a white screen http://www.proven-solutions.com/wp-...//www.proven-solutions.com/wp-admin/&reauth=1
Internet Explorer: Does not redirect but implies that the site is under maintenance with a http 500 error
I have researched and tried the following which did not resolve the problem:
Renamed .htaccess
Renamed plugins directory
Renamed themes directory

Thank you in advance!
 
I would turn on error reporting and see if its throwing anything up.
Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3391

Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3510

Notice: get_bloginfo was called with an argument that is deprecated since version 2.2! The home option is deprecated for the family of bloginfo() functions. Use the url option instead. in /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php on line 3508

Warning: Cannot modify header information - headers already sent by (output started at /services/webpages/p/r/proven-solutions.com/public/wp-includes/functions.php:3391) in /services/webpages/p/r/proven-solutions.com/public/wp-includes/pluggable.php on line 1196

Can you please assist?
TIA.
 
Make a complete backup of your site and database. Install WordPress 2.8 maybe 2.2, put your files back in place and upload your database. You can then work on issues that cause your site to break when upgrading WordPress.

The other option is to just get a new theme, I would suggest a cherry framework responsive theme.

https://codex.wordpress.org/Moving_WordPress
 
Well before you go any further I'd suggest that you perform a full backup of your site. Files and database.

If you FTP into your server and delete your current theme folder, "busybee" and then upload the default wordpress theme. Your Wordpress install should default back to this.

Once you've done that then try and get back into the admin section. If you can get in then it will be something in your themes functions.php.
 
Make a complete backup of your site and database. Install WordPress 2.8 maybe 2.2, put your files back in place and upload your database. You can then work on issues that cause your site to break when upgrading WordPress.

The other option is to just get a new theme, I would suggest a cherry framework responsive theme.

https://codex.wordpress.org/Moving_WordPress
Hmmm.
Since I am not very familiar with WordPress I really don't know if you are serious about the 'other option' or if you have a hidden smiley in there?
 
Hmmm.
Since I am not very familiar with WordPress I really don't know if you are serious about the 'other option' or if you have a hidden smiley in there?
No smiley lol, I just went though this with an old theme that I had purchased that didn't play well with newer WordPress installations. I ended up paying a guy to upgrade my theme and make it responsive instead of a new theme because I liked they way I had it already.
 
Maybe you had plugins set to auto update. Ftp in and check their dates for the directories. Rename the newest folder plugin, retry login. Something similar happened to me, so that's what I did. Then I uninstalled the offending plugin, and used something similar.
 
I agree with Layoric- looks like you have a plugin causing this error. I had a similar issue a while back. I have to revert to a backup but one trick i learnt was you can go to the plugins folder via FTP and rename the suspected plugin-folder to another name which will cause it to not work and deactivate it.

Is there any plugins called wp_register_sidebar_widget() - id start renaming that one.
 
FYI. Wordpress had an update a day or so ago and most sites are set to autoupdate. So its likely something isnt compatible with the new version.
 
Back
Top