v1.5 => Error 500 while loading Redmine

[Pierstoval]

I checked out v1.5 tag, and when I start redmine I have this error:

Started GET "/issues?sort=assigned_to%2Ctracker%3Adesc%2Cid%3Adesc%22" for 78.152.134.104 at 2014-11-19 12:24:00 +0100
Processing by IssuesController#index as HTML
  Parameters: {"sort"=>"assigned_to,tracker:desc,id:desc\""}
  Current user: pierstoval (id=1)
  Rendered queries/_filters.html.erb (64.6ms)
  Rendered queries/_columns.html.erb (7.8ms)
  Rendered issues/_list.html.erb (200.8ms)
  Rendered issues/_sidebar.html.erb (20.1ms)
  Rendered issues/index.html.erb within layouts/base (339.1ms)
Missing template, responding with 404
  Rendered common/error.html.erb within layouts/base (0.5ms)
Completed 500 Internal Server Error in 603.4ms

ActionView::Template::Error (Missing partial spent_time/javascript_report with {:locale=>[:fr, :en], :formats=>[:html], :handlers=>[:erb, :builder, :haml, :rsb]}. Searched in:
  * "redmine/plugins/redmine_spent_time_in_issue_description/app/views"
  * "redmine/plugins/redmine_dmsf/app/views"
  * "redmine/plugins/redmine_dashboard/app/views"
  * "redmine/plugins/redmine_custom_css/app/views"
  * "redmine/app/views"
):
    11: <%= stylesheet_link_tag 'rtl', :media => 'all' if l(:direction) == 'rtl' %>
    12: <%= javascript_heads %>
    13: <%= heads_for_theme %>
    14: <%= call_hook :view_layouts_base_html_head %>
    15: <!-- page specific tags -->
    16: <%= yield :header_tags -%>
    17: </head>
  lib/redmine/hook.rb:111:in `block in render_on'
  lib/redmine/hook.rb:61:in `block (2 levels) in call_hook'
  lib/redmine/hook.rb:61:in `each'
  lib/redmine/hook.rb:61:in `block in call_hook'
  lib/redmine/hook.rb:58:in `tap'
  lib/redmine/hook.rb:58:in `call_hook'
  lib/redmine/hook.rb:158:in `call_hook'
  app/views/layouts/base.html.erb:14:in `_app_views_layouts_base_html_erb___2785371365058861653_49587820'
  app/controllers/application_controller.rb:452:in `block (2 levels) in render_error'
  app/controllers/application_controller.rb:450:in `render_error'
  app/controllers/application_controller.rb:438:in `render_404'
  app/controllers/application_controller.rb:462:in `missing_template'

Maybe I made a mistake while upgrading the plugin ? :/

[Pierstoval]

Here is my environment:

Environment:
  Redmine version                2.5.2.stable.13338
  Ruby version                   1.9.3-p194 (2012-04-20) [x86_64-linux]
  Rails version                  3.2.19
  Environment                    production
  Database adapter               Mysql2
SCM:
  Subversion                     1.6.17
  Git                            1.7.10.4
  Filesystem                     
Redmine plugins:
  redmine_custom_css             0.1.4
  redmine_dashboard              2.3.1
  redmine_dmsf                   1.4.8 stable
  redmine_spent_time_in_issue_description 1.5

[Pierstoval]

Hmm, nevermind : I deleted the "redmine_spent_time_in_issue_description" config parameter and redmine automatically recreated it. Seems the migration did not went well, cuz the plugin parameters were not present in the database (that's why i "resetted" it )

Think this issue is solved for me, but maybe could you try to find a solution for other people who migrate from their version to master ?

[TravisSpangle]

I will confirm if the v1.5 tag is working as expected. I've had issues with the parameters in development as well.

[Pierstoval]

So is there any solution to avoid this problem when migrating ?

In fact the problem comes from the diff between "old" and new parameters, like display etc.

It works for me but a solution may be found, like defining default params in the app when they are not set in the db config line.

What do you think about it ?

[TravisSpangle]

Your error is from looking for the partial _javascript_report.html.erb. That file should not have existed for v1.5.

Using your version of Redmine and Ruby I had v1.5 checked out and only ran into issues with the translations file. I couldn't repo the parameters issue you experienced.

Because of the translation file issue I'm thinking of removing v1.5. Master should be stable enough that I can tag it.

[Pierstoval]

Yep, once translation files are OK, master is good !

For my problem, then it's solved ;)