Support » Networking WordPress » White Screen on Primary Domain Admin and Front End

  • I screwed up my multi-site during the update to 3.6.1

    It has been working perfectly for over a year.

    Now I cannot get to the dashboard (or frontend) for the primary site (white screen, no debug info, view source just shows 5 blank lines).

    One of the weird things is that I can still get to both the admin screens and frontend of the subsites (but they don’t look quite right … like they missing plugin or child theme files.

    Since I can’t even get to the admin screen to do anything … where do I start to fix this?

    Here is my .htaccess file

    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).*) $1 [L]
    RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
    RewriteRule . index.php [L]

    and my wp-config.php file (password and salt removed)

     * The base configurations of the WordPress.
     * This file has the following configurations: MySQL settings, Table Prefix,
     * Secret Keys, WordPress Language, and ABSPATH. You can find more information
     * by visiting {@link Editing
     * wp-config.php} Codex page. You can get the MySQL settings from your web host.
     * This file is used by the wp-config.php creation script during the
     * installation. You don't have to use the web site, you can just copy this file
     * to "wp-config.php" and fill in the values.
     * @package WordPress
    // ** MySQL settings - You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define('DB_NAME', 'wpff');
    /** MySQL database username */
    define('DB_USER', 'wpff_user');
    /** MySQL database password */
    define('DB_PASSWORD', 'zzzzzzzzzzzzzzzzz');
    /** MySQL hostname */
    define('DB_HOST', 'localhost');
    /** Database Charset to use in creating database tables. */
    define('DB_CHARSET', 'utf8');
    /** The Database Collate type. Don't change this if in doubt. */
    define('DB_COLLATE', '');
     * Authentication Unique Keys and Salts.
     * Change these to different unique phrases!
     * You can generate these using the {@link secret-key service}
     * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
     * @since 2.6.0
    define('AUTH_KEY',         'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
    define('SECURE_AUTH_KEY',  'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
    define('LOGGED_IN_KEY',    'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
    define('NONCE_KEY',        'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
    define('AUTH_SALT',        'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
    define('SECURE_AUTH_SALT', 'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
    define('LOGGED_IN_SALT',   'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
    define('NONCE_SALT',       'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz');
     * WordPress Database Table prefix.
     * You can have multiple installations in one database if you give each a unique
     * prefix. Only numbers, letters, and underscores please!
    $table_prefix  = 'ff_';
     * WordPress Localized Language, defaults to English.
     * Change this to localize WordPress. A corresponding MO file for the chosen
     * language must be installed to wp-content/languages. For example, install
     * to wp-content/languages and set WPLANG to 'de_DE' to enable German
     * language support.
    define ('WPLANG', 'en_US');
    define ('FS_METHOD', 'direct');
     * For developers: WordPress debugging mode.
     * Change this to true to enable the display of notices during development.
     * It is strongly recommended that plugin and theme developers use WP_DEBUG
     * in their development environments.
     * This will log all errors notices and warnings to a file called debug.log in
     * wp-content only when WP_DEBUG is true. if Apache does not have write permission,
     * you may need to create the file first and set the appropriate permissions (i.e. use 666).
    define( 'WP_DEBUG', false );  // false or true
    if (WP_DEBUG) {
      define('WP_DEBUG_LOG', true);
      define('WP_DEBUG_DISPLAY', false);
    define( 'WP_DEBUG', true );  // false or true
    define('WP_DEBUG_DISPLAY', true); 
    define('WP_POST_REVISIONS', false); //false means turn off saving of revisions
    define('AUTOSAVE_INTERVAL', 86400 );  // seconds
    define('WP_ALLOW_MULTISITE', true);
    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', false );
    $base = '/';
    define( 'DOMAIN_CURRENT_SITE', '' );
    define( 'PATH_CURRENT_SITE', '/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );
    define( 'SUNRISE', 'on' );
    define( 'NOBLOGREDIRECT', '' ); 
    /* 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');
Viewing 2 replies - 1 through 2 (of 2 total)
  • My first step would be pulling plugins out of the plugins directory one at a time, especially ones activated on the main site and any mu-plugins. Then I’d ditch the active theme. This typically reveals to me what is causing the problem.

    I can’t imagine the WordPress update causing the actual problem (unless you have modified your installation), rather it is likely that your plugins or themes are incompatible somehow and THEY require some updates.

    Moderator Ipstenu (Mika Epstein)


    Lead Plugin Wrangler

    If possible, you should be able to swap to the default theme by editing wp_options.

    Change stylesheet and template to ‘twentytweleve’

    That’s easier than messing with plugins, most of the time.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘White Screen on Primary Domain Admin and Front End’ is closed to new replies.