WordPress auto-install and upgrade

If your plugin update notifications aren’t showing up, then there’s two possible reasons.

Reason 1: Your server cannot contact api.www.ads-software.com in order to check for updates. This is the case on many servers that don’t allow arbitrary outside connections.

Reason 2: You are trying it too often or expecting too quick of a response. Plugin update checks only happen once every 12 hours, tops. Even if you change the version number, you’ll have to wait for your WordPress installation to check for updates again before it notices.

Note: Permissions have nothing whatsoever to do with this. The update checks and actually performing the updates themselves are two entirely separate things.

That was a nice image mrmist
Sadly, it seems to refer to an update for WordPress itself, rather than an update for a plugin. I say that because the advice seems to note “Comment Timeout” and has a 1 next to “Comments” – so I am assuming that was NOT a plugin named Comment Timeout. Forgive me if I’m wrong. ut! I suspect I AM wrong! You have a Plugin Called ‘Comment Timeout’ right?
Then there is the problem associated with the entire ‘view’.
If I click WordPress ‘Updates’ I get a scaly little message saying I am unclean ie. “no permission’ and I see NONE of your gracefully scripted window of auto and manual options, complete with version details etc.
We do not see an Update Advice Note coming up as a “Comments 1” either!
We only see the (1) next to Dashboard Updates, and farther down, next to Plugins.

What WE do is go farther down the Dashboard to the Plugins section and click on that, to see ALL our plugins and a note somewhat similar to the one in your image, telling us an update is available for a specific Plugin, which update and a link to the Plugin Site.

With this “wonderful one click” upgrade of WordPress, the Designers and Developers have removed a very simple facility that saved Bloggers in our position from having to manually, one by one, search the plugin site of every plugin, comparing the available version with the version installed so as to discover WHICH plugin has been updated.

We like that those who can use Auto-Update have this wonderful facility your image illustrates but we wish you had not removed the main functionality (for us) of the Plugin Manager. It used to be cool to pop in there and see which plugin had been updated.

“you do not have sufficient permissions to update plugins”
Code is Poetry – or Blank Verse, as the case may be.

Oh! And the reason we are discussing Plugins in the Auto-Update thread is because, due to the way this Forum operates, nobody was ineterested anywhere else, during the last couple of weeks. (since RC1)
Thank you all, for commenting here.
Poetry is Code, if you see what I mean.

For the record, I created a new User in the Dashboard, identical to the API registration, which anyway was correct, and find when I log in the situation remains the same. The new User has Admin rights in the WP Dashboard and we are really dealing with WordPress functionality, as someone pointed out, rather than DirectAdmin functionality.

My Host has never indicated that he sees his Server as related to this problem within the WP Dashboard and the associated plugins – although Plugins might be a misnomer as WordPress Automated Updates probably is still dead.

In anycase, when I click on Updates I still get the message about not having permission to update plugins. That seems to be a generic screen which I have also seen when attempting WP Auto-updates, not just Plugins.

We chatted about it here and find it hard to believe nobody else ‘in the World’ has this problem or a solution to it. One man in a thread that seems to have disappeared said, “Ditto” but nobody else commented in that forum thread so we have stuck with this one which at least seems responsive. No solutions dropped out though, yet.

I think I got this syntax right. Cut and paste is:
You do not have sufficient permissions to update plugins for this site.

Regardless of Firefox or IE – all same same.
I Deactivated ALL plugins and same response on clicking Updates.
Not the end of the world. We were just discussing options here.
Not as if we sit back and do nothing – but nothing changes the situation.

You do not have sufficient permissions to update plugins for this site.

A couple of thoughts:

1. Unfortunately, it could be your hosting provider. Due to various server configurations, some restrict this functionality. I have had the privilege of utilizing several shared hosting providers who do not, but also the displeasure of suffering through a few that do. A switch may be in order.

2. Try changing the permissions of /wp-content/ , /wp-content/plugins/ , and /wp-content/upgrade/ to 777.

3. Maybe your account lost full admin privileges? Access your database via phpMyAdmin (most hosting providers offer this in their control panel), go to the wp_users table and find the row for your user_login . Note the ID of this row. Now, go to the wp_usermeta table and find the wp_capabilities row for your user_id . Set the value of this row to a:1:{s:13:"administrator";b:1;}

Remember that WordPress only checks for plugin updates once every 12 hours, so if you don’t see any updates readily available, wait at least 12 hours.

As mentioned earlier, many of us see the plugins in need of updates identified clearly both in the Updates section (mrmist’s screenshot) and the Plugins section (I’ll take one the next time I see one available).

In the case of mrmist’s screenshot, the plugin “Comment Timeout” is clearly identified as being available for updating, followed by “You have version 2.0.1 installed. Update to 2.1.1.” As you can see, this both identifies the plugin to be updated and the version that it is to be updated too. I can assure you that the update notification in the Plugins section works no different than it did under 2.9.2.

Believe me, I wish that I could offer more than “It works for me,” screenshots for proof, and the occasional “Maybe try this” response, but that’s all that I have to offer. Because this functionality does work for me, exactly as it did under 2.9.2 (with the addition of the all-in-one Updates section), it’s hard to speculate as to what is causing your particular problem.

Indeed the plugin “comment timeout” was being shown as requiring an update. I cut that section from the Updates part of the screen, but you still (are supposed to) get the exact same message in the Plugins screen, just as always.

