-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Batch Action greyed out and not working #1462
Comments
I am not able to get the batch actions working at all. I have done a bundle install (gem 'activeadmin') in gemfile, so it should be pulling master. The version shows that I DO have 0.4.4 but I am missing some of the files such as batch_actions.rb. I have deleted, and re-installed the gem, i've done gem update, and plain old bundle install multiple times, but it doesn't appear to be grabbing the master. Any ideas on what I can do to fix this? |
@smikkelsen ActiveAdmin 0.4.4 (the latest gem) is definitely not pulling from master. Update your gemfile to use ActiveAdmin from master if you want batch actions. |
@ashleywysocki Could you force the option to "true" in the initializer? |
@pcreux Thanks a lot for your reply. I still cannot get it working. I updated the gemfile to this: I assumed that both would pull from master. "ActiveAdmin 0.4.4 (the latest gem) is definitely not pulling from master." Thanks again for your help! |
To get the latest ActiveAdmin code use this line in your Gemfile: gem 'activeadmin', :git => 'git://github.com/gregbell/active_admin.git' |
I have the same issue. The checkbox appear but it does nothing. |
+1 same issue, I have the batch action drop down button greyed out... Confirmed I have 0.4.4 latest. |
0.4.4 is not the latest. What's on GitHub is the latest. See my earlier comment for how to get the latest code from GitHub. For those who already have that line in their Gemfile, you can run |
I have a resource with this:
It's showing the selectable column and it's showing the batch action button. It's disabled but when I select at least one row in the selectable column it becomes active. When I press the button, there's nothing in it. If a remove the I even put the line It may be a problem when rendering the view? Please help, I need this ASAP. My configuration:
|
I found the problem in my case. I had:
but |
Had same problem, found as java script issue; solved with, rails generate active_admin:assets and this worked !! |
I am having the same issue where the batch action is greyed out for all my resources. In active_admin.rb, I have:
This is my index file for my resource Image:
I am using the latest version of activeadmin (0.5.1) and also ran "rails generate active_admin:assets" Please help! |
@ttseng, you need to include index do
selectable_column
column :id
# ... |
great this works for me. thanks! |
hm, actually, when I try to implement my own batch action, I am getting the following error: Missing template admin/images/batch_action |
@ttseng, as always, The problem with the example is it doesn't explicitly tell the controller what to render after the batch action is finished. You need to do something along these lines: batch_action :stuff do |ids|
# use those IDs to do stuff here
redirect_to collection_path, :notice => "We did stuff!"
end If you don't tell the controller what to do, it will implicitly look for a view template to render based on the current controller action. Hence the error, "Missing template admin/images/batch_action" |
I'm currently working on cleaning up the documentation, and at the very least I've fixed the problem I mentioned earlier. Closing this for now. |
I'm using the latest version of Active Admin (gemfile leads to gem "activeadmin", :git => "git://github.com/gregbell/active_admin.git") and in my Active Admin site, the Batch Action option is showing. However it's greyed out and it's not set to false in the config file. I tried to add a batch again to my mode programs:
But that's not showing up either and I'm not sure if it's the right syntax (the :hot confuses me). Does anyone know how to fix this?
The text was updated successfully, but these errors were encountered: