I just spent the last couple of hours trying to work out why the admin section of my site wasn’t being displayed after login. I tried many things including overwriting the admin section with a clean version, installing Wordpress from scratch and exporting the old database into the new one, as well as copying the wp-content directory from old to new.

None of what i tried worked. The page remained blank upon loading. All that was being displayed in the admin section was the title and when i viewed the source code only the start of the page up to a point was being loaded. I then located the file that was being loaded and realised that the point that it was being loaded to was do_action(’admin_head’);.

I proceeded to comment this out to see what would happen and what do you know, the admin section worked. Even more curious was the fact that now that i had disabled this section of the code the wp version check plugin was no longer being displayed due to being loaded with the do_action(’admin_head’).

After discovering this i disabled the plugin and uncommented the do_action(’admin_head’) section. Again the admin section loaded.

This was extremely strange as i had made no changes since this last worked. I decided to take a look at the plugin’s website which wasn’t loading. I then took a look in the plugin’s file and saw that it was loading the update information from the site which appeared to be down.

So when the plugin was being loaded with the admin_head it was unable to connect to the server it was retrieving the information from which was halting the remaining loading of the admin page.

It was a real pain in the ass to discover something so small, which could have been avoided by timing out the plugin script and continuing to load the remainder of the page. Anyway it’s fixed up now, anyone else using the plugin may experience the same problems of the admin page not loading after login. If so just comment out the do_action(’admin_head’); section of the admin_header.php file so you can access the plugins section to disable the plugin for the time being.

Update
The site that the plugin was using for update information is back online now so the plugin can be re-activated.

4 Comments for “Plugin Issues

westi on October 10, 2006 at 4:45 pm

Sorry the site went down. I had server issues with a backup script that went haywire in the middle of the night. I found out after I had left for work and couldn’t get in to fix it until I came home 9 hours later :-(.

I wonder what version of the plugin you are using as I updated it in v1.00 to have a timeout on the XML-RPC call to ensure that at times like this is shouldn’t block out your admin page access.

mick on October 10, 2006 at 5:10 pm

It’s all good, these things can happen.

I’m using version 2.0.4 and keep up to date thanks to your plugin. ;)
In regards to the timeout i meant more so as a feature of Wordpress, if it timed out scripts that weren’t going to load. Instead of persisting in loading it to a null affect.

Either way it’s back working now so i’m as happy as can be. Cheers. :)

westu on October 10, 2006 at 5:41 pm

I’m using version 2.0.4 and keep up to date thanks to your plugin.

I meant what version of the plugin.

In regards to the timeout i meant more so as a feature of Wordpress, if it timed out scripts that weren’t going to load. Instead of persisting in loading it to a null affect.

That not something that WordPress can do really. The way in which the plugin system works does not give it any way to detect that a plugin is causing this kind of problem.

The timeout that I introduced on the request to the XML-RPC service should ensure this issue doesn’t happen again if you upgrade to v1.00 of the Version Check Plugin.

mick on October 10, 2006 at 6:28 pm

That’s unfortunate that the WordPress plugin system doesn’t work in the way that it could have prevented this issue.

I have been using version 1.00 of your plugin for some time now. The problem still occurred even with the latest version.


Trackbacks


Leave a comment


(required)


(required) (will not be published)