0.9.1 - Attempt to filter by custom issue item - internal error

Added by John Reynolds over 11 years ago

Hello,

At any of our issue pages, when attempting to filter on any custom issue item, I receive the following error:

Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your redMine administrator for assistance.

It doesn't seem to matter if it is the only filter, or mixed in with others. I've tried several different customs that are text, list, etc. - all produce the same results.

AFAIK, the upgrade from .0.8.7 to .0.9.1 went off without a hitch.
Running the required software, and MYSQL.

Is there any way I can do a trace on Redmine to determine the issue and post more helpful information? Sorry, not a rails/ruby dev.

Thank you,

&J

Replies (3)

RE: 0.9.1 - Attempt to filter by custom issue item - internal error - Added by Andrew Leaf over 11 years ago

Hello John,

After running this query, what does your log/production.log say?

I had a similar issue in the RC of 0.9, but it was remedied with 0.9.1.

Cheers,

Andrew

RE: 0.9.1 - Attempt to filter by custom issue item - internal error - Added by John Reynolds over 11 years ago

Andrew,

Thanks for taking a look. Here is a copy/paste from generating the error.


Processing IssuesController#index (for 10.10.100.67 at 2010-02-02 01:05:34) [GET]
  Parameters: {"action"=>"index", "query_id"=>"65", "controller"=>"issues"}
Rendering template within layouts/base
Rendering issues/index.rhtml
Completed in 918ms (View: 513, DB: 70) | 200 OK [http://project1/issues?query_id=65]

Processing IssuesController#index (for 10.10.100.67 at 2010-02-02 01:05:53) [POST]
  Parameters: {"group_by"=>"priority", "set_filter"=>"1", "action"=>"index", "authenticity_token"=>"XryxQjcDzV+HhUJtZYrEgaVtrJ/X7QqofyRUYjevqEs=", "fields"=>["status_id", "priority_id", "assigned_to_id", "cf_5"], "operators"=>{"question_assigned_to_id"=>"=", "start_date"=>"<t+", "watcher_id"=>"=", "estimated_hours"=>"=", "created_on"=>">t-", "priority_id"=>"=", "cf_5"=>"=", "cf_6"=>"=", "cf_7"=>"~", "done_ratio"=>"=", "question_asked_by_id"=>"=", "updated_on"=>">t-", "subject"=>"~", "assigned_to_id"=>"=", "cf_8"=>"=", "tracker_id"=>"=", "cf_9"=>"~", "due_date"=>"<t+", "author_id"=>"=", "status_id"=>"o"}, "values"=>{"question_assigned_to_id"=>["me"], "start_date"=>[""], "watcher_id"=>["me"], "estimated_hours"=>[""], "created_on"=>[""], "priority_id"=>["5", "6", "7"], "cf_5"=>["Controls"], "cf_6"=>[""], "cf_7"=>[""], "done_ratio"=>[""], "question_asked_by_id"=>["me"], "updated_on"=>[""], "subject"=>[""], "assigned_to_id"=>["me"], "cf_8"=>["Light"], "tracker_id"=>["1"], "cf_9"=>[""], "due_date"=>[""], "author_id"=>["me"], "status_id"=>["1"]}, "controller"=>"issues", "query"=>{"column_names"=>["tracker", "priority", "subject", "category", "fixed_version", "due_date", "done_ratio", "status", "cf_6"]}}

ArgumentError (wrong number of arguments (6 for 5)):
  app/models/query.rb:392:in `sql_for_field'
  app/models/query.rb:392:in `statement'
  app/models/query.rb:374:in `each_key'
  app/models/query.rb:374:in `statement'
  app/models/query.rb:413:in `issue_count'
  app/controllers/issues_controller.rb:68:in `index'
  passenger (2.2.4) lib/phusion_passenger/rack/request_handler.rb:91:in `process_request'
  passenger (2.2.4) lib/phusion_passenger/abstract_request_handler.rb:206:in `main_loop'
  passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:376:in `start_request_handler'
  passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:334:in `handle_spawn_application'
  passenger (2.2.4) lib/phusion_passenger/utils.rb:182:in `safe_fork'
  passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:332:in `handle_spawn_application'
  passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in `__send__'
  passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in `main_loop'
  passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:195:in `start_synchronously'
  passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:162:in `start'
  passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:213:in `start'
  passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:261:in `spawn_rails_application'
  passenger (2.2.4) lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
  passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application'
  passenger (2.2.4) lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
  passenger (2.2.4) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
  passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:254:in `spawn_rails_application'
  passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:153:in `spawn_application'
  passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:286:in `handle_spawn_application'
  passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in `__send__'
  passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in `main_loop'
  passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:195:in `start_synchronously'

Rendering /var/www/redmine/public/500.html (500 Internal Server Error)

RE: 0.9.1 - Attempt to filter by custom issue item - internal error - Added by Andrew Leaf over 11 years ago

John,

How many filters do you have in place when you do this? It looks like there might be 6 and that is causing the problem, however, I couldn't reproduce it on my install. I recently upgraded from 0.8.3 > 0.9 RC > 0.9.1.

However, do you have the "Question" plugin installed? Try disabling that filter in the filter list to see if that corrects the problem.

(1-3/3)