4938 Posts in 16764 Topics by 1490 members
|Go to End|
1 September 2010 at 8:06am
I'm going absolutely CRAZY trying to get a SilverStripe instance back up using the same code and database as I was before. (Indeed ALL OF my SS instances are dead). I've spent way too much time on this and am now asking for help from the pros.
I just upgraded from Win XP to Windows 7 and as you may or may not know this causes you to have to reinstall most of your programs, Apache (2.2.16) and PHP (5.3.3) among them, which I have done. PHP is running. MySQL is running. Both verified using <? phpinfo(); ?>. And I have the DocumenRoot set to my SilverStripe root and mod_rewrite is enabled and AllowOverride All is set blah blah blah. And the database I'm referring to in _config.php is literally the same database as it was right before the upgrade. Nothing has changed. And the SYSTEM account as well as MY Windows account has full control of the root folder and subfolders.
But guess what -- EVERY request is a BLANK PAGE (not even an <html> tag) and there is NOTHING in the error log.
When I try to run the install script, it gives the Status message "Creating C:\Workspace\...\...\.htaccess" and then stops. For good. It does in fact create the .htaccess file but then nothing happens after that and any request to the site results again in blank pages, including the CMS. What am I doing wrong here?
I can run a normal non-SS PHP site without any issues. It seems clear that this is a configuration problem, but I'm at my wit's end. I'm going to attach my php.ini and httpd.conf and hopefully someone out there can help me out with this. I've developed probably a dozen SS sites but had never touched my Apache/PHP/MySQL installs until now and voila.
Thanks in advance,
1 September 2010 at 5:41pm
Never had this error personality but how I would debug it is put a die('123'); at the top of sapphire/main.php. This file is the first file after the .htaccess which is called. If you don't see a 123 then the issue is with htaccess. Debugging that is a bit trickier. You can take that out of the equation by using the index.php file - eg try domain.com/index.php/admin and if you still get a blank screen then put that die('123'); statement in index.php. Once you start seeing 123 then move the die statement futher down the execution pipeline till it blank screen. That should isolate a function / line.
2 September 2010 at 7:12am
Hi @Willr. Thanks for replying. I did as you instructed.
I followed the code from main.php to Core.php and then it seems to be dying in the function include_manifest() on line 70 (require_once(MANIFEST_FILE);) in ManifestBuilder.php. The die() prints out before this line and then not after. And i don't know what MANIFEST_FILE refers to so I'm not sure where to go from here. Help!
|Go to Top|