$50 to the first person to rescue me from my living hell.
Consider the following conundrum:
- 2 identical working Drupal websites
- Each residing on a different dedicated Linux / Apache 2.0
- Both websites have identical clean installations of Drupal 4.7.3 (default modules, default blue marine theme, etc.)
- Both websites are setup to use the exact same physical MySQL 4.1.19 database (which resides on a 3rd dedicated, db-only server)
- Both have memory_limit set to 50MB
The problem arises when I try to enable the views.module (v 1.142 2006/08/04 16:00:46)
One site works fine, the other site gives me a white screen of death (no error messages, not in server logs or anything). It happens on and off from the second I hit submit on the modules page. The white screen is site-wide — no URI's work. Physically removing the 'views' directory from /modules/, fixes it immediately.
Researching drupal.org for the last 2 days has revealed the following short list of confirmed causes of similar behavior, followed by my steps to address each:
-
Not enough Memory
I admit this smells like a memory issue, except that both sites have the memory_limit set to 50MB (which should be more than enough, although I've experimented upwards of 128MB with no improvement), and one site works fine.
-
Cache corruption
I have repeatedly emptied the cache to no avail.
-
Database corruption
Both sites are using the exact same - brand new - database, and one works fine.
The biggest difference between the two environments is the fact that the working site uses PHP 4 and the non-working site uses PHP 5, which leads me to believe it's one of the many PHP config settings, I just don't know which one. But I have a crisp $50... (paypal payment) for the first person who does :D