Releases: calagator/calagator
Releases · calagator/calagator
v2.0.0.pre.1
- [!] Upgrade to Rails 5 with minimum Ruby version 2.5.
- [!] Remove inappropriate terminology such as master, slave, and blacklist. Existing
blacklist.txt
files will need to be renamed todenylist.txt
when upgrading a Rails app that uses earlier versions of this gem. - [!] Meetup and Facebook integration is no longer supported due to changes to these services' APIs. Their API keys should be removed from your configuration.
- Upgrade development dependencies.
- Move CI testing to GitHub Actions.
- Upgrade additional dependencies for security updates.
- Improve accessibility by making required fields clearer to screen reader users.
- Remove Meetup parser (#681)
- Remove use of SortedSet in Source::Parser (#682)
- Remove Facebook parser (#683)
v2.0.0.pre.0
- [!] Upgrade to Rails 5 with minimum Ruby version 2.5.
- [!] Remove inappropriate terminology such as master, slave, and blacklist. Existing
blacklist.txt
files will need to be renamed todenylist.txt
when upgrading a Rails app that uses earlier versions of this gem. - Upgrade development dependencies.
- Move CI testing to GitHub Actions.
- Upgrade additional dependencies for security updates.
- Improve accessibility by making required fields clearer to screen reader users.
v1.1.0
v1.0.0
- [!] This release completely changes the way in which Calagator is distributed, moving from a standalone Rails app to a Rails engine. Instead of deploying Calagator instance from a modified version of this code, Calagator is now included as a gem within a new Rails app. Please review the updated installation instructions in INSTALL.md.
- If you are upgrading a site based on an earlier version of Calagator, please drop us a line. We've recently upgraded calagator.org and can help to point you in the right direction.
- [THEME] The theme system has been removed, favoring the view overriding functionality provided by Rails engines. This works much the same way as the previous theme system, allowing any Calagator view to be overridden by creating a file at the corresponding path within your app's
app/views/calagator
directory. - [SETTING] The YAML-based settings and secrets mechanisms have been replaced with an initializer inside the host application. See INSTALL.md for details.
- [MIGRATION] Database migrations are now installed into your host application.
- [DEPENDENCY] Upgraded to Rails 4.2.11.1.
- Numerous additional dependency upgrades and bugfixes.
v1.0.0.rc3
- [!] Facebook now requires an access token to read public event data from their graph API. Added
Calagator.facebook_access_token
configuration option and support for this authentication. - Fixed
calagator
executable and install process - Fixed handling of events with no end time when editing
- Fixed formatting of search field and edit forms
- Fixed cache key generation issue
- Fixed recent changes functionality
- Fixed tag editing
- Fixed an XSS vunlerability
- Improved error handling around search
- Disabled auth token checking for JSON requests
- Refactored and deleted unused code
- Improved documentation
v1.0.0.rc2
- Improved installation and configuration workflow
- Improved documentation
- Dropped support for Rails 3.2
v1.0.0.rc1
- [!] This release completely changes the way in which Calagator is distributed, moving from a standalone Rails app to a Rails engine. Instead of deploying Calagator instance from a modified version of this code, Calagator is now included as a gem within a new Rails app. Please review the updated installation instructions in INSTALL.md.
- If you are upgrading a site based on an earlier version of Calagator, please drop us a line. We've recently upgraded calagator.org and can help to point you in the right direction.
- [THEME] The theme system has been removed, favoring the view overriding functionality provided by Rails engines.
This works much the same way as the previous theme system, allowing any Calagator view to be overridden by creating a file at the corresponding path within your app'sapp/views/calagator
directory. - [SETTING] The YAML-based settings and secrets mechanisms have been replaced with an initializer inside the host application. See INSTALL.md for details.
- [MIGRATION] Database migrations are now installed into your host application.
v0.20150320
- [!] Dropped support for Ruby 1.8.7, and 1.9.3. Use Ruby 2.0+.
- Switched from outdated v2 Google Maps to a more flexible leaflet-based mapping system.
- [!] New mapping settings have been added to secrets.yml
If you wish to keep using Google as your map provider, you'll need to set your provider and add an API key to secrets.yml. - [!] The "venues_google_map_options" setting in settings.yml has been renamed to venues_map_settings.
- [!] Loading Google API keys from config/geocoder_api_keys.yml has been deprecated. Use config/secrets.yml instead.
- [THEME] References to the #google_map div in stylesheets should be changed to #map.
- [THEME] Theme authors need to require the mapping javascript files in the layout:
Add<%= javascript_include_tag *mapping_js_includes %>
just before your application javascript_include_tag.
- [!] New mapping settings have been added to secrets.yml
- Updated to Rails 3.2.21
- Rewrote deployment scripts using Capistrano 3
- Streamlined navigation, collapsing "Overview" and "Browse Events"
- Added the ability to lock individual events from editing to prevent vandalism
- Added a unified admin tool list (/admin) with optional password protection. Includes changelog, duplicate squashing, and event locking.
- Added prettier tag URLs (e.g. /events/tag/ruby, and /venues/tag/office)
- Added friendlier error pages with a confused alligator
- Added tag icons
- Added database seeds to ease development
- Fixed search loading and reindexing
- Squashed wiggly bugs
- Gloriously increased test coverage
- Copiously refactored, improved code style, and swept up unused code
- Updated vagrant configuration to Ubuntu 14.04 and Ruby 2.1
v0.20131020
- We now use the Rails 3.2 asset pipeline to compile assets.
- [!][THEME] Theme maintainers need to make a few small changes when upgrading.
See https://github.com/calagator/calagator/wiki/Asset-Pipeline-Theme-Upgrade for details.
- [!][THEME] Theme maintainers need to make a few small changes when upgrading.
- Improved venue search, backed by by SQL or Sunspot.
- [!] If you're running a Calagator instance using Sunspot for search, you'll want to run
rake sunspot:reindex
to index your venues.
- [!] If you're running a Calagator instance using Sunspot for search, you'll want to run
- Added Twitter and Facebook share buttons to event pages
- Added ability to export all events at a given venue to iCalendar
- Fixed Google geocoder: v2 was deprecated, using v3 now
- Assed microformats2 markup to event pages
- Removed reliance on the rails default /:controller/:action/:id route
- [DEPENDENCY] Upgraded formtastic and other dependencies
- Updated spam blacklist.
v0.20130717
- [DEPENDENCY] Upgraded to rails 3.2.13.
- Fixed #30: Relax markdown emphasis parsing to avoid adding emphasis to words_containing_underscores.
- Fixed #22 and #33: avoid double-output of cache block for filtered events.
- Fixed #35: Use 'medium' git log format for footer version number.
- Fixed #36, #37: Limit the number of links in event descriptions to three.
- Fixed Google Code issue #280: Strip whitespace from venue fields.
- Fixed #38: Fixed display of events with no end time
- Added Schema.org support to event markup.
- Updated spam blacklist.