<div>so I tried removing my all/modules and all/themes folder and I get an access denied message. If I bring back all my modules I'm suddenly able to see an unthemed homepage.</div><div><br class="webkit-block-placeholder">
</div><div>okay, this is really strange.</div><div><br class="webkit-block-placeholder"></div><div>So, I uploaded the full database again, with no modifications. I removed my all/themes folder and now I'm able to see an unthemed homepage. If I try to access any other pages, I get the WSOD.
</div><div><br class="webkit-block-placeholder"></div><div>Now, if I switch my theme to garland and upload that version of the db (and my all/themes folder removed) I get the WSOD.</div><div><br class="webkit-block-placeholder">
</div><div><br> </div><div><br> </div><div><span class="gmail_quote">On 8/24/07, <b class="gmail_sendername">Jason Flatt</b> <<a href="mailto:drupal@oadaeh.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
drupal@oadaeh.net</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Friday 24 August 2007 09:15:37 John Barreiros wrote:<br>> Thanks for the suggestions all.<br>> My host actually has the memory limit set to 32M. I increased to 50M, but<br>> still nothing.<br>><br>> I tried the suggestions from the handbook page, nada.
<br>><br>> I also tried switching to the garland theme, turning off friendly urls, and<br>> turning off all modules. nada<br>><br>> I looked at the error log, but it didn't tell me anything useful.<br>
>
<br>> next I created the db from scratch. This made the site show up. Then I<br>> turned on every module on one by one. The site is still showing. It looks<br>> like I have no choice but to rebuild the entire site. I'll be honest, this
<br>> really blows.<br><br>You might try it from the other direction and disabling modules on the<br>production site. You can move the modules out of the sites directory<br>one-by-one or all at once to see if your site comes back. I would probably
<br>start with a database back up, then by moving the e-commerce modules, since<br>there's so much code there.<br><br>Another thing to consider is potentially errant PHP code in a block or node<br>that might be causing the problem. I've done that enough times to look for it
<br>as an option.<br><br><br>--<br>Jason Flatt<br><a href="http://www.oadaeh.net/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.oadaeh.net/</a><br>Father of Six: <a href="http://www.flattfamily.com/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.flattfamily.com/</a> (Joseph, 14; Cramer, 12; Travis,
<br>10; Angela; Harry, 7; and William, 12:04 am, 12-29-2005)<br>Linux User: <a href="http://www.xubuntu.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.xubuntu.org/</a><br>Drupal Fanatic:
<a href="http://drupal.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/</a><br>--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.drupal.org/</a> ]<br></blockquote></div><br>