The error message:

  Notice: Undefined index: wildcard in calendar_plugin_display_attachment->display_granularity() (line 70 of sites/all/modules/calendar/includes/calendar_plugin_display_attachment.inc).
  Notice: Undefined index: wildcard in template_preprocess_calendar_main() (line 46 of sites/all/modules/calendar/calendar_multiday/theme/theme.inc).

The attached patch adds an isset() check before each of the problematic spots.
I do not know why wildcard is unset nor if it should be unset.
If it is the case that wildcard should always exist, then this patch does not solve the real problem, only solves the symptoms.

Comments

thekevinday’s picture

Status: Active » Needs review
brightbold’s picture

Also an issue in 7.x-2.x-dev: see #1123564: Notice: Undefined index: wildcard in calendar_plugin_display_attachment->display_granularity() (thanks for catching that thekevinday!) &mdash should these be combined as duplicates or kept separate since they're different versions?

thekevinday’s picture

Looking at the git repository, they at some point forked 7.x-1.x-dev into 7.x-2.x-dev without even making a stable 7.x-1.x release. (There is only -alpha3).

Given how similar both branches are, most bug-fixes in 7.x-2.x would, and probably should, apply to 7.x-1.x.
In fact, their difference seems to be only about 8-commits.

This means that most bugs reported in 7.x-2.x are also bugs in 7.x-1.x. I would say its up to you on how you want to handle "duplicates" here as I do not know what the developers are doing by starting a new development branch before even finishing the current stable branch.

karens’s picture

Status: Needs review » Closed (won't fix)

The release notes and the project page both say that 7.x-1.x should not be used. It was the initial port which then ended up needing such major refactoring that I needed to spin off a different branch to warn people that were using it that things would break in a big way.

The wildcard error is because Views changed this to 'exception' in the latest code, and I'm fixing that in the 7.x-2.x branch.

karens’s picture

Status: Closed (won't fix) » Fixed

That was supposed to be 'fixed' :(

karens’s picture

Oops. I see I did not mark 7.x-1.x as unsupported, so now I did.

Status: Fixed » Closed (fixed)

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