Can't get rid of the action_class and input_class deprecations until finishing #114. Will need to update the formtastic initializer to add the input class and action class initializers as explained in https://github.com/justinfrench/formtastic/wiki/Upgrading-to-Formtastic-3.1
Put it behind authorization since it includes author's emails. The previous accepted sessions was not showing sessions. It should be decomissioned as this moves to another application. Once done this controller (accepted_sessions) can be seriously improved. This closes #163.
Quite some changes in the way to view your own reviews but pretty much includes the same information plus the feedback. Also re-used the idea of presenting a summary of all session data in the organizer feedback visualization to better use space. Also did a small performance improvement in the reviews visualization page.
It is now easier to invite people that were reviewers in previous conferences. This is mostly how organizers will be able to check on feedback given to reviewers (for issue #159) so that they can get a sense of how people are doing. Next steps are: 1) Improve this new page as well as the reviewer 'My reviews' page to provide an overview of the feedback received. 2) Create the reviewer show page that will have detailed information on the feedback as well as their reviews. Link that from the summarized previous view.
Json extension is the default so no need to expect it. Removed the super class API Controller as it didn't make sense for the sessions. Migrated the gravatar_url to the application controller since it was needed for the JSON. Show only for now. Will probably want an API for accepted sessions for a given conference at some point. And maybe an RSS feed URL to listen for changes on those sessions/conference. Will have to create another issue for that.
Devise is compatible with rails 4 strong parameters. It detects if strong parameters are available and, if so, it uses that to filter which parameters should be allowed to go through the registration and sign in pages. As I added strong parameters (the gem) for issue #101, devise stopped accepting our custom parameters for user registrations. This allows them to be set.