Closed (fixed)
Project:
Date
Version:
5.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Mar 2008 at 13:01 UTC
Updated:
24 Mar 2008 at 20:41 UTC
I just verified this, after spending a few hours tracing it.
On A Drupal 5.7 install, Php 5.2.3, when I activate the "Date" module, i get a "white screen of death" on some admin pages, like for example "Backup and Migrate" or when setting up a CCK content-type.
Date API and Dqate Timezone are on, and everything is fine. Switching Date on as well causes the problem.
See also http://drupal.org/node/205952
Comments
Comment #1
sam6 commentedOne more thing. With "Date" on, if I try to access a new CCK type where I previously had created a date field, I get the white screen even by simply accessing the CCK "Manage fields" tab. Accessing any other CCK type without Date fields is fine.
Comment #2
karens commentedDid you empty the date folder out before adding the 5.2 code? The files are completely re-configured and if you have old 5.1 files in there all kinds of unpredictable things can happen.
Comment #3
sam6 commentedI installed a completely new instance of Drupal. I will do it again to reproduce it and report back to you.
Comment #4
sam6 commentedRonan gave an excellent .htaccess tip:
"White screen of death is usually caused by a fatal error with error reporting suppressed. Usually adding the following line to your .htaccess file can be very helpful
I created a completely new 5.7 drupal instance, added the .htaccess directive, installed the latest backup_migrate, views (5.x-2.x-dev, btw, thanks for the new version that came out today) and I was able to reproduce the problem.
This is the error message I get after enabling the Date module:
I uninstalled the token module, whilke keeping the Date module on, invoked the backup_migrate URL and everything was normal.
It would seem the problem lies somewhere in the token/date modules interaction. The backup_migrate module suffers from it as well and acts as telltale.
But I do not think the problem is with backup_migrate. In fact, I get the same error message when (having Date and Toke 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)
Comment #5
sam6 commentedIt seems the bug was related to the Token module.
I installed the latest dev release of the Token module (2008-Feb-24) and the problem disappeared.
Thank you for all your help!
Comment #6
sam6 commented.
Comment #7
karens commentedIf you use the Token module, you need the latest version of both Date and Token to fix a problem where the Token module was using functions that no longer exist in the new Date module.
The version of the Token module that fixes the problem is not yet an official release, but it's necessary to avoid this problem. Both Date and Token will soon issue official releases with the fix.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.