Vote #73350
完了After upgrade to 2.2.2 ticket list on some projects fails
0%
説明
On some projects I get just a 500 error with following debug output:
Completed 500 Internal Server Error in 145ms ActionView::Template::Error (comparison of Array with Array failed): 20: 21:22: <%= label_tag('add_filter_select', l(:label_filter_add)) %> 23: <%= select_tag 'add_filter_select', filters_options_for_select(query), :name => nil %> 24: 25: 26: app/helpers/queries_helper.rb:27:in `sort' app/helpers/queries_helper.rb:27:in `filters_options' app/helpers/queries_helper.rb:22:in `filters_options_for_select' app/views/queries/_filters.html.erb:23:in `_app_views_queries__filters_html_erb__1987712775818747131_9018920' app/views/issues/index.html.erb:18:in `block in _app_views_issues_index_html_erb___3250084186343222987_10921720' app/views/issues/index.html.erb:11:in `_app_views_issues_index_html_erb___3250084186343222987_10921720' app/controllers/issues_controller.rb:83:in `block (2 levels) in index' app/controllers/issues_controller.rb:82:in `index'
In development environment I tried to empty the queries table, does not help. The hint from "boards about this":http://www.redmine.org/boards/2/topics/35358 did not help for me.
So I did a workaround changing @app/helpers/queries_helper.rb@ and replaced line 27 with @sorted_options = query.available_filters do |a, b|@
I have no idea whats going wrong, it does not happen on all projects and does not depend on any queries stored. I'd upgraded from redmine 1.4.x to 2.2.2, all other stuff is working.
journals
Just tested with 2.2.3, too, same problem and workaround :(
--------------------------------------------------------------------------------
Could not reproduce but got the same error when :order key was missing in query filters.
This should no longer happen after r11372.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Is it possible that this fix isn't merged into 2.2-stable branch? there this error exists further and I didn't see that patch inside.
--------------------------------------------------------------------------------
As you could see in the target version, there is "2.3.0". This should answer your question that this issue will be fixed in 2.3-stable. ;-)
--------------------------------------------------------------------------------