monk@loosemonkey.net
Member
Posted 4 years ago #
I guess you got to love it! Trying to perform the automatic upgrade I get the following message and the upgrade fails.
Upgrade WordPress
Downloading update from http://wordpress.org/wordpress-2.7.1.zip
Unpacking the core update
Could not copy files
Installation Failed
Any ideas??
It's possible there's a permission issue with your host, and it's not allowing the 'unpacking' so you may have to follow the Upgrading WordPress instructions to upgrade to 2.7.1
monk@loosemonkey.net
Member
Posted 4 years ago #
Donnacha
Member
Posted 4 years ago #
I'm having the same problem - no problem upgrading plugins but no luck with the core, getting the same result as Monk.
And, yes, I the host too!
dswartze
Member
Posted 4 years ago #
I am getting same error at (2) different web hosters:
Downloading update from http://wordpress.org/wordpress-2.7.1.zip
Unpacking the core update
Fatal error: Cannot redeclare pclziputilpathreduction() (previously declared in /home/ccgreenv/public_html_youth/wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php:5421) in /home/ccgreenv/public_html_youth/wp-admin/includes/class-pclzip.php on line 5498
@dswartze - if upgrading from 2.7, disable the auto upgrade plugin and use the upgrader built-in to 2.7.
dswartze
Member
Posted 4 years ago #
@HandySolo --- thanks! that did it.
Donnacha
Member
Posted 4 years ago #
Just to be clear, I don't have the Auto Upgrade plugin installed and have de-activated the handful of plugins I do have.
Would it be possible for someone to list EXACTLY what permissions are required to enable automatic upgrades in 2.7?
Looking around online, it's fairly clear that a lot of people are having this problem, clearer instructions would help a lot of people and, more importantly, allow hosts such as myself to empower our users to do more with WordPress.
To those acting as their own host, look through http://codex.wordpress.org/Core_Update_Host_Compatibility to see if you can see something. Maybe upgrade your PHP.
Also review past info:
http://core.trac.wordpress.org/search?q=Unpacking+the+core+update
Donnacha
Member
Posted 4 years ago #
I have now deleted all my plugins and 777'd everything, but I keep getting this:
Downloading update from http://wordpress.org/wordpress-2.7.1.zip
Unpacking the core update
Could not copy files
Installation Failed
Donnacha
Member
Posted 4 years ago #
MichaelH, thanks for the suggestions but neither of those paths revealed a solution, I tried everything described, one by one.
I'm using the current version of PHP5, standard WHM/CPanel setup.
Server config discussions tend to take us a bit out of scope, but just for grins...
Are you running SElinux? If so, have you been checking your server logs?
Donnacha
Member
Posted 4 years ago #
I'm running CentOS, which is RHE rebadged and the most common distribution of Linux for CPanel.
One thing I've noticed from watching YouTube videos of the upgrade process is that some people, after press the automatic upgrade button, get the same login page that I do, asking for FTP details (hostname, user and password), whereas in this video the upgrade process starts as soon as the button is pressed:
http://www.youtube.com/watch?v=F2N0q7vwh0U
Is that how it is meant to be for everyone? Why do some of us have to enter the FTP details?
Donnacha
Member
Posted 4 years ago #
I have root access, I can change any permissions I want but I simply don't know what needs to be changed.
Does all this have something to do with WP being installed/owned by Apache or some other process that doesn't have FTP permissions?
CentOS has SElinux on by default, right? (or used to). Have you tried turning that off to see if anything changes?
If you are running your own webserver, then look into installing "suPHP" instead of the normal PHP modules. For RedHat compatible systems, it's usually as easy as "yum install suphp".
suPHP makes the PHP process run as the user who owns the PHP files, meaning that the script has the necessary permissions to update itself directly. No more FTP info required.
suPHP is pretty much the standard for shared hosting setups, as it ensures that somebody hacking into one website won't have sufficient permissions to hack into the other sites on that server through the same means (assuming everything is chmodded correctly, of course).
monk@loosemonkey.net
Member
Posted 4 years ago #
Has anyone figured out yet how to do this?
Also, I am looking at the list of Working Themes with no Issues from the Themes/Theme Compatability/2.7 page, http://codex.wordpress.org/Themes/Theme_Compatibility/2.7
My theme which is Aurora is not listed in this list. So, what exactly does this mean?
Your theme has nothing to do with the upgrade functionality.
Donnacha
Member
Posted 4 years ago #
Thanks HandySolo and Otto42, I greatly appreciate your help.
@HandySolo: SElinux is, indeed, in CentOS but is apparently has to be turned off when Cpanel is installed, so, it was already off.
@Otto42: The suPHP tip seems to have done the trick, excellent advice, cheers.
I am having same problem with two blogs, all versions 2.7 on two different servers. On one server the automatic upgrade stops after "unpacking". When checking "automatic upgrade" again, WP says "I have the latest version" (still being 2.7...). On the other server, some "fatal errors" popping up. Sorry but something here is WRONG. First time to happen. Unless there is correction, I simply won't upgrade. Any thoughts? All explanations and tips do not make sense. Messing around with those permissions is not for everybody and why suddenly now?
OK, found it. Actually thanks to HandySolo. Solution: deactivate the automatic upgrade, then there is still an "upgrade" under tools. All OK suddenly. Weird. Does it mean this plugin is now no more needed?
Victory too soon. On one server it's OK, on the other one:
Downloading update from http://wordpress.org/wordpress-2.7.1.zip
Unpacking the core update
Verifying the unpacked files
Installing the latest version
Could not copy file: /vservers/h8986wp/htdocs/wp-blog-header.php
Installation Failed
====
So... Sorry but all the tips above are either "Chinese" for me or look impossible to do...
Any "simple" advice?
Further to the previous entry: when I tried to set the file mentioned to 777 I get "SITE CHMOD command failed". The server I am using is not "as good" as the other one where the tip did work. Problem is, if I have to ask the service provider to change the setting to 777 which files should I request for them to do manually?
monk@loosemonkey.net
Member
Posted 4 years ago #
HandySolo
Where do I check to see if Auto Upgrade plugin is installed?
monk@loosemonkey.net
Member
Posted 4 years ago #
Otto42, My theme may have nothing to do with the upgrade. I didn't say that it did. I merely asked a question which I am asking again,
"I am looking at the list of Working Themes with no Issues from the Themes/Theme Compatability/2.7 page, http://codex.wordpress.org/Themes/Theme_Compatibility/2.7
My theme which is Aurora is not listed in this list. So, what exactly does this mean?"
Cheers
I think the problem is that the question doesn't make any sense. What do you mean by "what does this mean"?
Will the theme work? Probably. No way to tell.
Will the theme support the new 2.7 features? Probably not. No way to tell.
WordPress didn't create your theme. It has no control over it. And that page you linked to on the codex is not a comprehensive list by any means. So, your theme not being in there means nothing whatsoever.
@monk - log into your blog and check the Plugins page.
@bjprc - just to confirm: Yes, from 2.7 and up you don't want the "old" WP upgrader plugin anymore.
monk@loosemonkey.net
Member
Posted 4 years ago #
There are no plugins installed
monk@loosemonkey.net
Member
Posted 4 years ago #
Thanks Otto
I figured as the page was on wordpress.org that it would be comprehensive. My mistake.
I thought my question was clear. I was merely asking if installing the update would cause issues with my theme. Not quite sure how to make it any cleare.
However... question solved. As the auto update continues to fail, I manually updated to 2.7.1. It realy is quite easy (even though the comprehensive backup instructions are quite vague). And guess what?? The theme continues to work just fine.
Rock on!!!
Cheers
Thanks to HandySolo for the comment. I am however still at a loss what to do with the permissions. I am afraid manually updating to 2.7.1 will also bring up the permission problems on that one server. Now unable to change to 777 and not clear what exactly to ask the service provider to change - e.g. what files in which folder... Sorry for my ignorance... weird is, the exact same WP software on another service provider was updated without any problems after disabling the old plugin updater.
[moderated HandySolo now known as Chris_K]