Missing argument x for theme_date_all_day()

Just did the updates to 6-2.x-dev and D6.16 and am seeing these errors as well. PHP 5.2.9 with CCK 6-3.x-dev, Date, Date API, Date Popup, Date Timezone, Date Tools, and Date Repeat API enabled.

* it doesn't appear on the create content form or when viewing previously created nodes, but does get output in Views which display nodes with Date module dates.
* when I edit a node containing a Date field, the messages appear on the edit form. When I save the node, the messages do appear when viewing the node— even if it was not appearing before the edit.

The errors go away when I disable Date Repeat API.

--
Update: looks like it is related to comment #9 in #698522: Make date compatible with both views 2 and views 3.

Marked #733828: Errors when displaying multiple day date. as a duplicate, in which hawleyal reports seeing the errors on multi-day dates.

Marked #734532: UPgraded on Mar 5 as a duplicate.

I have the same problem :(

Doesn't go away when date repeat api removed

I upgraded to the new dev version because the "now"function didnt work..

Now I installed the dev version and get big lists of # warning: Missing argument 6 for theme_date_all_day() all over my site..

What version should I install? :(
I don't want these warnings but I need the "now" function to work

Does anyone know in what version the "now" function does work?

Than I just will install an older version

Subscribing... same issue on my date output.

Same problem - looks like it is caused by something not being passed.

Changing the function to have undefined variables defined as = NULL makes the errors go away.

e.g.

function theme_date_all_day($field = NULL, $which = NULL, $date1 = NULL, $date2 = NULL, $format = NULL, $node = NULL, $view = NULL) {

subscribe

subscribing

subscribing

subscribing

Me too, thank you!

RAR, your solution above worked wonderfully, at least on my simple one-date-field content type. Thanks!

Subscribe

I had the same problem. Apparently the maintainer corrected the problem in the latest dev-version (March 9 2010). It would be helpfull though if he/she would make a note of this somewhere (like here in this issue).

Mike.