3.01 update fails

  • I tried the automatic update to 3.01 but it failed giving following strange errors that I never got ever:
    ————————————————-
    Warning: copy(/home/user123/public_html/wp-includes/images/smilies/icon_redface.gif) [function.copy]: failed to open stream: Permission denied in /home/user123/public_html/wp-admin/includes/class-wp-filesystem-direct.php on line 200

    Warning: copy(/home/user123/public_html/wp-includes/images/smilies/icon_redface.gif) [function.copy]: failed to open stream: Permission denied in /home/user123/public_html/wp-admin/includes/class-wp-filesystem-direct.php on line 200
    Could not copy file.: /home/user123/public_html/wp-includes/images/smilies/icon_redface.gif

    Installation Failed
    ——————————————-
    Can someone help how to update to wordpress 3.01 under this scenario?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I’d do it manually, since it looks like you have some permissions issues colliding with the php run upgrader.

    I ran automatic updates on all my wordpress-mu sites residing on my VPS from 3.0 to 3.0.1 without a hitch.

    However, on my plain WordPress sites on a c-panel setup, I ran into this problem only it wasn’t icon_redface.gif that appeared in the error message. It was something else.

    I noticed some people had problems doing the manual update, and I posted something to that other page which makes me hate to post something like it here, but since it will probably help someone, here’s what I did to have good luck with my manual upgrades:

    I didn’t remove everything. I kept wp-config and the wp-content and images directories. This is probably obvious to anyone who works with the internals of WP all the time, but I’m sure many people have probably blown away those files and directories thinking they were supposed to delete “everything” first. Or they could have backups…

    I think copied everything from the 3.0.1 distribution back into the websites directory. Everything, that is, except wp-content, images, and the wp-config file (which isn’t there when you unpack the new installation anyway)

    I then ran the upgrade.php as the readme file says to do, and voila. Of course, if you’re running WordPress as WPMU, you’ll probably need to press the update button to update all the blogs.

    And just to feel good and consistent, I cleared my caches (Super Cache, or W3 Total Cache, or whatever).

    ——————
    All in all, I’ve had great luck with the automatic and manual upgrades. I think my problem that caused me to have to do the manual upgrades on the C-panel system is that I’m dealing with two different user-ids: one for the C-panel login, and one that that apache runs as.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    There’s more than just cPanel differences between VPS and Shared Hosting. Like I said, there’s very likely some weird permissions things going on, and since there are a nigh unlimited number of ways you might possibly set up your server, it’s impossible to catch ’em all :/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘3.01 update fails’ is closed to new replies.