• Resolved ColinD

    (@colind)


    We have a MS install that can’t seem to update from 3.2.1. The upgrade process works fine. The network update reports no errors. The site is configured for subdirectories. After updates all the content for the root site “/” works as expected. (www.example.com/about-us, etc.)

    All sub-sites return a white screen. If I enable PHP error reporting via .htaccess I don’t get anything. If I turn on debug in wp-config I get “Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in ~/public_html/wp-includes/wp-db.php on line 1142”

    I have removed all plugins and themes.

    Here’s the .htaccess:

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    # uploaded files
    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    Here’s the wp-config (where I suspect my error is):

    <?php
    // ** MySQL settings - You can get this info from your web host ** //
    // **there are valid db settings here... **//
    /**#@+
     * Authentication Unique Keys and Salts.
    // **there are valid keys and salts here **//
    /**#@-*/
    
    /**
     * WordPress Database Table prefix.*/
    $table_prefix = 'stage_';
    
    /**
     * WordPress Localized Language, defaults to English.
    */
    define('WPLANG', '');
    
    /**
     * For developers: WordPress debugging mode.
     */
    define('WP_DEBUG', true);
    
    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', false );
    $base = '/';
    //define( 'DOMAIN_CURRENT_SITE', 'example.com' );
    define( 'PATH_CURRENT_SITE', '/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );
    //define('WP_DEFAULT_THEME', 'example');
    
    define('ALTERNATE_WP_CRON', true);
    
    define('ADMIN_COOKIE_PATH', '/');
    define('COOKIE_DOMAIN', '');
    define('COOKIEPATH', '');
    define('SITECOOKIEPATH', '');
    
    /* That's all, stop editing! Happy blogging. */
    
    /** Absolute path to the WordPress directory. */
    if ( !defined('ABSPATH') )
    	define('ABSPATH', dirname(__FILE__) . '/');
    
    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . 'wp-settings.php');

    Any suggestions would be greatly appreciated.

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

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    When you removed all themes, did you switch to Twenty Twelve or Twenty Thirteen?

    Thread Starter ColinD

    (@colind)

    Twenty Thirteen

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    All sub-sites return a white screen.

    For ALL the subsites too? I mean, did you remember to change their themes? You may have to do it in the DB.

    Thread Starter ColinD

    (@colind)

    I’ll try that and report back. However, the reason I have all the plugins and themes removed is because all (yes all 24) where giving me a white screen initially. And its not a typical WSOD; I can’t get any decent debug info about where this is failing even when I enable php error and log to a file. Enabling the WP_DEBUG flag isn’t helpful either.

    But really appreciate your help. Thanks.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    Sure. 🙂 WordPress is funny. If you delete a theme it SHOULD fall back to the default, but sometimes it doesn’t so you have to force change it in the DB.

    (I do a lot of ‘hacked sites’ work and that one comes up a lot)

    Thread Starter ColinD

    (@colind)

    Awesome! So I edited blog 2’s option and all the sub-sites started working (which doesn’t make any sense…) My theme is a child of the WooTheme Simplicity so I enabled that and everything seemed AOK. Then I enabled my custom theme and I get no data received. But that seems like a problem I can troubleshoot on my own. Thanks Mika!

    Thread Starter ColinD

    (@colind)

    Actually, maybe I’ll ask, since perhaps you know: My custom child theme works on blog 1 (/) but I get the ‘no data received’ on the child sites. I am grabbing a menu and so forth from blog one as the primary nav of the theme. So that’s seems like the first candidate. Any other ideas?

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

The topic ‘Problem after updating from 3.2.1’ is closed to new replies.