Hi,

It seems with the recent release of Calendar (3.1), this module has to be fixed: when displaying the block, the tooltip is empty and displays a serie of message like Notice: Undefined offset: 0 in calendar_tooltips_preprocess_calendar_datebox() (line 80 of calendar_tooltips/calendar_tooltips.module)..

Comments

simon georges’s picture

Status: Active » Needs review
StatusFileSize
new1.55 KB

This patch seems to work for me.

pfx’s picture

I encountered the same problem in the last update of the Calendar.
Your patch has completely solved the problem!
thank you

simon georges’s picture

Status: Needs review » Reviewed & tested by the community

Thanks for your feedback!

Tezza’s picture

Calendar 7.x-3.2
Calendar Tooltips 7.x-2.0

Patch in #1 works for me. Thank you Simon.

simon georges’s picture

Priority: Major » Critical

Let's raise the priority, as a lot of users seem to be affected.

rob c’s picture

Looks good. Indeed fixes this error. Everything else (from what i've seen now) still works. Tried disabling/enabling javascript in my browser and also have ajax activated for the calendar, this all still works.

knoppyFR’s picture

Same problem. Does anybody can help me to apply the patch ?
I don't understand how to apply it.

Thank you

simon georges’s picture

@knoppyFR, everything related to applying patch is at http://drupal.org/patch/apply.

rjb’s picture

Thanks Simon for the patch and thanks everyone else for testing. I will apply it asap.

One thing to watch out for is that our users have to upgrade Calendar as well, otherwise the same kind of error will occur. The Calendar maintainers changed an array index from a numeric one into a string, which is an improvement of course, but it also causes an incompatibility with older versions of Calendar.

simon georges’s picture

rjb, you may eventually indicate in the next release that you need an upgraded version of calendar (by using an explicit dependency).

rjb’s picture

Thanks. Will do.

rjb’s picture

Version: 7.x-2.0 » 7.x-2.1
Status: Reviewed & tested by the community » Fixed

Fixed in 7.x-2.1.

Status: Fixed » Closed (fixed)

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