Problem with issue list page after upgrading to version 2.1.0

Added by Florian Krauthan over 7 years ago


I've upgraded today redmine from version 1.4 to 2.1.0. It looks like that everything works except the issue list pages. If I go to a page like this I get a 500 error in the browser. And the production log gives me this error:

Started GET "/projects/***/issues" for *** at 2012-10-08 02:04:32 +0200
Processing by IssuesController#index as HTML
  Parameters: {"project_id"=>"***"}
  Current user: fkrauthan (id=3)
Completed 500 Internal Server Error in 22ms

ActiveRecord::SubclassNotFound (The single-table inheritance mechanism failed to locate the subclass: 'ScrumblerIssueCustomField'. This error is raised because the column 'type' is reserved for storing the class in case of inheritance. Please rename this column if you didn't intend it to be used for storing the inheritance class or overwrite CustomField.inheritance_column to use another column for that information.):
  app/models/query.rb:906:in `add_associations_custom_fields_filters'
  app/models/query.rb:308:in `available_filters'
  app/helpers/queries_helper.rb:127:in `build_query_from_params'
  app/helpers/queries_helper.rb:95:in `retrieve_query'
  app/controllers/issues_controller.rb:56:in `index'

My environment is this:

  Redmine version                          2.1.2.stable.10570
  Ruby version                             1.9.3 (x86_64-linux)
  Rails version                            3.2.8
  Environment                              production
  Database adapter                         Mysql2
Redmine plugins:
  no plugin installed

Replies (1)

RE: Problem with issue list page after upgrading to version 2.1.0 - Added by Jean-Baptiste Barth over 7 years ago

Solved on IRC, most plugins that define custom fields introduce this problem when you uninstall or remove them.

One solution is to remove manually the custom fields in a rails console production :

CustomField.where(:type => "ScrumblerIssueCustomField").each(&:destroy)

Please note that it will remove all those custom fields, so you'll lose data (though it might be data you don't want anymore). It's strongly recommended to backup your database before doing such operations.