Closed (fixed)
Project:
Date
Version:
5.x-2.0-rc4
Component:
Date Timezone
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Aug 2008 at 08:40 UTC
Updated:
20 Aug 2008 at 05:11 UTC
After installing date, date_timezone and date_api on Drupal 5.9 with cck 5.x.1.7, given the following error:
"The Date Timezone module requires you to set the site timezone name."
However, upon setting various timezone names in /admin/settings/date-time, including Etc/GMT, US/Arizona, America/Phoenix, US/Pacific, etc, the error persists as if no timezone name were set.
Comments
Comment #1
karens commentedAre you using the Event module? If so, that is the problem. The Event module wipes out the Date module's attempts to set the timezone.
Comment #2
karens commentedIn fact I can tell you are, because those are the deprecated timezones that are no longer used by the Date module, they only show up as options if you use the Event module. So you have to disable the Event module. There is an issue on the Event module issue queue about trying to get them working together, but it isn't going anywhere.
Comment #3
xolotl commentedThanks KarenS! I was using Event, but have found it so buggy I'm moving to just cck with a date field. I'll disable event.
I know this isn't the place to bring it up, and not sure if it's possible, but wondering if in the module.info files in addtion to "Required by" and "Depends on" we could also put "Conflicts with" and specifically disallow enabling a module if a conflicting module were in place.
Comment #4
karens commentedThat would be something Drupal core would have to do, you could create an issue for that (wouldn't happen before Drupal 7 at this point).
Comment #5
xolotl commentedthanks, gave my +1 to already existing core feature request http://drupal.org/node/92233
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.