CiviCRM Community Forums (archive)

I just upgraded an existing Drupal 6.13/CiviCRM 2.2.8 installation to Drupal 6.15. All the Drupal screens behave as expected, but all /civicrm/* screens are now completely blank.

I followed the Drupal upgrade instructions exactly, including disabling all modules (including CiviCRM) during the upgrade. Not seeing anything unusual in Apache logs.

Not quite sure where to start. Can someone give me a hint? Thx.

Thank you. Just for a sanity check, can you tell me whether I'm looking in the right places?

For watchdog, I'm using the Drupal web interface at Administer>Reports>Recent log entries. If I attempt to browse to a non-existent URL on my site (/abc) I see a "page not found" warning in the log. But if I go to /civicrm/dashboard, no entry is added to the log.

For Apache, I'm looking in the file I specified as my "ErrorLog" in my <VirtualHost> configuration. There are a few errors from today noting that the file favicon.ico doesn't exist, but that's it.

I've also edited php.ini and set "display_errors = On" and restarted Apache. Still just a white screen when I browse to /civicrm/dashboard.

Does that sound like I'm looking in the right places or am I missing something? Thanks again.

Okay, assuming I'm reading my logs correctly:

• Any suggestions as to how I might begin to debug this problem?
• Is there some sort of cache I could try clearing or some other sort of reset I could give a shot just to see if it works?
• Can anyone confirm that the "sites" directory is the only one you need to backup/restore during a Drupal upgrade? In other words, CiviCRM doesn't write to any directories outside of "sites", right? When I upgraded Drupal, I backed up "sites", wiped out the entire Drupal install dir, extracted the new Drupal installation, and restored the previous "sites" dir (along with all the other upgrade steps). I wasn't supposed to backup/restore some other dir besides "sites" for CiviCRM, was I?

Thanks for any help.

Thanks again for the response. I was already at 128M, and I tried your suggestions to no avail.

But now my problem is getting more serious. I just tried to revert to Drupal 6.13. I wiped the install dir, extracted 6.13, restored my original "sites" dir from a tarball, and restored my database from a dump file I took immediately before starting the upgrade. Drupal is back to where it was and it works but I'm getting the same behavior with all civicrm pages - WSOD. Clearly, I screwed something up during the initial upgrade. In fact, while reverting to 6.13 I realized something odd happened when I was first backing up the sites dir. After I tar'd it, I tried to "rm -rf" the install dir, but there were a handful of files in the sites dir (I think they may have been in a civicrm subdir) that I didn't have permission to delete, so I had to do it under sudo. So maybe those files didn't make it into the sites tar either.

The only thing I can think of to do at this point is to delete civicrm.settings.php and files/civicrm, drop all civicrm_ tables in my DB and reinstall from scratch. So here's my question: if I install a fresh copy of civicrm, what tables would I need to restore from my backup to get things back to the way they were? Or is that whole idea asking for trouble?

I am getting same WSOD with new installation of Drupal 6.16 and civicrm-3.1.3-drupal. Any ideas? Installed drupal, then civicrm with everything seemingly going smooth. Click on anything Civicrm and get blank screen.


Hmmmm, checked the error logs and found this...


PHP Fatal error:  Uncaught exception 'Exception' with message 'SimpleXML not loaded.' in /var/www/.....

I had the same problems. I removed the templates_c dir and then tried to issue the update statement for the backend. This solved the white screens and errors.

The only problem I now faceis that when I use CSS optimization CiviCRM stops working displaying a page cannot be displayed error (all other settings in Drupal's Performance module work properly). Perhaps this happens with you as well.