Unable to Update from 2.3 to 2.3.1

This seems to be a common error with WordPress. You can read more about it here:
https://www.ads-software.com/support/topic/http-error-could-not-open-handle-for-fopen?replies=7

If this solution doesn’t work, could you try to install the plugin manually, as explained here;:
https://codex.www.ads-software.com/Managing_Plugins#Manual_Plugin_Installation

Let me know if it helps.

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 https://downloads.www.ads-software.com/plugin/jetpack.2.3.1.zip…
Download failed. Could not open handle for fopen() to /tmp/jetpack.tmp
========

Could you let me know the name of your host? That’s the first time I receive a report about this error message when updating Jetpack, but I’ll make sure to follow up if we receive other reports!

The host is MDDHosting (https://www.mddhosting.com/) and the contact there is Michael Denney.

He replied that I was not the first to bring the error to his attention.

Also please note previous Jetpack updates (like the update to 2.3, for instance) applied without error on this host. And, during this round of updates, others succeeded where the Jetpack 2.3.1 update
failed.

Although I manually updated Jetpack on the site that I originally began posting about, 7 other sites (as reported by InfiniteWP) failed to update Jetpack, although other updates in the batch completed successfully. I applied the fix Michael provided for the config.wp file, and every one of the 7 was then able to apply the Jetpack update. And btw, although I typically use IWP to receive alerts to available updates and apply them, the site where I first discovered the problem was being updated through the WP Dashboard because I was already in there doing other things and noticed the available updates. It was later shown to fail on the 7 other sites while IWP was running the updates as a batch. Point being, the fix worked, and IWP does not factor into the equation, other than the fact that it reported the error just as native WordPress did.

Thanks for passing this on to the Jetpack development team.

Since you’re in contact with him, could you ask Michael to let us know if this happens again, by contacting us here:
https://jetpack.me/contact-support/

Jetpack is a large plugin, partly because it includes a lot of language files that make it larger than most plugins. The size of the plugin folder might be what’s causing the issue here.

Thanks!

Jeremy –

I have passed along your request.