I suspect point (3) in the post above might be an important one in this case, there’s not many other reasons why your admin login would get a WordPress permissions error (as apposed to a server permissions error.)

The code (in update.php) that controls this message is

if ( 'update-selected' == $action ) {
		if ( ! current_user_can( 'update_plugins' ) )
			wp_die( __( 'You do not have sufficient permissions to update plugins for this site.' ) )

Which suggests that your admin user has lost that right from his role, which in turn suggests that at some point you’ve used a role-manager type plugin which has somehow screwed with your WP rights. Have you used any such plugins? It should be fixable with macmanx’s point(3) above, but it depends on the severity of the damage.

Ahh! these are hot points.
I’ll send Rinty and the 7th to investigate those exact suggestions.
Many thanks, guys.
I will return and report.

ggrrr

PhpAdmin shows all my admin Permissions are fine – which is just as they are under Users in the Dashboard.

I fiddled with the Folder permissions in the Domain, as I have in the past (this was also suggested by my Host) but that has no impact on the ‘permissions’ message above.
True, there is no wp or plugin update available right now but I would expect the Screen to come up, despite there being no updates to display.

I’ll try that again next time an update does show up but I have no real expectations of success.

About a year ago I dropped this in my Host’s lap and got no real response aside from that, if I chose, he could update WP for me. That was unsatisfactory because I can do it myself anyway (we all can here) but it would help if he would withdraw the cork he has inserted somewhere which interrupts the flow. That’s a solution that works well with good wine but I’m not up on Servers and I think I have in mind a different kind of Host!

I’ll email him the url for this thread. He will prolly go out in sympathy with you guys! lol

Raidie

This may very well be the solution that you’ve been looking for:

https://www.ads-software.com/support/topic/413565?replies=6#post-1565434

hmmm
I tried all that Macmanx and had no success.
(actually thought I reported back here too but my post is gone)

My Host says this problem has only affected selected clients from time to time so it’s not his Server. He seconded the suggestions in this thread and actually went in and verified I had all my internal settings correct.

While ‘looking’ at WP Settings I altered the url and crashed the Site. Have reverted to a Restore point on 18th June so the Angel has taken the Blog Post about WordPress 3.0 !!!!! “The Angel giveth and the Angel taketh away!”

I plan to look at it sometime today, as I get time.
Following options are to:
1 Delete all unnecessary parts of WP – keeping the Theme and certain files like wp-config etc which I will need to identify yet;
2 Reinstall WP 3.0 and see if there were any un-deleted files/folders from a previous installation causing a hangup in there.
3 If that fails (and it will require some time to do all that – takes 35 minutes to FTP WP from my HD to the Domain), then I will revert the site to WP 2.9.2 and gerrymander /includes/version.php just so the Dashboard doesn’t keep shouting at me there is a new version. (I did this in the past, for similar reasons, and can still test subsequent upgrades as they are released).
Anyway, the Post on the Blog is down, along with all the interesting comments, including some of our own!!!
We consider this defect still not-resolved.

I would certainly try the re-install route next. Make sure that you backup everything beforehand and let us know how it goes.

If you’ve been previously able to update plugins you should still be able to do that now.The availability of auto-update would depend on the security settings for your blog.In fact, you should still see the “update available” numbers next to both “Plugins” and “Update” (under Dashboard).

Was never able to Auto-Update in WordPress. Was used to doing so in Joomla and felt peeved it didn’t work here.
Before I found a good FTP platform I had to upload all the folders and files discretely using DirectAdmin – took two and a half hours!
Today I did delete completely the admin and includes folders and all the public files except Config. I downloaded the original files (files) from the public-html directory and ended up replacing the two Sitemap files associated with Google XML Sitemap.

With a completely new instal of WP and NO plugins activated, I still had “You do not have sufficient permissions to dada plugins”.

So now I am letting this run for a day. I have all the plugins (only 11 now) running as planned and I’ll wait to see if anything promulgates in the next day to change things.

In another thread I put in a FIX for fatal error with WordPress Stats. My FTP uploaded wp-includes/class-IXR.php with the ixr in lower case! That is something that needs to be watched.
I’ll have to check my FTP (FTP Clasic by NCH) and see if it’s set to convert all filenames to lowercase.
I am still stonkered on autoupdates though.
By Friday I will probably revert to 2.9.2 and slip the includes/versions file for 3.0 in to shut up the Updates Alert.

Over – and out to watch World Cup in 10 minutes at 4 am. Australia are playing someone. Serbia?

nite!

The answer to that business of lowercase was a Yes!
Our FTP was set to convert all filenames to lower case.
AND to replace spaces with underscores 0_0
So we’re unsure but not convinced this is the area of our problem.
Inability to AutoUpdate antedates the introduction of our FTP app.
Will probably set the ghost to replace all the wp-admin and wp-includes folders and files yet again – before reverting the site to WP 2.9.2
WP 3.0 makes very little difference to us as we run only the one dedicated Blog, so far at least. The only noticeable difference, from our perspective, is that updates have become more difficult to track.
Thanks Matt!
Not for the first time, days are being wasted here cumulatively, attempting to resolve a problem that apparently does not exist.

The fatal impact of that one Syntax error in WP Stats, pointing to: wp-includes/class-IXR.php, indicates it may be worth our while to refresh all those files and folders though, just in case.