Rails 3 :method=> :delete doesn't work in Internet Explorer

Question

I am going through the rails 3 tutorial at railstutorial.org. I have just created an extremely simple scaffold Users.

The scaffold-generated destroy link does not work in Internet Explorer. It redirects to the show action instead of deleting the user.

This problem only happens in IE9 and IE8 (the only IE versions I've tested so far) The problem DOES NOT happen in Firefox. Can anyone tell me why this is happening?

The view:

<%= link_to 'Destroy', user, :confirm => 'Are you sure?', :method => :delete %>

Generated HTML:

<a href="/users/1" data-confirm="Are you sure?" data-method="delete" rel="nofollow">Destroy</a>

The controller:

def destroy
    @user = User.find(params[:id])
    @user.destroy

    respond_to do |format|
      format.html { redirect_to(users_url) }
      format.xml  { head :ok }
    end
end

I have this issue too, but only using IE9. IE8 works for me, IE9 gives me the same symptoms as you if I use the short hostname (I'm running in development mode here), but if I use the FQDN of the dev server, the object gets deleted and the development log shows a redirect to the index, but then a request to the get for the now-deleted object. — hmallett, Jul 25 '11 at 13:39

score 8 · Answer 1 · answered Dec 02 '11 at 00:07

8

In Rails 3.1 with the asset pipeline, all the javascript is in application.js. So, rather than :defaults, you need "application".

<%= javascript_include_tag "application" %>

answered Dec 02 '11 at 00:07

George Shaw

1,771
1
18
32

After upgrading and comparing my layout to the default one "application" was missing. This works for me. – ayckoster Dec 16 '11 at 17:08
Yeah this works. Can't believe the things we have to change from even 3.0 to 3.1. – manojlds Jan 10 '12 at 17:49
Can someone explain why this fixes the problem? Is rails using javascript to change something about the html? – Jason Axelson Jul 12 '12 at 02:14
I had this problem on any browser. Adding the javascript_indlude_tag solved it. – Lucas Pottersky Aug 30 '12 at 15:58

score 2 · Answer 2 · answered Sep 22 '10 at 21:22

2

Make sure you have <%= javascript_include_tag :defaults %>

JS is now unobtrusive in rails 3, so the include is required to make it work.

answered Sep 22 '10 at 21:22

theschmitzer

12,190
11
41
49

I do have this line in my default application layout, the problem still exists – louis11 Sep 23 '10 at 14:26

score 2 · Answer 3 · answered Nov 19 '10 at 13:54

Replace public/javascripts/rails.js of your application with this one:

https://github.com/rails/prototype-ujs/raw/master/src/rails.js

This is updated recently (2010/11/13).

The rails.js bundled with Rails 3.0.0/3.0.1 does not work well on Internet Explorer.

score 2 · Answer 4 · answered Apr 01 '11 at 15:55

You need to upgrade your prototype distribution to 1.7 instead of 1.7rc2 (which doesn't have full support for IE 9). The latest Rails gem (at time of writing( in the gem repo is bundling 1.7rc2. Go to the prototype homepage, download the new 1.7 release and replace this with the bundled prototype.js.

score 2 · Answer 5 · answered Jul 25 '11 at 14:02

2

I couldn't get it to work with IE9 with the default javascript libraries, so I installed jquery-rails and it works just fine. Not perhaps the ideal solution, but if it works...

answered Jul 25 '11 at 14:02

hmallett

1,537
1
10
11

score 1 · Answer 6 · answered Jun 06 '13 at 07:24

This is probably because the loading of your script (rails.js and/or application.js) happens in head. At script execution time, there are no elements in your DOM with the attributes data-confirm and data-method.

So, the solution is to move the javascript tag to the end of <body>. At this time, the DOM has most likely been loaded and the javascript will find your elements.

score 1 · Answer 7 · answered Jan 17 '11 at 14:21

1

By default, new rails projects are created with Prototype javascript libraries, with some prototype-specific helper functions in "public/javascript/rails.js". The scaffolding relies on some of these helpers to handle some things, like destroying a record, since there isn't a good javascript-free way of making a DELETE request, etc.

Make sure that your pages are loading both the javascript libraries and the "rails.js" file, which are needed to make the scaffolding work (see theschmitzer's answer, or check in Firebug).

Second, if you are using jQuery, install the 'jquery-rails' gem and then run "rails g jquery:install". This will remove the Prototype libraries, install the jQuery libraries, and update the helpers to use jQuery.

answered Jan 17 '11 at 14:21

user421944

89
1
2

1

I had this problem but in any browser and using jquery along with prototype was the culprit. This solution worked. – Jorge May 05 '11 at 03:59
I did not have any other library, not sure why I was getting this error. But I followed this one and it worked! thanks @user421944 – gouravtiwari21 Nov 03 '11 at 17:21
error on "rails g jquery:install": Could not find generator 'jquery:install' – David Ljung Madison Stellar Aug 02 '16 at 20:52

score 1 · Answer 8 · answered May 05 '11 at 22:02

1

Try replacing your javascript default include with:

<%= javascript_include_tag "jquery" %>
<%= javascript_include_tag "jquery.min" %>
<%= javascript_include_tag "rails" %>

after following the steps above to get the latest jquery.js, jquery.min.js, and rails.js. That worked for me, anyway.

Or, replace the meaning of :defaults in application.rb:

config.action_view.javascript_expansions[:defaults] = %w(jquery jquery.min rails)

And then your application layout can still look have

    <%= javascript_include_tag :defaults %>

answered May 05 '11 at 22:02

Adam Ehven

119
1
3

having same issue on Linux and Rails 3. Have tried all day to get it working and the only thing that worked was separating the tags as above. weird behaviour. delete works again, live search works, sorting works. works in firefox and chrome and safari on linux and mac, works on chrome.firefox on windows havent tried IE. Thanks @Adam Ehven – IanN Jul 30 '11 at 11:41
forgot to mention I never edited the config/application.rb and it works. Maybe not the most graceful way or the best DRY, but at this point I dont care – IanN Jul 30 '11 at 11:42

score 0 · Answer 9 · answered Aug 05 '14 at 00:35

I notice that in rails 4, link_to puts the :method as a html attribute "data-method" but :confirm goes to an attribute "confirm" where the javascript needs it to be "data-confirm".

Not sure if this is a bug in rails, but you can work around it by doing this:

<%= link_to 'Destroy', user, :data => {:confirm => 'Are you sure?'}, :method => :delete %>

Stefan Pettersson · Answer 10 · 2010-12-06T11:16:05.997

I experience the same problem, regardless of web browser.

theschmitzer's answer didn't help me.

I found that as long as I am using the jquery javascript library the destroy method in the controller is never called.

In my case I had a conflict between the javascript libraries (jQuery and Prototype) which was hard to figure out for such a newbie. I changed completely to jQuery - as in the end of this railcast: http://railscasts.com/episodes/205-unobtrusive-javascript

score 0 · Answer 11 · edited May 23 '17 at 12:13

0

I had the same problem. I was using the <%= javascript_include_tag :defaults %> as well as the jQuery library. When I removed the jQuery library, things worked. Also, you could use noConflict().

edited May 23 '17 at 12:13

Community

1
1

answered Dec 15 '10 at 07:55

Zabba

64,285
47
179
207

Rails 3 :method=> :delete doesn't work in Internet Explorer

11 Answers11

Linked