Support » Fixing WordPress » Auto updated problems after upgrade 3.0.2 / 3.0.3

  • Hi,

    I am having problems after upgrading my 3.0 to a later version.

    I have several installs and can tell this issue comes from upgrading. Before upgrading, autoupdates on WP and plugins works fine. After upgrading WP, Autoupgrade no longers works. Not for WP and not for plugins.

    It says this now

    Downloading update from http://wordpress.org/wordpress-3.0.3.zip…
    Unpacking the update…
    Could not create directory.: /public_html
    Installation Failed

    Even when the upgrade did not work.

    Now I tried upgrading another 3.0 tot 3.0.3, it upgraded fine, after, not possible to autoupgrade plugins anymore

    I have one install that no longer autoupdated WP itself, it got stuck halfway upgrading and now non of the auto update options work. So also I can’t upgrade the 3.0 to a later version.

    I have never had this issue before, same serverspecs, same everything. So it must be some issue in the latest WP.

    Anybody knows how to fix this?

    manual updating sucks, I hope this gets fixed in new versions of beloved WP 🙂

    Cheers,
    Vincent

Viewing 15 replies - 1 through 15 (of 15 total)
  • Tried another install, same server other domain/website. running 3.0.1

    updated on the of plugins that were heighlighted to upgrade, did the automatic install. works fine.

    Then on to auto upgrade to 3.0.3 this gets stucks halfway and gives me this error

    Downloading update from http://wordpress.org/wordpress-3.0.3.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

    further trying to autoupgrade does not work.

    I don’t get it at all :'(

    Vincent

    Ok tried it on a 2.9.2 on another server.

    auto upgrading plugins works
    auto upgrading to 3.0.3 works
    auto upgrading plugin still works

    So that leaves: Server specs/ or the fact that I update a 3.0 or 3.0.1 to 3.0.3

    I am out of WP installs to test, if anyone has any tips #prettyplease

    🙂
    Vincent

    Hey I am pretty sure I have a fix for the Automatic Upgrade Problem.

    In your root folder edit your .htaccess file

    Open .htacess file up in notepad
    at the top, add this code-

    AddType x-mapp-php5 .php

    Then save and re-upload to your site.

    I use the 1&1 as a host.

    Now it works perfect.

    Hope this works.

    🙂 your friends at UtahSEO

    I change my .htaccess to this:

    AddType x-mapp-php5 .php
     AddHandler x-mapp-php5 .php
    
    # BEGIN WordPress
    
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    But that just brakes down the site completely?

    It gives me a 500 int.server error?

    Read about it, but doesn’t seem to fix the problem? Any advice?
    `
    This is the server, it is PHP5+ indeed:
    http://honda-supermagna.nl/phpinfo.php

    anyone any ideas? #prettyplease

    THIS IS EXACTLY WHAT I HAVE.

    COPY EXACTLY & OVERWRITE your .htaccess with the below code only

    AddType x-mapp-php5 .php

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    Let me know if that works.

    🙂 mg UtahSEO

    Thank you for your reply again 🙂

    now when I use that the site brakes down and the browser shows me this:

    <?php
    /**
     * Front to the WordPress application. This file doesn't do anything, but loads
     * wp-blog-header.php which does and tells WordPress to load the theme.
     *
     * @package WordPress
     */
    
    /**
     * Tells WordPress to load the WordPress theme and output it.
     *
     * @var bool
     */
    define('WP_USE_THEMES', true);
    
    /** Loads the WordPress Environment and Template */
    require('./wp-blog-header.php');
    ?>

    any ideas?

    Did you try upgrading automatically to 3.0.3 before you upgraded the plugins?

    I upgraded automatically to 3.0.3, and after that I upgraded Akismet. The Akismet upgrade was to make it compatible with 3.0.3, so I thought I should upgrade to 3.0.3 before I did anything else.

    I tried different options, I tested upgrading plugins before and after and somehow that did matter?

    still dont know how to fix this :'(

    Did you change the file permissions for folders public_html and wp_content without knowing???

    Check this article to find out about permissions specific to a WordPress installation…

    http://codex.wordpress.org/Changing_File_Permissions

    I didn’t change permissions. I wonder if the upgrade is doing this somehow? But I can hardly imagine I am the only one facing these issues with auto upload on 3.0.2 or 3.0.3?

    Would still appriciate some ninja’s input 🙂

    esmi

    (@esmi)

    Forum Moderator

    The upgrade won’t have changed folder permissions but your hosts may have.

    Have you tried turning all plugins off then try them one by one?

    This actually worked for me a couple of times.

    Google Analytics or Plugins by-Denis de Bernardy messed it up if I remember correctly.

    I agree with UtahSEO. Most of the time a stupid plugin is the culprit…

    I think this could be a problem with the 3.03 update, I do multiple installations on my own server weekly and never have problems, and with this new update, I cannot run any auto upgrades or updates to plugins, and I’m getting other issues as well.

    UtahSEO’s solution of adding the following line to .htaccess worked perfectly for me for upgrading from 3.0.1 to 3.0.3 and I’m using 1&1 as my host as well. Thanks!!

    AddType x-mapp-php5 .php

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Auto updated problems after upgrade 3.0.2 / 3.0.3’ is closed to new replies.