Announcement

Collapse
No announcement yet.

Entire site blank pages

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Entire site blank pages

    Two days ago my 3.8.4 test board was working perfectly. I've made no changes, and tonight I get a blank page for any page I try going to on the site. This includes the ACP. No matter what URL I enter for the site, it's blank.

    I've already gone through this page of the manual regarding blank pages: http://www.vbulletin.com/docs/html/blank_pages. Is there any other reason this might happen?

    My live site on the same domain and server is fine. It's just the test board that took a walk.
    ~ Life isn't always fair, but you can be. ~

  • #2
    Maybe trying going through that list again.

    Also try a full refresh (CTRL-F5) of the page.

    Comment


    • #3
      Full refresh is always the first thing I try, and many times during troubleshooting.


      The list:
      1. You did not upload the vB files correctly...
      Not relevant in this case, since the problem sprung up on an existing board that worked properly a couple days ago.

      Then, if you can access the Admin CP, run 'Suspect File Versions' in Diagnostics...
      I cannot access the Admin CP.

      2. You have extra space or lines in your config.php file. Make sure there is no whitespace or extra lines in config.php either before the <?php or after the ?>. [Note: Beginning with 3.6.3 the trailing ?> was removed.]
      There are no extra spaces in the config.php file.

      3. If this is happening on the forum home page only, then you may have an empty index.html or index.htm file in that directory. Delete it.
      It is happening on all pages, not just forum home.

      4. You have a bad plugin installed. To disable the plugin system, edit config.php and add this line right under <?php

      define('DISABLE_HOOKS', true);

      Note: If you are running vBSEO or other add-ons that use .htaccess rewrite, you will need to remove those changes as well.
      Done. No change.

      5. The servername setting in config.php is wrong. Doublecheck this setting. 99% of the time, 'localhost' is correct:

      $config['MasterServer']['servername'] = 'localhost';
      Servername is correct in config.php

      6. Your PHP has magic_quotes_sybase turned on...
      Not relevant, since the site worked a couple days ago, and highly doubtful the host made any changes in this area.

      7. [For multiple white pages] You have added code to your header, headinclude or phpinclude templates that is no longer functional.
      [For white pages in a select area] You have added code to one of your templates that is causing this problem.

      The quickest way to find out if a custom template is at fault is to create a new style with no parent style and try that:

      Admin CP -> Styles & Templates -> Style Manager -> Add New Style
      No code has been added since the site last worked properly. Even so, I can't get into the template system to check it out.

      8. You have a corrupted template. Repairing the template table may help:

      REPAIR TABLE template;
      Ran the repair query via phpMyAdmin, since I can't do it in the Admin CP. No change.

      9. You have GZIP enabled. Try turning GZIP off here:

      Admin CP -> vBulletin Options -> Cookies and HTTP Header Options -> GZIP HTML Output -> No

      Or by running these queries in the SQL tab in phpMyAdmin:

      UPDATE setting SET value = '0' WHERE varname = 'gzipoutput';

      UPDATE datastore SET data=REPLACE(data,'s:10:"gzipoutput";i:1;','s:10:"gzipoutput";i:0;') WHERE title='options';

      You can also edit config.php and add this right under the <?php line to disable GZIP:

      DEFINE('NOZIP', 1);

      Sometimes this problem is caused when your server is already using GZIP and by turning this on in vB you were double compressing. This causes problems with some pages but not others. It also happens to some people and not others.
      Tried it, no change.

      10. Sometimes this can also be caused when PHP has the 'display_errors' function turned off. So instead of displaying the actual error so you can see what is wrong, you get a blank page. Look at your phpinfo page and if 'display_errors' is Off or '0', then add this line to your includes/config.php file right under <?php

      ini_set("display_errors", true);
      Done, no change.

      11. Check your phpinfo page to see if suhosin is installed as a module. If it is, this could be the cause of this problem. To fix this, add or edit an .htaccess file in your root forum directory and add these lines to it:

      php_flag suhosin.cookie.encrypt Off
      php_value suhosin.request.max_vars 2048
      php_value suhosin.post.max_vars 2048
      Tried, no change.

      12. This can be caused by a bug in PHP 5.2.5:

      http://bugs.php.net/bug.php?id=43620
      Not using PHP 5.2.5.

      13. This can also be caused by a memory_limit setting in php.ini that causes the server to time out before displaying the page. Edit config.php and add this right under the <?php line:

      ini_set('memory_limit', -1);
      Tried, no change.

      14. If the script producing this problem is showgroups.php, then you may have too many usergroups for this. Make sure this is set to 'No' for any groups except Admins and Mods:

      Admin CP -> Usergroups -> Usergroup Manager -> Edit Usergroup -> Viewable on Show Groups
      Not relevant.

      15. Check the file and directory permissions. Although this can differ by server, in general the directories should be chmod'd to 755 (-rwxr-xr-x) and files to 644 (-rw-r--r--). If any are set to 777 (-rwxrwxrwx) then this could result in blank pages.
      CHMODs are correct

      16. Check your .htaccess file for any rewrite rules that may be effecting the page(s) you are having the issue with. If your problem is only in one particular directory, you may need to exclude the rewrite rules from working in that directory.
      Not relevant.
      ~ Life isn't always fair, but you can be. ~

      Comment


      • #4
        Problem solved. It was a PHP version conflict on the server. Turns out my host account was set to 4.4.9 but I was using 5.2.13? No idea what happened there. The host had to fix it.
        ~ Life isn't always fair, but you can be. ~

        Comment


        • #5
          Interesting. Thanks for posting back.!

          Comment

          widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
          Working...
          X