The MU forums have moved to WordPress.org

[closed] Upgrade to WPMU 2.8.2 failed (18 posts)

  1. TonyVitabile
    Member
    Posted 14 years ago #

    I saw the message about the new version of WPMU 2.8.2 on my admin screen tonight, so I decided to run the upgrade. It failed. Here are the messages

    Downloading update from http://mu.wordpress.org/wordpress-mu-2.8.2.zip.

    Unpacking the update.

    Warning: copy(/hermes/web03/b541/moo.hgmadmin/worship/wp-content/upgrade/wordpress-mu-2.8.2/wordpress/wp-admin/includes/update-core.php) [function.copy]: failed to open stream: No such file or directory in /hermes/web03/b541/moo.hgmadmin/worship/wp-admin/includes/class-wp-filesystem-direct.php on line 131
    Could not copy files.

    Needless to say I'm not going to try the upgrade again for a while.

    Tony

  2. Avazbek
    Member
    Posted 14 years ago #

    I got the same error.

  3. aberean
    Member
    Posted 14 years ago #

    I got the same error.

  4. andrea_r
    Moderator
    Posted 14 years ago #

    If the upgrade fails, you can always do it manually.

  5. danaldinho
    Member
    Posted 14 years ago #

    I got the same error :(

    To do it manually, where can we see which files to just upload or edit?

  6. LoganSix
    Member
    Posted 14 years ago #

    I usually just update the ones changed after a certain date.
    However, it would be nice to know which files to update, since the auto-update doesn't work.

  7. LoganSix
    Member
    Posted 14 years ago #

    I guess anything newer than July 10th has been updated.

  8. LoganSix
    Member
    Posted 14 years ago #

    wp-admin/includes/
    misc.php
    template.php
    comment.php
    mu.php

    wp-includes/
    version.php
    wpmu-functions.php
    rewrite.php
    default-widgets.php
    comment-template.php
    functions.php
    user.php

    blogroot/
    xmlrpc.php
    wp-settings.php
    wpmu-settings.php

  9. LoganSix
    Member
    Posted 14 years ago #

    wp-admin/
    options-permalink.php
    edit-form-comment.php
    comment.php
    plugins.php
    wpmu-users.php
    menu-header.php
    wpmu-blogs.php

  10. andrea_r
    Moderator
    Posted 14 years ago #

    You can always see the changes, and the files, in trac.

    http://trac.mu.wordpress.org

    Click the Browse button. :) If you do browse earlier versions, there's a zip link at the bottom of the page. You can also compare revisions and download just the changed files.

  11. upgrades
    Member
    Posted 14 years ago #

    What a nightmare, the auto failed to upgrade for me like Tony above had stated.

    So I attempted to do it manually, after backing up all the files, the database and uploading the 2.8.2

    Im at the point where it asks me to open up upgrade.php
    instead of upgrading it takes me to the install.php as if I was setting up a new blog. This is not what Im trying to do.

    Dont get me wrong, Im not complaining one bit, but the almost clock work upgrades to wordpress has me pulling my hair out. Its one thing to do a upgrade because of security, and this was the sole reason I was attempting it.

    I hoping now that after uploading my older files my site will be restored.

    As far as this exploit with xss is it possible to remove the the comments from the admin panel to avoid this? or is there more to it then just that?

    Looking for answers here. Ive read and read and find my self in loops of dont delete this folder but if you have customized these files then you need to do this. ahhhhhhhhh I tell ya I need a drink!

    Also once my site is back up and running, will the error Im getting to upgrade automatic be fixed? I was more able to upgrade that way then go back and edit the custom files I have changed.

    Its not a major lost here, mostly my own site which Ive been working on since day one and really the only thing I care about and a handfull of user blogs.

    really hoping my site will restore back to the way it was :|

    ~ fustrated and sick of upgrades

  12. Driftless1
    Member
    Posted 14 years ago #

    quick question --- I have uploaded all the files manually - and everything works fine.

    But how do I get rid of the update nag? Do I have to change the db? Cheers!

    EDIT: Nevermind, I missed the version.php file... D'oh!

  13. mcmc
    Member
    Posted 14 years ago #

    there was already a problem with the automatic update from wpmu 2.7.1 to 2.8.1, which got fixed fairly quickly. I copied over the corrected files and now it works.

    Now I wanted to update 2.8.1 to 2.8.2 and have the same problem from 2.8.1 to 2.8.2 as you guys do. What I really don't get is why these updates are not tested out before they are released?

    Don't get me wrong, I think WPMU is awesome and its cool that its free for everybody to use and all that, but I don't think I will be among the early updaters anymore, Ill rather wait until the bugs are fixed.

  14. Albertane
    Member
    Posted 14 years ago #

    In /wp-admin/includes/class-wp-upgrader.php

    Change:
    // Copy update-core.php from the new version into place.
    if ( !$wp_filesystem->copy($working_dir . '/wordpress/wp-admin/includes/update-core.php', $wp_dir . 'wp-admin/includes/update-core.php', true) ) {

    To:
    // Copy update-core.php from the new version into place.
    if ( !$wp_filesystem->copy($working_dir . '/wordpress-mu/wp-admin/includes/update-core.php', $wp_dir . 'wp-admin/includes/update-core.php', true) ) {

    Automatic upgrade should then work correctly.

  15. donncha
    Key Master
    Posted 14 years ago #

    *cough*thanks for the ticket*cough*

  16. tsalagi_red
    Member
    Posted 14 years ago #

    When I attempt to do an automatic upgrade from 2.8.1 to 2.8.2, I get as far as "Downloading update from http://mu.wordpress.org/wordpress-mu-2.8.2.zip." and the whole process stops. Changing the code above doesn't do a thing for me.

    @donncha -- Trac report http://trac.mu.wordpress.org/ticket/1037

  17. MAVIC
    Member
    Posted 14 years ago #

    Thanks much Albertane. Worked perfectly.

  18. jsaf
    Member
    Posted 14 years ago #

    @Albertane: Thanks man, your solution worked perfect for me.

    I only had to change /wordpress/ to /wordpress-mu/ on the above code.

About this Topic

  • Started 14 years ago by TonyVitabile
  • Latest reply from jsaf