b9a2a80a75
Currently, it's rather difficult to use OSEM and embed a schedule into another website. We currently use OSEM for the backend, but still use a different system for our main site. This change allows us to dynamically embed the schedule in our main website as well as allow us a simple way to get data for the use in mobile applications or similar. This limits the JSONP support to only GETS on json formatted requests. This prevents any XSS even though we don't require a authenticity token.
48 lines
1.2 KiB
Ruby
48 lines
1.2 KiB
Ruby
class ConferenceController < ApplicationController
|
|
before_filter :respond_to_options
|
|
load_and_authorize_resource find_by: :short_title
|
|
skip_before_filter :verify_authenticity_token, if: :json_request?
|
|
|
|
def json_request?
|
|
return false if request.request_method != 'GET'
|
|
return false if !request.format.json?
|
|
true
|
|
end
|
|
|
|
def index
|
|
@current = Conference.where('end_date >= ?', Date.current).order('start_date ASC')
|
|
@antiquated = @conferences - @current
|
|
end
|
|
|
|
def show; end
|
|
|
|
def schedule
|
|
@rooms = @conference.rooms
|
|
@events = @conference.events
|
|
@dates = @conference.start_date..@conference.end_date
|
|
|
|
if @dates == Date.current
|
|
@today = Date.current.strftime('%Y-%m-%d')
|
|
else
|
|
@today = @conference.start_date.strftime('%Y-%m-%d')
|
|
end
|
|
|
|
respond_to do |format|
|
|
format.html
|
|
format.json { render json: @conference.as_json, callback: params[:callback] }
|
|
end
|
|
end
|
|
|
|
def gallery_photos
|
|
@photos = @conference.photos
|
|
render 'photos', formats: [:js]
|
|
end
|
|
|
|
private
|
|
|
|
def respond_to_options
|
|
respond_to do |format|
|
|
format.html { head :ok }
|
|
end if request.options?
|
|
end
|
|
end
|