Unable to configure - "white screen of death"

Are you using the very latest version of the module? This sounds a lot like this issue (http://drupal.org/node/191659), which was fixed by changing the way i detect the zlib library. If you are in fact using the most recent version, can you let me know what environment you're on? What version of PHP and MySQL? Do you have the zlib module? Are all the tabs failing or just the configuration tab?

More info on debuging this can be found on the thread linked above.

Thanks
R

I am having the same problem (posting it here, since the http://drupal.org/node/191659 ticket is closed.)

I am hosting Drupal 5.7 sites with DreamHost, but all other similarly configured Drupal sites are able to run *Backup and Migrate* just fine.

The version of *Backup and Migrate* is the latest one.

I am able to access:

admin/content/backup_migrate/restore - works!

admin/content/backup_migrate/files - works and both the 'files/backup_migrate' and 'files/backup_migrate/manual' directories were created.

admin/content/backup_migrate/files/scheduled - works, files/backup_migrate/scheduled created

admin/content/backup_migrate/schedule - works

The only problem is with the home page of the module:
admin/content/backup_migrate - where I get the White Screen

There are no errors printed, the error log does not have any trace, and the source of the page is completely blank, 0 bytes.

Caching is completely off, and I tried switching themes, with no results.

I can't figure figure it out, especially since the same module, with the same Drupal, on same hosting provider do work.

I verified this happens when I have installed the date (CCK) module (could it possibly interact with the date module becasue of the "Timestamp format:" field?)

By deactivating the date module, the *Backup and Migrate* module runs fine again.

BTW, I opened a bug with the Date project: http://drupal.org/node/228754

Thanks for the info, I use date.module and backup and migrate on most of my sites without a problem, but I'll look through the code to see if there's anything obvious with the date stuff that may be causing this.

White screen of death is usually caused by a fatal error with error reporting suppressed. If you can turn on full error reporting and let me know if there is an error reported that would really help me track this down. I don't know dreamhost's configuration, but usually adding the following line to your .htaccess file can be very helpfull

  php_value error_reporting                 6135

this assumes php 5. for php 4 try 2047 instead of 6135

R

Thank you for the .htaccess tip

I created a completely new 5.7 drupal instance, added your .htaccess directive, installed the latest backup_migrate, views (5.x-2.x-dev, btw, it seems a new version came out today) and I was able to reproduce the problem.

This is the error message I get after enabling the Date module:

Fatal error: Cannot redeclare date_token_list() (previously declared in /home/.reggea/forumcivico/sandbox.forumcivico.it/sites/all/modules/date/date/date.module:354) in /home/.reggea/forumcivico/sandbox.forumcivico.it/sites/all/modules/token/token_cck.inc on line 226

I uninstalled the token module, and invoked the backup_migrate URL and everything was normal.

It would seem the problem lies somewhere in the token/date modules interaction, and the backup_migrate module suffers from it as well.

I do not think the problem is with backup_migrate. In fact, I get the same error message when (having Date and Token active at the same time) I try to manage a CCK field, even if it is not a Date field.

(Url like example.com/admin/content/types/story/fields/field_b)

Fatal error: Cannot redeclare date_token_list() (previously declared in /home/.reggea/forumcivico/sandbox.forumcivico.it/sites/all/modules/date/date/date.module:354) in /home/.reggea/forumcivico/sandbox.forumcivico.it/sites/all/modules/token/token_cck.inc on line 226

I cross posted these comments also in the corresponding Date bug tracker:

http://drupal.org/node/228754#comment-753412

It seems the bug was related to the Token module.

I installed the latest dev release of the Token module (2008-Feb-24) and the porblem disappeared.

Thank you for all your help!