Entire Site Went Blank [Solved]

Quote from: stempy at Sep 19, 2007, 11:23 PM

Are you able to preview ANY pages, or able to view the source code of any, it could possibly be a snippet problem, perhaps host upgraded their servers (version of PHP, MySql, etc)
What you might want to do is enable PHP error checking and reporting, if there is a parsing error, it usually results in a blank page.

Stempy - That is what I’m not sure of on the host side I don’t think they did, but if they did would that cause this kind of problem? If so, is there plans to have modx not do that if that happens to anyone? ^_^

When I go to the blank page and view the source nothing comes up at all. The preview on the manager shows a blank page too. Might be a snippet problem but I would wonder why just out of the blue it would just fail? Either way can you remind me how to get a php error checking setup again I know it’s a php.ini file but I forget the rest.

Quote from: Izumi at Sep 20, 2007, 06:11 PM

Quote from: stempy at Sep 19, 2007, 11:23 PM

Are you able to preview ANY pages, or able to view the source code of any, it could possibly be a snippet problem, perhaps host upgraded their servers (version of PHP, MySql, etc)
What you might want to do is enable PHP error checking and reporting, if there is a parsing error, it usually results in a blank page.

Stempy - That is what I’m not sure of on the host side I don’t think they did, but if they did would that cause this kind of problem? If so, is there plans to have modx not do that if that happens to anyone? ^_^

When I go to the blank page and view the source nothing comes up at all. The preview on the manager shows a blank page too. Might be a snippet problem but I would wonder why just out of the blue it would just fail? Either way can you remind me how to get a php error checking setup again I know it’s a php.ini file but I forget the rest.

If PHP error reporting is turned off, and any error occurs it usually displays a blank page. What may have happened, is corruption in db, or PHP settings may have changed, possibly safemode. or base directory restrictions switched on, among other things.

to enable php error_reporting quickly..edit the index.php file in the main directory (same level as assets and manager folder)

ini_set("display_errors",1);
error_reporting(E_ALL);

You may have to check the rest of that file to make sure it’s not disabled elsewhere, hopefully this may give an indication.

Stempy - I added those lines to the index.php site still comes up blank. I deleted the other error checking set to 0 as well, no change or anything, any other way to try?

Thanks

You mentioned this is 0.9.5. Are you positive this has not been upgraded to 0.9.6? If it was 0.9.6, I might have possible solution, but it does not apply to 0.9.5, so I’m at a loss.

To truly see what’s happening, access to the raw server logs, including Apache’s access and error logs, might help identify the problem more quickly...

Izumi,

I had the same thing happen to me with 0.9.5. Since none of the other ideas have panned out, I thought I’d mention my experience.

In my case, I could go directly to a subsidiary page on the site if I typed its URL directly but going to the home page or the manager led to a blank screen and no code in "view source." Trying to go directly to some page other than the default page might be useful in diagnosing your problem.

My problem turned out to be a badly formed snippet call on the home page. I had listed one parameter twice and had used single quotes rather than backticks in the snippet call.

You said you hadn’t changed anything at the site. If that’s true, this suggestion probably won’t help, but it may be useful for others. It might still help you eliminate the possibility that you have a snippet problem.

I’m afraid Susan is right about familiarity with the database.

The only way I could solve my problem (and since nothing else is working, you might try the same) was to edit the source code of my home page in the database using PhpMyAdmin.

I just went in and edited the record directly in the MODx database. After I MODx database for a while, it began to make some sense to me and I began to get a sense of what I could safely change.

Here are the steps that solved my problem:

Before starting, backup your database!

1. Go to your hosting site (Cpanel or the equivalent) and launch PhpMyAdmin.

2. If there’s more than one database, select the MODx database.

3. Look for the modx_site_content table.

4. Click on the browse icon for that table.

5. Find your home page (default) document (often its ID is 1) in the modx_site_content table.

6. Click on the little pencil icon to edit it.

7. Scroll down to the "content" field.

8. You might want to use cut and paste to copy the entire text of the content field to someplace safe (e.g. a notepad document) so you can undo your work later without restoring the whole database. This will also let you examine the code of that page. You could edit the code in notepad and paste it back into the database field.

9. Remove any snippet calls in the "content" field (again, save them somewhere so you can later correct any problems and put them back). You can also try removing them one at a time to see which one (if any) is causing the problem.

10. Click on the "go" button to save your changes.

As an alternative, you could try using one of the programs Susan recommended to do the same thing.

Good luck,

Bob

Greetings everyone,

I didn’t have a chance to check the logs or anything, but I figured it was best to just upgrade and see what happens. That is what I did and the site now is working just fine on 0.9.6 I’m still unsure why the entire site would have went blank, but everything is working fine now so, just a side note for anyone else that might have/had this problem upgrading to the current release might fix things.

Thanks for attempting to help everyone.