Undefined method 'all_options_admin_users_path'

[davidwparker]

Having issues getting this to work.

Note: we have 3x different namespaces for different Active Admin interfaces. (Admin2, Super, Custom).

admin2/flag.rb

  form do |f|
    f.semantic_errors
    f.inputs do
      f.input :assigned_user, as: :searchable_select, ajax: { resource: User }
      f.input :admin_notes
    end
    f.actions
  end

admin2/user.rb

searchable_select_options(scope: User.all, text_attribute: :username)

When that's setup like that, I get the following error:

undefined method `all_options_admin_users_path' for #<#<Class:0x00007fc178072b50>:0x00007fc178062b88>
Did you mean?  all_options_admin2_users_path
               all_options_admin2_users_url

Suggestions? Thanks!

[davidwparker]

Follow up:

Note that when I change this line:

activeadmin-searchable_select/lib/activeadmin/searchable_select/select_input_extension.rb

Line 48 in c9373a9

template.polymorphic_path([:admin, ajax_resource_class],

to
template.polymorphic_path([:admin2, ajax_resource_class],

it renders!

But now I get the console error:

Uncaught Error: Option 'ajax' is not allowed for Select2 when attached to a <select> element.

1. It would be nice to have this library pass in which namespace it is within.
2. Not sure about this new error yet.

[tf]

Hi,

a PR making the namespace configurable is definitely welcome. I'd suggest passing it in as part of the ajax option:

f.input(:additional_category,
        as: :searchable_select,
        ajax: {
          namespace: :admin2, 
          resource: Category 
        })

As an extra, one could look into using the name of the current namespace as a default. This should work the same way we currently determine the default resource.

Regarding the second error: What version of select2-rails are you using?

[davidwparker]

Cool, I'll take a look into making a PR!

In regards to the latter, it's whatever was autoinstalled with this gem, so (https://github.com/codevise/activeadmin-searchable_select/blob/master/activeadmin-searchable_select.gemspec#L34)? I'll take a look when I get more time to switch back to this branch.

[tf]

Great!

I can only find the mentioned error message in the source code of the 3.5 verion, though. In 4.0 I no longer find it. Could you check your Gemfile.lock or even the Select2 version comment in the js file inside the browser, to see which version you are using.

[davidwparker]

Here's what I'm seeing via the Gemfile

    activeadmin-searchable_select (1.0.1)
      activeadmin (~> 1.x)
      jquery-rails (>= 3.0, < 5)
      select2-rails (~> 4.0)
    select2-rails (4.0.3)
      thor (~> 0.14)

But when I look at the JS source, I see this:

Version: 3.5.1 Timestamp: Tue Jul 22 18:58:56 EDT 2014

It appears our app was using an older version of select2 that was overriding select2-rails. I'll be checking with my team to see if we can upgrade...

[davidwparker]

Also, removing the old one does allow for things to work, albeit the CSS is a little off.

Forward progress!

[tf]

Importing active_admin/searchable_select.scss should include the required styles.

[davidwparker]

Again, we had the old version of 3.5 select2 SCSS. Removing that fixed the CSS problem!

Thanks again! I'll see about that PR still.

[davidwparker]

Oh, one more thing to suggest. It would be nice to be able to query against multiple text_attributes in a single select2.

For example:

searchable_select_options(
    scope: User.all,
    text_attribute: [:email, :username]
  )

Would search against email and username (using OR).

I don't know Ransack very well (I should research more!), but I figure this is the place I should be looking?
https://github.com/codevise/activeadmin-searchable_select/blob/master/lib/activeadmin/searchable_select/option_collection.rb#L90

[tf]

Looking at this Ransack wiki page, something like the following should do the trick:

searchable_select_options(scope: User.all,
                          text_attribute: :username,
                          filter: lambda |term, scope|
                            scope.ransack(email_or_username_cont: term).result
                          end)

[davidwparker]

Works perfectly thanks! When I get a PR up, I'll be sure to throw something like that in the documentation too, as it's helpful to know.

[davidwparker]

Here you go, thanks for the help! #4