3.01 Auto Upgrade Error

  • I’m having this error on about half of my sites

    Could not copy file.: /public_html/wp-admin/css/theme-editor.dev.css

    Installation Failed

    Beyond the manual upgrade, is there anything else I can do? I only ask because these are sites that the automatic upgrade worked before, so I’m just worried the automatic upgrade isn’t going to work again. I know I’m not the only one with this issue, so I’m not sure if its a server setting or something else.

Viewing 8 replies - 1 through 8 (of 8 total)

  • I get this error too. I run 7 or 8 WP sites. Tried 2 so far and get this error on both when doing the auto upgrade.

    Could not copy file.: /…/…/wp-admin/css/theme-editor.dev.css

    Never had a previous auto upgrade fail in WP ever! ??

    Thread Starter colleenharr

    (@colleenharr)

    *bump*

    Anything? Is the automatic upgrade just pretty much toast now?

    Have the same issue on all sites on my server. (Even tried fresh WP installation)
    On first update receive:

    Downloading update from https://www.ads-software.com/wordpress-3.0.1.zip…
    Unpacking the update…
    Verifying the unpacked files…
    Installing the latest version…
    Could not copy file.: /public_html/wp-admin/css/theme-editor.dev.css
    Installation Failed

    Anytime I update after that receive:

    Downloading update from https://www.ads-software.com/wordpress-3.0.1.zip…
    Unpacking the update…
    Could not create file.: /public_html/
    Installation Failed

    Repaired this by removing
    /webroot/.maintenance
    /webroot/wp-content/upgrade (complete directory)

    I have checked the modified dates on all the wordpress core components after running the update and files are being updated until the /public_html/wp-admin/css/theme-editor.dev.css file

    Checked the ftp logs, no errors related to uploading files.
    The theme-editor.dev.css file exists in the temp directory from unpacking the update.
    I am able to manually copy the file from the temp directory to wp-admin/css/ with no errors.

    I am out of ideas on this one….

    If it helps at all I am running CentOS installed with CPanel at PHP version 5.2.8.

    Has ANYBODY figured this out yet??

    I’m having the same issue too. I’m really surprised there hasn’t been an answer from WP developers.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Sadly, the answer is that it’s not always a reliably reproducible error. I can cause it to happen on my server by increasing server load over php at the same time I run any upgrade (core or plugin). Some people have fixed it with a reinstall of php, others had permissions changed. It seems to be something to do with how the FTP over php runs, and permissions and server usge at the time of upgrade :/ WordPress is getting bigger, and not all hosts are keeping up I suspect.

    So the best solution is to manually upgrade. It’s the official solution and always has been for when the automatic one fails.

    I’ve only had the auto upgrade work once. I’ve gotten to the point where I wonder why the auto upgrade is still part of the software package. To me it seems nothing but a big dud.

    The manual upgrade with FTP is not tough. Basically, you are dumping the new files right in where the old ones are and telling it to use the new ones instead of the old files. Turn off your plugins, don’t delete them just deactivate them. After the new WP is loaded you can reactivate your plugins, they will be in the ‘recently active’ section.

    If you have tried the auto upgrade once and had it fail use FTP and find wp-content/ upgrade. Get rid of all the failed files in there. Those will block a new try at the upgrade. Just delete anything in the upgrade file.

    Here is what you need for the manual upgrade. Copy all the new files over the old ones, except for wp-content which has your themes and plugins.

    I’m not a WP developer but I’ve done this enough times to know it works.

    John Ford

    (@aldenta)

    There’s a patch (https://core.trac.www.ads-software.com/ticket/10913) for WordPress that should go into 3.2 and help fix this upgrade error for most people running into it. It only seems to happen with servers running Pure-FTPd (and usually cPanel). In the meantime, there’s a plugin that should help fix updates for most people: https://www.ads-software.com/extend/plugins/ftp-upgrade-fix/

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘3.01 Auto Upgrade Error’ is closed to new replies.