Hey! I’m not the only person on the planet that had this issue this year.
My fix was to have the hosting company empty the ./tmp/ directory. For some reason that they couldn’t explain, none of the updates were being deleted after the install was complete.
It may take awhile to get some hosting companies (I’m talking to you GoDaddy) to understand that you the user can’t clean out the directory that is having the issue.
Good Luck!
I agree with cderrington. This does sound like a server/hosting issue to me too. Try contacting your hosts about it and sending them a full copy of the error message.
Other auto updates are proceeding and completing normally. I have full access to the tmp directory and can even change it’s permissions. I set them to 777 and that did not help either. There are no remnants of other WordPress updates in the folder. Since JetPack is the only update failing, my web host’s position would be clear – contact Jetpack support.
Any other suggestions?
Sorry – not unless you update the plugin manually using FTP. It’s a hosting issue – not a plugin one (or even a WordPress one).
And you have this direct from the developer?
I have received a response from the hosting company – one of the most helpful and professional hosts I have ever had the pleasure of working with. Based on their response, I am not at all of a mind to believe it has anything to do with their platform. Rather, I believe there is an issue with the plugin and the developers need to investigate the matter further.
To aid any who are having this issue, this is the reply I received from my hosting company (it’s actually from their knowledgebase):
——–
Cannot upgrade WordPress or a WordPress Plugin
Should you receive an error message about not being able to write or open a file in “/tmp” when upgrading WordPress or a WordPress plugin, please add this line to the bottom of your “wp-config.php” file:
define(‘WP_TEMP_DIR’,ABSPATH.’wp-content/uploads/’);
This line will result in WordPress using your “/wp-content/uploads” folder to store temporary files required during the upgrade process instead of the system-wide /tmp folder. We have only seen this issue reported for the “Jetpack” plugin, however, this issue may affect other plugins.
An example error message that this line will resolve:
========
Installing Plugin: Jetpack by WordPress.com 2.3.1
Downloading install package from http://downloads.wp.xz.cn/plugin/jetpack.2.3.1.zip…
Download failed. Could not open handle for fopen() to /tmp/jetpack.tmp
========
You can post JetPack support requests on the JP forum here:
http://ww.wp.xz.cn/support/plugin/jetpack
(Scroll down to make a new post there)
EDIT- looks like you already posted there several hours ago – so this is now a duplicate thread – CLOSED.
