|
From: Rob L. <ro...@ro...> - 2007-09-10 01:34:03
|
Looks like my problem is solved. I nuked the Foo.GED_upcoming.php cache file, causing it to be regenerated. Ideally, that file would be automatically invalidated on an upgrade (or at least this upgrade), but looking through the code a little more closely did make the fix obvious. Viva open source! Rob On 9/9/07 6:07 PM, Rob Lanphier wrote: > I just upgraded from 3.3.8(?) to 4.1 last night, and then from 4.1 to > 4.1.1 today. The first upgrade went fine as near as I could tell, but > the second upgrade caused a problem. I'm now noticing this call stack > in "On this day" and "Upcoming events" infoboxes: > > ERROR 8: Undefined index: jd > 0 Error occurred on line 1438 of file functions_print_lists.php in > function print_events_table > 1 called from line 223 of file todays_events.php in function > print_todays_events > 2 called from line 1 of file index.php(385) : eval()'d code in function eval > 3 called from line 385 of file index.php > > I'm going to poke around in the code and see if I notice anything > obvious, other than observing that this is new code in 4.1.1. I haven't > yet tried reimporting my GEDCOM file, which I may do if I don't catch > something obvious. > > Rob > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Phpgedview-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpgedview-talk > |
