Site Index Parse error?

I am getting the following error in logs.. the site won’t even load just shows a blank white page for the index and I can not access the manager either same thing
blank white page. There was a server crash I’m just wonder how it would effect this and would would return this error?

PHP Parse error: parse error, unexpected T_STRING in /var/www/vhosts/naturalbridgecabinrental.com/httpdocs/assets/cache/siteCache.idx.php on line 1328

I would get into the server and delete the siteCache.idx.php file, or move it to a different name.

Good Luck

Actually, to clear that file you can upload the blank one that came with the MODx installer or just create a new blank file with that name. Make sure that the permissions on the new file are correct for your server. Then you should be able to login to the manager and choose Site -> Clear Cache (and hopefully that will make your public website show up as before).

I tried both things mentioned aboved and nothing happened I’m still getting blank white pages that load up where the index and manager should be. :’(

Upload the original install/ directory (or even better, grab the latest release) and try running an upgrade install. This should re-establish a proper siteCache.inc.php file that works. It’s never really a good idea to delete or put a blank siteCache.inc.php file in an existing site; that will basically render it unusable. It’s better to see the line in the file causing the error and your next move will be better informed.

From line 1328:

}?4µ$s[’Ditto’] = ’/*

This appears to be the code in question.

Never seen anything like that, and out of context it means very little. Could be anything from a hacker injecting content into your file (assuming they compromised your user account or got your password somehow) to garbage written to the file due to a server crash/hiccup.

Looks like garbage to me. I guess I would next check the database to see if info in it has become corrupted. You may find, for example, that the Ditto snippet is to blame, and deleting it from the database might clear up the problem (you can always download and reinstall it later).

Quote from: ZAP at Mar 04, 2008, 07:27 PM

Looks like garbage to me. I guess I would next check the database to see if info in it has become corrupted. You may find, for example, that the Ditto snippet is to blame, and deleting it from the database might clear up the problem (you can always download and reinstall it later).

Ditto drives a large part of the site, without it it wouldn’t function. If I decompress a tar ball of 0.9.6.1 on top of the existing installation and running an upgrade do you think it would work would I lose any of the contents of my site by doing this? The site is rather large losing the entries and DB content associated with it is not an option.

Quote from: OpenGeek at Mar 04, 2008, 07:10 PM

Never seen anything like that, and out of context it means very little. Could be anything from a hacker injecting content into your file (assuming they compromised your user account or got your password somehow) to garbage written to the file due to a server crash/hiccup.

The server did infact crash and reboot. The database seems fine though