Project

General

Profile

Actions

Defect #4364

closed

Filtering by a List custom field gives Internal Server Error

Added by Rahul Vaidya over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2009-12-08
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

Experienced in latest trunk. I have a List custom field with multiple values, and whenever I try to query issues using this field I get

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.

Actions #1

Updated by Jean-Philippe Lang over 14 years ago

Can not reproduce. Please read SubmittingBugs, I need your stack trace.

Actions #2

Updated by Rahul Vaidya over 14 years ago

Sorry about that.

Using SQLite.

Stack trace:

ArgumentError (wrong number of arguments (6 for 5)):
app/models/query.rb:379:in `sql_for_field'
app/models/query.rb:379:in `statement'
app/models/query.rb:361:in `each_key'
app/models/query.rb:361:in `statement'
app/controllers/issues_controller.rb:64:in `index'

Rendering C:/Ruby/redmine-trunk/redmine/public/500.html (500 Internal Server Error)

Actions #3

Updated by Jean-Philippe Lang over 14 years ago

Rahul Vaidya wrote:

Experienced in latest trunk.

This trace shows that you're not using latest trunk. Please re-read SubmittingBugs.

Actions #4

Updated by Rahul Vaidya over 14 years ago

I am using r3137 and am experiencing this problem (with same stack trace).

Windows 2003 Server x64
Ruby 1.8.6
Rails 2.3.4
Running on Mongrel
I cannot run script/about, I do not have MySQL installed and I get errors about missing libmysql.dll

All the steps in http://www.redmine.org/wiki/redmine/RedmineUpgrade have been followed (I have an upgrade script that does everything).

Actions #5

Updated by Jean-Philippe Lang over 14 years ago

There's no call to Query#sql_for_field at source:/trunk/app/models/query.rb@3137#L379.

Actions #6

Updated by Rahul Vaidya over 14 years ago

  • Status changed from New to Resolved

How bizarre...

I deleted all the Ruby source files in the app folder and restored from SVN (svn update never gave any sort of error message) and things seem to work now.

Sorry for all the trouble.

Actions #7

Updated by Jean-Philippe Lang over 14 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid

OK, thanks.

Actions

Also available in: Atom PDF