-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 Error after creating schedule #21
Labels
Comments
I'll take a look...
… On Mar 6, 2018, at 2:10 AM, mecrider ***@***.***> wrote:
Creating a new schedule brings me to a 500 page with the following logs:
I, [2018-03-05T18:31:44.646204 #23484] INFO -- : Started POST "/template-scheduling/schedules" for 192.168.10.183 at 2018-03-05 18:31:44 -0600
I, [2018-03-05T18:31:44.649085 #23484] INFO -- : Processing by ConcertoTemplateScheduling::SchedulesController#create as HTML
I, [2018-03-05T18:31:44.649274 #23484] INFO -- : Parameters: {"utf8"=>"✓", "authenticity_token"=>"xHOlN85WYKHr0I0L7wKZkoF6kkWIoSUR9gUxwyRR0loj8oMCY
rY9fncr0UcmEeM6RqQcvKl9HGZY1qC6/PfE0w==", "schedule"=>{"screen_id"=>"1", "start_time"=>{"date"=>"03/05/2018", "time"=>"6:00am"}, "end_time"=>{"date"=>
"03/06/2118", "time"=>"5:59am"}, "config"=>{"display_when"=>"2", "feed_id"=>"7", "scheduling_criteria"=>"custom", "from_time"=>"7:30am", "to_time"=>"8
:30am"}, "template_id"=>"1"}, "commit"=>"Create Schedule"}
I, [2018-03-05T18:31:44.827250 #23484] INFO -- : Redirected to http://concerto-server/template-scheduling/schedules/2
I, [2018-03-05T18:31:44.827549 #23484] INFO -- : Completed 302 Found in 178ms (ActiveRecord: 121.6ms)
I, [2018-03-05T18:31:44.971360 #23484] INFO -- : Started GET "/template-scheduling/schedules/2" for 192.168.10.183 at 2018-03-05 18:31:44 -0600
I, [2018-03-05T18:31:44.972831 #23484] INFO -- : Processing by ConcertoTemplateScheduling::SchedulesController#show as HTML
I, [2018-03-05T18:31:44.972931 #23484] INFO -- : Parameters: {"id"=>"2"}
I, [2018-03-05T18:31:45.018166 #23484] INFO -- : Rendered vendor/bundle/ruby/2.3.0/gems/concerto_template_scheduling-0.0.7/app/views/concerto_template_scheduling/schedules/show.html.erb within layouts/application (8.2ms)
I, [2018-03-05T18:31:45.018459 #23484] INFO -- : Completed 500 Internal Server Error in 45ms (ActiveRecord: 6.9ms)
F, [2018-03-05T18:31:45.050673 #23484] FATAL -- :
ActionView::Template::Error (765: unexpected token at 'custom'):
40: %>
41:
<%= t(:feed) %>: <%= feed_name %>
42: <% elsif @schedule.config['display_when'].to_i == ConcertoTemplateScheduling::Schedule::DISPLAY_AS_SCHEDULED %>
43:
***@***.***_in_words %>
44: <% end %>
45:
<%= ConcertoTemplateScheduling::Schedule.human_attribute_name(:from_time)%>: <%= @schedule.config['from_time'] %>
46:
<%= ConcertoTemplateScheduling::Schedule.human_attribute_name(:to_time)%>: <%= @schedule.config['to_time'] %>
app/controllers/application_controller.rb:114:in `set_time_zone'
I, [2018-03-05T18:31:45.051236 #23484] INFO -- : Processing by ErrorsController#render_error as HTML
I, [2018-03-05T18:31:45.051303 #23484] INFO -- : Parameters: {"id"=>"2"}
I, [2018-03-05T18:31:45.060977 #23484] INFO -- : Rendered errors/error_generic.html.erb within layouts/no-topmenu (0.9ms)
I, [2018-03-05T18:31:45.062118 #23484] INFO -- : Rendered elements/_head.html.erb (0.1ms)
I, [2018-03-05T18:31:45.062826 #23484] INFO -- : Completed 500 Internal Server Error in 11ms (Views: 3.1ms | ActiveRecord: 2.8ms)
At that point navigating back to the screen the template was scheduled for also brings me to a 500 error:
I, [2018-03-05T18:37:20.692113 #23484] INFO -- : Started GET "/screens/1" for 192.168.10.183 at 2018-03-05 18:37:20 -0600
I, [2018-03-05T18:37:20.694074 #23484] INFO -- : Processing by ScreensController#show as HTML
I, [2018-03-05T18:37:20.694173 #23484] INFO -- : Parameters: {"id"=>"1"}
I, [2018-03-05T18:37:20.746581 #23484] INFO -- : Rendered vendor/bundle/ruby/2.3.0/gems/concerto_hardware-0.8/app/views/concerto_hardware/screens/_
screen_link.html.erb (0.4ms)
W, [2018-03-05T18:37:20.748066 #23484] WARN -- : ConcertoPlugin: use_plugin_ability: No Ability found for ConcertoTemplateScheduling
I, [2018-03-05T18:37:20.763769 #23484] INFO -- : Rendered vendor/bundle/ruby/2.3.0/gems/concerto_template_scheduling-0.0.7/app/views/concerto_templ
ate_scheduling/screens/_screen_link.html.erb (15.5ms)
I, [2018-03-05T18:37:20.763891 #23484] INFO -- : Rendered screens/show.html.erb within layouts/application (28.0ms)
I, [2018-03-05T18:37:20.764191 #23484] INFO -- : Completed 500 Internal Server Error in 70ms (ActiveRecord: 10.0ms)
F, [2018-03-05T18:37:20.787288 #23484] FATAL -- :
ActionView::Template::Error (765: unexpected token at 'custom'):
47: <% end %>
48:
49: <% elsif schedule.config['display_when'].to_i == ConcertoTemplateScheduling::Schedule::DISPLAY_AS_SCHEDULED %>
50:
<%= schedule.schedule_in_words %>
51: <% end %>
52: <% if schedule.config['display_when'].to_i != ConcertoTemplateScheduling::Schedule::DISPLAY_NEVER %>
53:
<%= schedule.config['from_time'] %> - <%= schedule.config['to_time'] %>
app/models/concerto_plugin.rb:139:in block (2 levels) in render_view_hook' app/models/concerto_plugin.rb:135:ineach'
app/models/concerto_plugin.rb:135:in block in render_view_hook' app/models/concerto_plugin.rb:133:inrender_view_hook'
app/views/screens/show.html.erb:2:in _app_views_screens_show_html_erb___3536034979308501794_42659000' app/controllers/screens_controller.rb:24:inshow'
app/controllers/application_controller.rb:114:in `set_time_zone'
I, [2018-03-05T18:37:20.787934 #23484] INFO -- : Processing by ErrorsController#render_error as HTML
I, [2018-03-05T18:37:20.788031 #23484] INFO -- : Parameters: {"id"=>"1"}
I, [2018-03-05T18:37:20.797366 #23484] INFO -- : Rendered errors/error_generic.html.erb within layouts/no-topmenu (0.8ms)
I, [2018-03-05T18:37:20.798413 #23484] INFO -- : Rendered elements/_head.html.erb (0.1ms)
I, [2018-03-05T18:37:20.798986 #23484] INFO -- : Completed 500 Internal Server Error in 11ms (Views: 2.8ms | ActiveRecord: 2.5ms)
The only fix I have found to let me get back to the screen page is to log into the mysql database and delete the record for the schedule.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@mecrider this is working fine for me under my development environment. I will check the vm shortly. One thing to keep in mind is that once you install this plugin you need to restart the webserver so that it can run the database migration to create the scheduling table that it uses.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Creating a new schedule brings me to a 500 page with the following logs:
At that point navigating back to the screen the template was scheduled for also brings me to a 500 error:
The only fix I have found to let me get back to the screen page is to log into the mysql database and delete the record for the schedule.
The text was updated successfully, but these errors were encountered: