Defect #5074

Error attempting to administer Custom Fields

Added by Nick Read over 8 years ago. Updated over 8 years ago.

Status:ClosedStart date:2010-03-15
Priority:HighDue date:
Assignee:-% Done:


Category:Custom fields
Target version:-
Resolution:Invalid Affected version:


Affects trunk at latest revision (r3586) but don't know when it was introduced.

Processing CustomFieldsController#index (for at 2010-03-15 11:49:59) [GET]
  Parameters: {"action"=>"index", "controller"=>"custom_fields"}
Rendering template within layouts/admin
Rendering custom_fields/index

ActionView::TemplateError (undefined method `[]' for nil:NilClass) on line #17 of app/views/custom_fields/_index.rhtml:
14:     <% (@custom_fields_by_type[tab[:name]] || []).sort.each do |custom_field| -%>
15:         <tr class="<%= cycle("odd", "even") %>">
16:             <td><%= link_to, :action => 'edit', :id => custom_field %></td>
17:             <td align="center"><%= l(CustomField::FIELD_FORMATS[custom_field.field_format][:name]) %></td>
18:             <td align="center"><%= image_tag 'true.png' if custom_field.is_required? %></td>
19:             <% if tab[:name] == 'IssueCustomField' %>
20:             <td align="center"><%= image_tag 'true.png' if custom_field.is_for_all? %></td>

    app/views/custom_fields/_index.rhtml:17:in `_run_rhtml_app47views47custom_fields47_index46rhtml_locals_index_object_tab'
    app/views/custom_fields/_index.rhtml:14:in `each'
    app/views/custom_fields/_index.rhtml:14:in `_run_rhtml_app47views47custom_fields47_index46rhtml_locals_index_object_tab'
    app/views/common/_tabs.rhtml:24:in `_run_rhtml_app47views47common47_tabs46rhtml_locals_object_tabs'
    app/views/common/_tabs.rhtml:23:in `each'
    app/views/common/_tabs.rhtml:23:in `_run_rhtml_app47views47common47_tabs46rhtml_locals_object_tabs'
    app/helpers/application_helper.rb:180:in `render_tabs'
    app/views/custom_fields/index.rhtml:3:in `_run_rhtml_app47views47custom_fields47index46rhtml'


#1 Updated by Nick Read over 8 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Ignore this - it's not a problem.

I had a patch that implemented very basic subtasking by having a new custom field type called "issue". I wasn't applying my patch any more because it's native to Redmine now (thanks!), but I hadn't removed the type from the database.

#2 Updated by Jean-Philippe Lang over 8 years ago

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

Also available in: Atom PDF