Closed GoogleCodeExporter closed 8 years ago
It seems this is purposely built into the code, as the ReadMe documentation
states
"Repeating events are created using using (5# Vacation) within normal events.
The
code looks up the previous months and applies carry-over events to the current
month.
It may increase the calendar load time as it looks back 15 days into the
previous
month for carry over repeating events."
I presume increasing this number, especially on quite busy calendars, may
increase
load times to unacceptable / timeout levels.
Original comment by ev.delen...@gmail.com
on 6 Jul 2009 at 6:15
It is currently hardcoded as user "ev.delen.work" states because of
performance. The
repeating logic is very slow because its all wiki code based, not SQL based.
I've
played with a few options, but there really isnt a great way to do it without
making
the calendar talk to MediaWiki at the SQL level.
Once I get some time, I'll see what I can do to improve this more.
Thanks
Eric
Original comment by kenyu73
on 6 Jul 2009 at 6:39
updated the code in 3.7.8
It defaults 1/2 (15 days) into the previous month. I added an option
to 'enablerepearevents=<number>' to override the default.
Original comment by kenyu73
on 4 Aug 2009 at 10:38
Original issue reported on code.google.com by
osikt...@googlemail.com
on 18 Jun 2009 at 3:38