Does this happen with any other plug-ins?
I’m not even certain that there’s anything I *could* do which would cause an upgrade problem like this from within the plug-in; which suggests that this is a general problem with upgrading. However, if it only happens with this plug-in, then that’s…well, pretty strange, but possibly worth investigating.
Thread Starter
MomDad
(@momdad)
It has only happened with WP to Twitter. I’ve gone through a multitude of other plugin updates between the last time it happened and this time, and all those worked without a hitch. I can’t say with any certainty that it’s not a conflict with another plugin, but that in itself would be a bit strange too to have a conflict like that during the upgrade process.
Since I no longer have a copy of 2.4.6, I’ll manually edit the plugin version in the db and the plugin files and force it to prompt again for upgrade. I’ll enable logging and see what, if anything, it spits out this time during the process.
Definitely let me know. That’s a pretty odd occurrence – not one which has ever been reported to me. Please do send a support request via the built-in support form; that could be very useful to me.
Thread Starter
MomDad
(@momdad)
Ok, I’ve just gone through the process 3 times, each time manually editing the db and plugin files to mask it as 2.4.6 and prompt for upgrade to 2.4.7. Apache error logging with LogLevel set to “warn” catches nothing out of the ordinary during the upgrade process. In WP admin, the upgrade output is as follows:
Downloading update from http://downloads.wp.xz.cn/plugin/wp-to-twitter.zip…
Unpacking the update…
Installing the latest version…
Removing the old version of the plugin…
Could not remove the old plugin.
Plugin update failed.
Return to Plugins page
After each of the 3 run-throughs, the only file left in the directory is wp-to-twitter/js/jquery.charcount.js
Is it possible that the cleanup/removal routine of the old version is not actually removing the .js file and the js sub-dir as intended, and thus can’t delete the main wp-to-twitter plugin dir?
For certain privacy/anonymity reasons, I’d prefer not to submit a support request as-is, but I’ll gladly send you an anonymized copy of it if you can provide me with an email address to send it to.
Submit a contact through my website contact form: http://www.joedolson.com/contact.php. I’ll respond to you so you’ll have an email to send it to.
It looks to me like a server issue that’s only affecting WP to Twitter – specifically, that either the files or the directory that’s left behind is not getting deleted, which may be due to permissions issues. Check the file permissions on that directory and file and see if there’s an issue with them.
Thread Starter
MomDad
(@momdad)
Gosh, that’s embarrassing. My apologies for the false alarm, Joe — that was indeed the reason why.
Before upgrading to 2.4.5, I had moved the existing wp-to-twitter dir elsewhere as a backup, manually uploaded 2.4.5, and neglected to change its ownership.
Thanks for the rescue!
Glad to know it! Always happy to know that I don’t have to fix something. 🙂
