Since updating Drupal installation to 7.24 SOME of my new events give the following error code:
Fatal error: [] operator not supported for strings in /home/robadmin/public_html/includes/common.inc on line 2445

I create a new event to be posted to my calendar (the same way I have been doing successfully all year) and when I hit save I get the error code above. The event IS created AND appears in both the calendar and the upcoming events views but when you click the event you get the error message again so you can not view the event.

OK - this is the weird part: All my old events work just fine. If I create a new event but for a past date it works fine. If I create a new event for more than 12 days in the future it works fine. It appears to be only for events created within the next 12 days.
I've never had problems creating events for the immediate future before - this is new behavior.

I don't have problems creating any other kind of content - only calendar events.
I tried updating the fullcalendar-plugin to the latest version 1.6.4 but no change in behavior.

I DID update the libraries API module from 7.x.1.0 to 7.x.2.1 recently but I do not see that listed as a dependency for FullCalendar so I'm assuming that's not a factor.

Stumped.

Comments

robbielink’s picture

robbielink CreditAttribution: robbielink commented

Update: Once an event that was generating the error code has passed (the day after) it becomes viewable without giving an error.
Have not been able to verify if the window for future dates giving an error is rolling forward or if it is static based on calendar date (which might indicate some sort of database corruption?)
Any suggestions on where to look further would be greatly appreciated. This is driving me crazy.
Calendar at http://robbielink.com/calendar and the upcoming events module will be on the left column if you scroll down. As of today, future events prior to December 15 generate an error.

robbielink’s picture

robbielink CreditAttribution: robbielink commented

UPDATE: After further testing I realized that the unviewable events were the same events generated in a block (created by Views). Any events listed in the Views block (upcoming events) generated the error whether they were clicked on in the Calendar View or the Upcoming Events Block. If I disabled the block (did not assign it a position on the page) the events became viewable with no error.
So this may not be a FullCalendar bug but I'm not sure where to go from here. Any suggestions?
I deleted the Upcoming Events View and created a new one (and let it create a new block) but that did not solve the problem.

robbielink’s picture

robbielink CreditAttribution: robbielink commented

Final Update:
Found a work around for my problem but leaving this issue open in case someone here thinks this may be a bug in FullCalendar.
What finally worked for me:
Set the "Upcoming Events" view block to be only visible on the home (i.e. ) page. I had originally had it set to be visible on all pages (even though it doesn't appear on the FullCalendar view page since the calendar takes up that entire view) and that was never a problem until recent core updates.
If anyone knows why this would make a difference I would love to know.
I'll take this issue over to the Views module and see if I can get any insight there.