Project

General

Profile

Actions

Bug #4712

closed

Editing organization gives undefined method `parent_taxonomy_selected_location_path'

Added by Dominic Cleal about 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Organizations and Locations
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When organisations are enabled, but not locations, you can get errors trying to resolve routes for the "other" taxonomy when editing an organisation.

ActionView::Template::Error (undefined method `parent_taxonomy_selected_location_path' for #<#<Class:0x000000077546d8>:0x00000007adf000>):
    5:   <%= select_f f, :parent_id, taxonomy.class.where("id NOT IN (#{taxonomy.subtree_ids.join(',')})").order(:title), :id, :title, { :include_blank => true },
    6:                { :label => _('Parent'), :onchange => 'parent_taxonomy_changed(this);',
    7:                  :help_inline => :indicator,
    8:                  :'data-url' => parent_taxonomy_selected_location_path(taxonomy.id)
    9:                } %>
    10: 
    11:   <%= text_f f, :name %>
  app/views/taxonomies/_form.html.erb:8:in `block in _app_views_taxonomies__form_html_erb___4317518605146758171_66773220'
  app/helpers/layout_helper.rb:248:in `form_for'
  app/views/taxonomies/_form.html.erb:3:in `_app_views_taxonomies__form_html_erb___4317518605146758171_66773220'
  app/views/taxonomies/edit.html.erb:4:in `_app_views_taxonomies_edit_html_erb___4188087350678574917_64430140'
  app/controllers/concerns/foreman/controller/taxonomies_controller.rb:67:in `block in edit'
Actions #1

Updated by Ivan Necas about 10 years ago

This is a blocker for testing Katello provisioning

Actions #2

Updated by Og Maciel about 10 years ago

This blocks QE UI auto as well

Actions #3

Updated by Ohad Levy about 10 years ago

Og Maciel wrote:

This blocks QE UI auto as well

As a workaround please enable locations too. It should be on by default IMHO.

Actions #4

Updated by Og Maciel about 10 years ago

Even with location enabled I still see this issue. nm

Actions #5

Updated by Dominic Cleal about 10 years ago

Og Maciel wrote:

Even with location enabled I still see this issue.

Works fine with locations enabled here. Did you restart Foreman or Apache after changing the configuration?

Actions #6

Updated by Lukas Zapletal about 10 years ago

Works fine with locations enabled here. Did you restart Foreman or Apache after changing the configuration?

Yeah the Og's one is different I think (Katello needs to be enabled for that).

Actions #7

Updated by Ohad Levy about 10 years ago

Lukas Zapletal wrote:

Yeah the Og's one is different I think (Katello needs to be enabled for that).

can you elaborate what is the difference? do we have a different stack trace when locations are enabled?

Actions #8

Updated by Lukas Zapletal about 10 years ago

Sure, the one Og referred to was https://bugzilla.redhat.com/show_bug.cgi?id=1076562 I assume.

Actions #9

Updated by Mike McCune about 10 years ago

The issue outlined in https://bugzilla.redhat.com/show_bug.cgi?id=1076562 (moved to POST) is no longer occurring but the situation outlined in this issue still is.

Actions #10

Updated by Joseph Magen almost 10 years ago

  • Status changed from New to Assigned
  • Assignee set to Joseph Magen
Actions #11

Updated by Dominic Cleal almost 10 years ago

  • Status changed from Assigned to Ready For Testing
  • Target version set to 1.8.4
Actions #12

Updated by Dominic Cleal almost 10 years ago

  • translation missing: en.field_release set to 4
Actions #13

Updated by Joseph Magen almost 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF