• Hey Guys
    After uploading my site to live server, all am getting is white screen without error.
    The posts and pages urls are loading as usual, but after the loading, all am getting is the same white page.
    The only pages that show some contents are #WordPress built in pages like …/wp-admin …/wp-login.php. Though the content it shows are not exactly as it ought to be, which also indicate some problem
    I can login to the admin dashboard, and there is okay. This issue only affect the front end site.
    The site is running multisite.

Viewing 8 replies - 1 through 8 (of 8 total)
  • This Codex article may provide an answer: Common WordPress Errors (including The White Screen of Death) « WordPress Codex.
    If not, please return.

    Thread Starter UgoDimma

    (@lovecoinz)

    Thanks for the link.
    I took a look at it, but one thing I think that might lead to my issu is memory limit, but after taking a look at my php.ini at my xampp, compare it with what I have on my live server, they are the same, but even as to that, I made little adjustment by increasing it at my live server, but nothing happened.

    NOTE, the site loads well on local machine, but not on live server, in this case, am not sure it get to do with theme or plugin as I have not installed, or updated any. As it is on local server, so it is on live server.

    In my site content, I don’t have any error log to look at.

    I don’t know if there is need to provide my site url here.

    jack randall

    (@theotherlebowski)

    check your php versions and the apache versions on xampp and your live server, the environments may not be the same. if in doubt contact your web host to find out if they’re optimally set up to host wordpress.

    Thread Starter UgoDimma

    (@lovecoinz)

    Hey Jack

    Thanks for pointing me to this direction. I see difference in bot

    XAMPP
    Apache Version Apache/2.4.12 (Win32) OpenSSL/1.0.1l PHP/5.6.8

    LIVE SERVER
    Apache Version Apache/2.4.6 (CentOS) PHP/5.4.16

    Am running vps, which mean, am in control some how. I will try to upgrade my server to be of the same value with my xampp where the site was developed.
    If resolved I will let you guys know.

    Thread Starter UgoDimma

    (@lovecoinz)

    PHP upgraded, but issue is still there.

    LIVE SERVER
    Apache Version Apache/2.4.6 (CentOS) PHP/5.6.17

    Thread Starter UgoDimma

    (@lovecoinz)

    Please guy

    What else should I do, or where else should I look into.
    Am hooked up in the middle of ocean, not knowing what exactly to do.

    Thread Starter UgoDimma

    (@lovecoinz)

    Hey Guys

    I added

    define('WP_DEBUG', true);
    error_reporting(E_ALL); ini_set('display_errors', 1);

    to my wp-config.php file at both the site, local machine and live server, and both of them display the bellow error

    Notice: Constant WP_MEMORY_LIMIT already defined in /var/www/html/wp-content/plugins/wplms-customizer/wplms-customizer.php on line 104

    Notice: Undefined variable: theme_customizer in /var/www/html/wp-content/plugins/wplms-hover-blocks/classes/hover_squeeze.php on line 7

    Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /var/www/html/wp-includes/functions.php on line 3787

    Notice: Undefined index: quiz_start in /var/www/html/wp-content/plugins/vibe-course-module/includes/bp-course-notifications.php on line 225

    Notice: Undefined index: assignment_start in /var/www/html/wp-content/plugins/vibe-course-module/includes/bp-course-notifications.php on line 225

    Notice: Use of undefined constant ATT_REQ – assumed ‘ATT_REQ’ in /var/www/html/wp-content/plugins/wplms-assignments/includes/assignments.php on line 130

    Notice: Constant VIBE_URL already defined in /var/www/html/wp-content/themes/wplms/includes/config.php on line 8

    Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in /var/www/html/wp-includes/functions.php on line 3619

    Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in /var/www/html/wp-includes/functions.php on line 3619
    Notice: Undefined variable: metabox_settings in /var/www/html/wp-content/plugins/vibe-customtypes/custom_meta_boxes.php on line 991

    Notice: Undefined index: action in /var/www/html/wp-content/plugins/wplms-assignments/wplms-assignments.php on line 59

    Notice: Undefined index: security in /var/www/html/wp-content/plugins/bp-social-connect/includes/class.init.php on line 41

    NOTE: On the local machine, it still displays the site content at the buttom, but on live server, it only display the error report and nothing more.

    When I deleted error_reporting(E_ALL); ini_set('display_errors', 1); and change `define( ‘WP_DEBUG’, <strong>true</strong>);
    to
    define( ‘WP_DEBUG’, <strong>false</strong>);` the site on local machine displays WELL as usual, but the one on live server still display white screen.

    On this note, where do I start?
    What next should I do?
    Am no coder, and knows very little. But with a good instruction, I can handle it.

    Thread Starter UgoDimma

    (@lovecoinz)

    Is quite painful getting no help. Better still, I kept on digging.

    Hey guys, after adding the bellow code to my wp-config.php file

    // Enable WP_DEBUG mode
    define( 'WP_DEBUG', true );
    
    // Enable Debug logging to the /wp-content/debug.log file
    define( 'WP_DEBUG_LOG', true );
    
    // Disable display of errors and warnings
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );

    to the two sites, live server and local machine, the site on local machine was able to create debug.log authomatically on wp-content directory. To verify it creates it authomatically, I deleted the file debug.log, and reload my site, then the file recreated again authomatically. But the site on live server were unable to create the file, debug.log. So I think it might be permission issue.

    I have earlier on granted the required permission to the files and folder by using the bellow command as prescribed by WordPress Codex
    For directories
    find /path/to/your/wordpress/install/ -type d -exec chmod 755 {} \;
    For files
    find /path/to/your/wordpress/install/ -type f -exec chmod 644 {} \;
    For the benefit of doubt, I checked it again using ftp, and their permissions are as follows
    Directorie – 755
    Files – 644

    In this case, is like WordPress does not have the necessary permission to rewrite, but how and why?

    Some help please.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘White page without error report’ is closed to new replies.