Version 2.1<br />----------------<br />- Adds the ability for members of a special FEU group to edit or delete any event from the frontend.<br />- Ads the ability to bulk delete expired events.<br />- New installs use InnoDB instead of MyISAM which allows for data integrity.<br><br />Version 2.0<br />----------------<br />- Removes the previously deprecated calendar view.<br />- Migrates all template functionality into the CMSMS 2.0 Layout scheme. All templates for CGCalendar are now available in DesignManager.<br />- Moves all settings controls into their own navigation item in the admin console.<br />- Removes the upcominglist template type, and replaces it with the standard list template type. Note: This may cause compatibility issues. Pastlist and upcominglist views no longer support pagination.<br />- Adds support for a day view.<br />- Unifies all summary views (year, month, day, upcominglist, pastlist) to use the same eventlist templates. The format of this template has changed significantly.<br />- No longer pass the eventtemplate parameter from the summary view into detail urls to potentially allow for pretty urls in detail (event) views. Use the {cge_module_hint} tag instead.<br />- No longer use the use_session parameters for list views. The default template allows for scrolling by ajax.<br />- No longer use the displayforday parameter for pastlist or upcominglist. Upcominglist automatically includes events for the current day, as does pastlist.<br />- No longer use the unique_only parameters for the pastlist and upcominglist views as the event name cannot be assumed to be a key. Post filtering in the list template may be a valid solution for this if on a particular site it can be assumed that the event name is unique.