• Resolved nikitarama

    (@nikitarama)


    I got the white screen of death after editing some PHP. I was trying to add php to pull in the date of a post in the YYYY-MM-DD format.

    I added some incorrect PHP and now I have the white screen. The rest of my website it fine because it doesn’t run off WordPress, only my blog. subdomain.

    I requested FTP access from my web host.

    I am pretty sure I was editing the content-single.php file from a child theme. and I know where the code that is wrong is.

    What do I do when I get FTP access?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator t-p

    (@t-p)

    Have you tried:
    – Flushing any caching plugins you might be running, as well as server and/or browser caches. Also, any op cache or content network cache, as well as Cloudflare, clear those caches.
    – deactivating ALL (yes all) plugins temporarily to see if this resolves the problem (plugin functions can interfere). If this works, re-activate them individually (one-by-one) to find the problematic plugin(s).
    – If you can’t get into your admin dashboard, try resetting the plugins folder by FTP. Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder (if you have created such folder). The easiest way is to rename that folder to mu-plugins-old.
    – switching to the unedited default Twenty Fifteen theme for a moment using the WP dashboard to rule out any theme-specific issue (theme functions can interfere like plugins). If you don’t have access to your admin area, use FTP , or your web-host’s cPanel or whatever file management application your host provides. Navigate to /wp-content/themes/ and switch to the default theme by renaming your current theme’s folder by adding “-old” to the end of the folder name. Alternately, you can remove other themes except the default theme. That will force your site to use it.
    – If all the above steps do not resolve the issue, then try MANUALLY updating. Download a fresh copy of the WordPress .zip file to your computer, unzip it, and use that to copy up all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory. You may need to delete the old wp-admin and wp-includes folders and files on your server before uploading the new ones. Read the Manual Update directions first.
    Backup: If you haven’t already done, always backup everything (including your database) before doing any actions, just in case something really goes wrong.

    Thread Starter nikitarama

    (@nikitarama)

    Thank you for the help!

    I got FTP access and went to the line of PHP I put in and removed it. That did the trick!

    Moderator t-p

    (@t-p)

    Glad to know it 🙂

    This appears to be the most recent thread regarding WordPress “White Screen of Death” with WP 4.3.1.

    I have a virtual private server running 6 instances of WordPress and four had the white screen issue. After exhaustive review of the configuration, disabling add-on’s and other nonsense, the fix was to edit wp-config.php and add the line:
    define(‘CONCATENATE_SCRIPTS’, false);

    Just after the php opening tag. This resolved the issue and I wanted to document it here.

    Hello kind folks – adding my troubles to this thread which is dead-on what my issue is. Could someone take a look at this and steer me in the right direction??

    Scenario:
    While troubleshooting an image permission “parent directory writable by server?” in the WordPress 4.4.x install i have running, i decided to troubleshoot it by adding something to my WP-CONFIG.PHP file, which was:

    define(UPLOADS, 'wp-content/uploads');

    as the last line, and was saved and uploaded to FTP.
    Then came the WHITE SCREEN OF DEATH! In a panic, I grabbed the original file and uploaded that. Still nothing. My admin panel is alive and well, just not the front-facing blog itself.

    DEBUG throws this out:
    Warning: include(/var/www/MyWebsite.org/web/content/blog/wp-content/advanced-cache.php): failed to open stream: Permission denied in /var/www/MyWebsite.org/web/content/blog/wp-settings.php on line 74 Warning: include(): Failed opening '/var/www/MyWebsite.org/web/content/blog/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/MyWebsite.org/web/content/blog/wp-settings.php on line 74

    and my WP-CONFIG.PHP looks like this:

    <?php
    /**
     */
    
    // ** MySQL settings - You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define( 'WPCACHEHOME', '/mnt/stor10-wc2-dfw1/567388/MySite.org/web/content/blog/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager
    define('WP_CACHE', true); //Added by WP-Cache Manager
    define('DB_NAME', 'something');
    
    /** MySQL database username */
    define('DB_USER', 'something');
    
    /** MySQL database password */
    define('DB_PASSWORD', 'something');
    
    /** MySQL hostname */
    //define('DB_HOST', 'mysql51-25.wc2.dfw122.stabletransit.com');
    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 https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org 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("DISALLOW_FILE_EDIT", TRUE);
    define('AUTH_KEY',         'something');
    define('SECURE_AUTH_KEY',  'something');
    define('LOGGED_IN_KEY',    'something');
    define('NONCE_KEY',        'something');
    define('AUTH_SALT',        'something');
    define('SECURE_AUTH_SALT', 'something');
    define('LOGGED_IN_SALT',   'something');
    define('NONCE_SALT',       'something');
    
    /**#@-*/
    
    /**
     * 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  = 'wp_';
    
    /**
     * 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
     * de_DE.mo to wp-content/languages and set WPLANG to 'de_DE' to enable German
     * language support.
     */
    define('WPLANG', '');
    
    /**
     * 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.
     */
    
     define('WP_DEBUG', true);
    
    /* 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');

    I appreciate any and all suggestions! I’m filling in for a now-gone developer and obviously way over my designer head. Time to make the backup file.

    Cheers!

    i should probably note that the WP-Super-Cache plugin isn’t even installed or activated.

    Disabling the WP-CACHE to ‘false’ didn’t solve anything, and no debug entry was made.

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

The topic ‘White Screen after editing PHP – getting FTP access’ is closed to new replies.