Drupal Association members fund grants that make connections all over the world.
Based on my initial fork from kiphaas7's work, I had found a number of issues concerning the date which had to do with the default_timezone and other function call changes.
Yeah, the result of not having some of this is always having this on signup creation:
Warning: array_push() expects parameter 1 to be array, null given in date_formatter_format() (line 453 of /home/rfay/workspace/d7git/sites/all/modules/date/date.module).
I'm a little bit lost - is the patch causing other errors to come up or fixing the issue you are having?
Your patch is essential. (I was working on a similar one).
I just put it in CNR.
Shouldn't this patch be in the "date" project?
Ok, sorry for confusion. :-/
I didn't see the /sites/all/modules/signup/includes/date.inc.
The first part of the patch on this issue is somehow related to #1190944: Notice: Undefined property: stdClass::$language in _signup_date_get_node_scheduler(), which solves an actual error ($node->language, not being defined) which may have been causing the array_push error in the first place, but I'm not totally sure.
The patch on this issue may also solve the same issue by changing the order of the two if statements. I'm not 100% sure of the intended impact of switching the preference from where to grab the date value from, but the fact is $node->language will never be set because the $nodes passed to this function are not real nodes, so if by any chance, it gets past the first if, then it will still fail.
I wasn't experiencing the time-zone issues reported on this thread, so I ask that you also take a look at my issue as well, to perhaps combine forces.
We can integrate this applied patch for the desired result.It will be needful
Unassigned so others can do something about this.
Drupal is a registered trademark of Dries Buytaert.