GCalendar Block Error

Posted: Tue Nov 25, 2008 5:06 pm

I'm just working on my development site - so not a pressing issue.

I have block-GCalendar.php enabled on the home page, and rather than showing the calendar, it's full of the following error:

Code:

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/xxxxxx/public_html/modules/GCalendar/getMonthlyEvents.php on line 163

Line 163 looks like this:

Code:

                  if ($ts >= $startTs && ($noEndDate || $ts <= $endTs) && !in_ar


ray($n, $exceptions[$eventId]))


                  {


                     $events[$n][] = array('id' => $eventId, 'title' => $title, 


'category' => $category);


                  }

Regular Joined: Sep 12, 2006 Posts: 58 Location: Dsm, IA

Gremmie fixed it, see this thread:
http://sourceforge.net/forum/forum.php?thread_id=2480969&forum_id=654086

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

webservant, please be careful not to post your root path in a public forum... I removed it from your post.

Posted: Tue Nov 25, 2008 7:21 pm

Doh! - Thanks!

Interestingly, I have four themes customized from NukeNews. When I fixed the css, then everything works. However, when I use fisubice theme, I get the error. It's really odd.

I'll try the mod that you posted, and see what effect it has on both themes.

Posted: Tue Nov 25, 2008 7:37 pm

Well, there are new css entries in fisubice! However, the module update works, and does no harm to my themes. Yeah!

Thanks for the quick reply kguske :clap:

registered · Posted: Thu Nov 27, 2008 8:06 am

I have taken Gremmie's fix and applied it to the next patch release of RN.

Posted: Thu Nov 27, 2008 8:11 am

Thanks montego!

Client Joined: Jul 18, 2003 Posts: 977

montego wrote:

I have taken Gremmie's fix and applied it to the next patch release of RN.

I have RN 2.3.01 and it was still throwing that error. I uploaded the fix and it works now.

Posted: Fri Apr 03, 2009 7:22 am

blith, RN 2.3.01 was cut in Oct, 2008, so my comment still stands. I just checked our code repository and I had checked that code fix in on 11/27/2008.