Depending on the math, either 2015 has 53 weeks, or 2016 does... In this Calendar, it happens to be 2016. Unfortunately, I completely forgot to program 53 weeks into the Weekly Calendar display. This version fixes that. You will now be able to access week 53 on the Weekly Calendar.
BUG FIX: Fixed a bug that made it so the Event Queue did not get properly populated by multiple occurrences.
Events will now get unique CSS classes based on what keywords are linked to said event... This will allow you to color events on your calendars based on what categories/keywords they belong to. CSS classes are styled in the form of "atendoKey#".
Event Queue bubble will now show up properly outside of the calendar views.
Event Threads will now give proper Facebook OpenGraph data.
Added a Search Handler for events! Events will now show up when you use the search engine. For this, a new content type called "event" has been added to handle for this. You will need to rebuild the search index for events if you want previously submitted events to be in the search index.
A "date" field has been added to events. This is a private field that is automatically updated whenever any changes happen to an event, or occurrences are added/edited for an event. The entire purpose of this field is to order the event in search results.
BUG FIX: This update fixes a major bug that prevents events from showing more than one occurrence per monthly view. For instance, if you had an event set to repeat every week, this bug, which was introduced in the last update, would only show the first occurrence of the event, and not the others.
BUG FIX: Fixed an issue where if RSVPs were disabled for an event, it would still show "0 Going" on the occurrence list.
Added an option to reverse the order of timezones on event pages. By default, when viewing an event's page, it will show the times in the timezone set for that event; if a user wished to see the times adjusted for their local timezone, all they needed to do was mouse over the times, and it will show a tooltip of the adjusted times. This new option reverses this, so event pages will show the user's local times, and then the event's local times on mouseover. This is an option I do not recommend using as it will end up inciting confusion.