this error happens on a clean install if i enable *all* date modules at once.
it does not happen if i
- enable Date Timezone
- set timezone
- enable other modules

imho if this is not checked by code there should be an idiot-proof warning... (at least i didnt see one)

see also: http://drupal.org/node/216365#comment-724917
this user seemed to have the same problem

Comments

CarpeDiemEVive’s picture

CarpeDiemEVive commented

I'm running into this issue, but I don't quite understand your workaround. Is it as simple as disabling all of my date modules and re-enabling them one at a time? I had the Date Timezone already enabled, I disabled it to see if that would help. I also had my timezone set already. I changed it and changed it back, but still no good. I could enable other modules, but is there any rhyme or reason as to which modules I enable to get this to work?

I would vote for a check in the code on this, because I've never really considered myself an idiot, but if I got caught by it I'm sure others will ;)

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented

>Is it as simple as disabling all of my date modules and re-enabling them one at a time?
In my place it seemed to be, see above.

The major problem for tracking this is that drupal provides no backtrace.
If this error persists you might want to use debug.module or try this: http://www.lullabot.com/articles/quick_and_dirty_debugging

;-) aexl

karens’s picture

karens commented
Status: Active » Fixed

I'm totally unable to replicate this in the latest dev code, so I think it is since fixed.. I tried various flavors of clean installations, including enabling CCK, Views, all the Date modules and all the Calendar modules at the same time, and had no trouble.

DerTobi75’s picture

DerTobi75 commented

I got the same issue right now! Do not know, how to fix it ;(

karens’s picture

karens commented

I just made some new commits that should take care of this for once and for all by changing the code to always return a valid date object (previously sometimes NULL was returned.)

This is in cvs now and will get into the dev tarball by tomorrow.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

robertgarrigos’s picture

robertgarrigos commented
Status: Closed (fixed) » Closed (duplicate)

This is not fixed but a duplicate of another issue (http://drupal.org/node/247215) which is not fixed either.

However, this answer (http://drupal.org/node/247215#comment-847566) gives a workaround that helps. The problem seems to be in the calendar default view provided by the calendar 2 module.