Oddly, the update to 11.5 worked on two out of the three of my domains where Jetpack is installed. But the third one no dice. I’ll wait for the promised point release 11.5.1 tomorrow and if it still won’t update, I’ll re-install the entire plugin.
Thanks for the update and patience, @dhochman.
If the error you’re seeing on the third site mentions jetpack-waf, then the fix we will roll out with the 11.5.1 release should resolve it.
It turns out the “could not copy file” error also appeared when I tried to upgrade WordPress itself, and further research showed this error message is nearly always due to the domain running out of disk space for unzipping the upgrade files. Raising the disk space ceiling on this domain fixed the problem, and both the new version of WordPress and Jetpack 11.5.1 installed fine. Thank you!
-
This reply was modified 3 years, 5 months ago by
dhochman.
I’m glad that you got this sorted out.
I’m going to mark this thread as resolved. If you have additional questions about Jetpack in the future, feel free to open a new thread.