Bug: Mini Calendar widget: TribeEvents nextMonth() calculation

[timhengeveld]

Hi,

The function nextMonth() in the TribeEvents class is used for calculating which month to load with the prev/next month buttons in the Mini Calendar widget.

But if the current day number does not exist in the subsequent month, this leads to skipping a month when clicking the next month button in the mini calendar widget.

Examples:
$tribe_ecp = TribeEvents::instance();
$tribe_ecp->nextMonth(‘2014-01-29’); // Returns 2014-03

$tribe_ecp = TribeEvents::instance();
$tribe_ecp->nextMonth(‘2014-03-31’); // Returns 2014-05

The next month value is set in the ‘data-month’ attribute of the next month link anchor tag in the calendar widget (used in widget-calendar.js and send via Ajax), which causes the mini calendar widget to skip months on some occasions (like today: 2014-01-29).

The bug can be easily duplicated on your own demo site: http://wpshindig.com/event-widgets/ in the Mini Calendar widget on the top right of the page.

Kind regards,
Tim

[Matthew]

This reply is private.

[Barry]

This reply is private.

[Barry]

Apologies everyone, that last reply shouldn’t have been marked as private – our forum software can be a little overzealous sometimes. Let me re-post that:

We did do some work in relation to that problem and it looks like the calendar widget may unfortunately have been missed or some code inadvertently rolled back, perhaps – but we’ll certainly ensure this gets back on the tracker and fix it as quickly as we can. Thanks for bringing it to our attention!

@Matthew: with regards to events not being listed below the widget, that’s a different issue but if I’m understanding you correctly it’s not something I can replicate. Can you create a new thread for this specific issue?

Thanks!

[Barry]

I’ll close this thread for the time being, but we’ll certainly do our best to post an update re the calendar widget issue once we’ve got something further to report on that end. Thanks!

[Barry]

Hi! We’ve now completed some work that ought to address this issue in our very next upcoming release. Thanks for your patience and if you do hit any further problems with this once you’ve updated please don’t hesitate to let us know in a new thread – thanks!

[Author]

Posts