Posted 2 months ago #
Hi there
I've upgraded to 2.8.4.
If there are any plugins in the plugin folder the plugin page will not show. This includes the standard plugins that ship with WP.
I delete those standard plugins and when the folder is empty I am able to access the plugins page.
I have reloaded 'fresh' versions and renamed my content folder so I don't think it's any exisiting plugins that are causing the problem.
Posted 2 months ago #
Anyone out there with a solution? Anyone want to help? Please!
Is this part of a wider installation problem or something specific?
Posted 2 months ago #
Humor me for a minute. What's your blog URL?
If there are any plugins in the plugin folder the plugin page will not show.
When you go to http://your-blog-url.com/wp-admin/plugins.php what does your browser display? Any error messages?
Also check your file permissions for your plugins folder. If your webserver can't read the contents of the plugins folder, you won't get any plugins listed.
Posted 2 months ago #
Thanks for your reply!
With the debug mode active I get this message:
Warning: fopen(http://api.wordpress.org/plugins/update-check/1.0/) [function.fopen]: failed to open stream: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. in F:\mywebsite\wp-includes\http.php on line 984
Fatal error: Maximum execution time of 30 seconds exceeded in F:\mywebsite\wp-includes\http.php on line 984
Fatal error: Maximum execution time of 30 seconds exceeded in F:\mywebsite\wp-includes\wp-db.php on line 383
Before I didn't have to set any special permissions for the plugins folder - has this changed in 2.8.4? What permissions do I need to set for the plugins folder? I don't have direct access in this case unfortunately.
Posted 2 months ago #
That helps and looks like the problem is with your blog contacting http://api.wordpress.org/plugins/update-check/1.0/
There is a disable plugin update plugin but you can't actually get there to install plugins...
Try doing this: backup your wordpress files and then re-name the wp-content/plugins to wp-content/plugins-old. Then create a new wp-content/plugins directory.
I want to see if having no plugins will stop the update check. If that works and you can get to your plugins page (which should be empty), is if you can then install http://wordpress.org/extend/plugins/disable-wordpress-plugin-updates/
Posted 2 months ago #
hi there
That didn't work unfortunately.
I'm actually getting the same error messages on my dashboard on the 'Incoming links', 'Plugins' etc
I've also tried to update a WP installations on a testing server and yep - it's the same errors. It would suggest to me that there is probably something permissions related going on here.
Have http.php and wp-db.php changed massively in recent versions? I wonder if because of permissions something is not being written correctly to the database.
deerfoot: No, the error message you gave is very clear. Your server is unable to access the plugins update check site, and so it times out before finishing. It has nothing to do with http.php or wp-db.php, those are simply the locations where the timeout is occurring. The first error is the important one.
The fact that you get the same error on incoming links and such means that your server is unable to make ANY outgoing http connections. Thus it's a server configuration issue. Perhaps you're firewalled or something?
Posted 2 months ago #
Thanks very much for the replies, much appreciated.
I'm surprised that it is the update that is causing problems but it it pretty clear that the problem is my end.
I will get in touch with the server guys- I don't like to bother them too much as it was an effort to get WP installed in the first place!
Understandably they are security focussed. I'll reply when I've had a response from them.
Posted 2 months ago #
Hi there
My sys admin came up with the goods by suggesting putting this into wp-config:
define('WP_HTTP_BLOCK_EXTERNAL', true);
Does this have any disadvantages? I guess it might affect some WP functions and plugins?
That doesn't exactly *fix* the problem, it just makes WordPress not try to contact external sites. It breaks all the update functionality, the external feeds, all ping support, etc, etc. Basically makes it so WordPress never, ever, tries to contact any other server, ever.
You must log in to post.
