I’ve found where the problem is occurring:
the-events-calendar.php lines 1184-1189:
if ( isset ( $wp_query->query_vars['eventDate'] ) ) {
$this->date = $wp_query->query_vars['eventDate'] . "-01";
} else {
$date = date_i18n( The_Events_Calendar::DBDATEFORMAT );
$this->date = str_replace( substr( $date, 8 ), '01', $date );
}
When there is no event selected (which would be normal going to the calendar view, called “month”), that last line takes over to construct the date passed to the grid creator.
substr($date,8) pulls out the ‘day’ digits of the month, since the date looks like this: YYYY-MM-DD and the 8th character is the first D, so the substr returns the DD part (which, today, is 03… see where the problem is yet?). The whole date is 2010-03-03.
the str_replace tells it to check the $date (which is 2010-03-03) for the string figured out above (supposed to be the day pair) which turns out to be 03, and replace it with 01. So the date that is being calculated is now 2010-01-01 as both instances of the 03 were replaced with the 01. This must have also happened on February 2nd… unless there has been an update which modified this since then.
What I did to fix it, and I’m not sure why you’d always want the month view to default to highlighting the first day of the month, was to comment out this line:
//$this->date = str_replace( substr( $date, 8 ), '01', $date );
(the // comments out the line)
and change it to this:
$this->date = $date;
This seems to work, and it also serves to highlight what day is “today” on the month view.
I don’t think it breaks anything, but perhaps the people who wrote this could make sure I haven’t crippled anything. ??
On the up-side, of course… it should work perfectly well tomorrow (2010-03-04) and not break again until April 4th (2010-04-04).
Hope that helps someone.
