In wp-config.php, set define( 'WP_DEBUG', true );, and then report back whatever errors are reported.
Also: be sure to post Theme-specific support questions through the Theme’s dedicated support forum*, which can be found from the Theme’s Extend listing page, and which is here for Gray Opaque.
* Here’s why
I’m able to open the WP-admin tools, as I have not yet tried to activate the problem theme.
I tried to open WP-config.php and got a white screen and no error message, though. I’m not sure what you mean by “set define” the term “WP_DEBUG’, true”. When I tried to open “WP-config.php=?WP_DEBUG’, true” there was an error message: “The requested URL /signals/wp-config.php= was not found on this server.”
I read the WP-config file on the server and I think it looks like the original text file I uploaded.
You need to use FTP to access wp-config.php.
Oh, I think you’re trying to say I should edit and replace the current text file with change on the WP_DEBUG line. All Greek to me, sorry. I changed ‘false’ to ‘true’ on that line and uploaded it, and requested: http://www.synapse9.com/signals/wp-config.php.
Is that what you wanted? I got a blank page. Then I should activate Gray Opaque and see what wp-config.php returns then, I guess? Is there a way to back out, so I don’t have to completely start over the whole installation again?
Chip, I was waiting to see if you knew a way to back out of loading a theme that crashes the blog. Is there a specific group of directories or files that activating a theme would alter, that if I had copies of I could replace and restore the blog to working order?
I’ve done a little work on it, that I don’t want to lose by having to re-install WordPress entirely, as my only way to recover
Chip, I was waiting to see if you knew a way to back out of loading a theme that crashes the blog.
Using FTP, go into \docroot\wp-content\themes\, and delete the directory name that corresponds to the problematic Theme. e.g. if the Theme is Crappy Site Crashing Theme, the directory would be crappy-site-crashing-theme.
Simply delete the directory, and then navigate to your WP-Admin backend. WordPress will reset itself to use the current default Theme (TwentyTen in 3.1, or TwentyEleven if you’re beta-testing 3.2).
That won’t fix the issue with Crappy Site Crashing Theme, but will at least get you up and running again.
