| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
multiple local and web calendars, in any number and combination. The
calendar name will also be displayed correctly, instead of only
displaying a single calendar name when multiple calendars are chosen.
|
|
|
|
| |
the comment in config.inc.php.
|
|
|
|
|
| |
array for $ALL_CALENDARS_COMBINED even if the global $allow_webcals
was not 'yes'.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
by name, where the calendar file would fail to be found. Included a comment
explaining what is going on.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
$calendar_path and the new iCal calendar repository structure. The
calendars are still referenced by calendar name, so all URLs are unchanged.
Refactored the date parsing code out of ical_parser.php and into
date_functions.php. Minor logic changes to the parser to correctly
populate the TODO date and time values.
Refactored the calendar name code into a new getCalendarName() function,
since calendar names may no longer be determined solely by filename if
using an iCal repository. Template code updated to match.
Added calls to stripslashes() for calendar text data, such as the summaries
and descriptions. Also put stripslashes() into people data, since people's
names may contain escaped characters.
|
| |
|
| |
|
|
|
|
| |
pop-up correctly - now it passes the time used in the array as part of the openevent call.
|
| |
|
| |
|
|
|
|
| |
year view - prior to this, you'd only get events for 3 months, which three months depending on what getdate was set to. So, basically year.php never displayed all the year events, unless you had the cache turned on.
|
|
|
|
| |
well. Also cleaned up some unused code I missed the last time, and a minor spelling fix in a comment.
|
|
|
|
| |
to event popup, and added two small patches.
|
|
|
|
| |
work with cpath multiple calendar directories
|
|
|
|
| |
template.php; add cpath to other files
|
| |
|
| |
|
|
|
|
| |
simplifies the code.
|
|
|
|
| |
default expectations weren't to have things get cut off.
|
|
|
|
| |
This started out as a "simple" bug, and ended up being a complete rewrite of overlapping_events. The changes to template.php are to fix a minor rendering bug that was part of the overlap issue, and the changes to ical_parser are because the api to checkOverlap changed.
|
|
|
|
| |
Relatively simple fix to a complex, that changes the weekly code to render to the window of $next_date_range -> $next_date_range + $interval weeks. Took me a while to wrap my head around this one - I knew what the solution was, but wasn't sure if it handles everything. Still not 100% sure about the edge cases, though.
|
|
|
|
| |
wasn't a need for a new function, and it also simplified the code. Update the config text to make more sense, but we should note things in the README when we release 2.0.
|
|
|
|
| |
PRIVATE/CONFIDENTIAL events.
|
|
|
|
| |
fixed a comment that referenced the old name.
|
|
|
|
| |
Trivial option to support non-standard FTP ports.
|
|
|
|
| |
calendar as appropriate.
|
|
|
|
| |
The bug was when generating $recur_array, the code assumes for each pass, you're filling in $recur_array from $next_range_time to $next_range_time + $interval $freq_type, in this case $next_range_time to $next_range_time + 1 year. However, the previous code used the fixed year of $next_range time, making the range filled into $recur_event per pass (jan 01, year of $next_range_time) to (dec 31st, year of $next_range_time). There was a hack that tried to fix this by saying "assume next year if it's jan/feb", trying to compensate, but it just semi-papered over the issue since the ranges still didn't match up. The fix was to make sure the ranges actually did match up, by adjusting the year used each month. This also meant that a bunch of events outside of start/end_range are no longer rendered. Since the window now matches on a monthly basis, it will still generate events slightly outside of start/end_range, but it should now render correctly in all cases (the extra events are just slightly wasted space, but less wasted space than before). Note that this fixes a bunch of problems w/ rendering yearly events in dec/jan/feb (the year border), beyond the SF bug.
|
| |
|
| |
|
|
|
|
| |
order for events starting before day start)
|
| |
|
| |
|
|
|
|
| |
directories selected by REQUEST).
|
| |
|
|
|
|
| |
correctly.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixed.
|
| |
|
| |
|
| |
|
| |
|