Last 7 days

• Dec 10, 2009

  issue 43 (Clash with jquery's slideUp and slideDown methods) commented on by grande   -   same problem here ...

  same problem here ...

Earlier this year

• Nov 11, 2009

  issue 44 (Element.show is not a function) commented on by internetchris1   -   Element.show is prototype syntax. It should be... $('tag-spinner-#{category.id}').show()

  Element.show is prototype syntax. It should be... $('tag-spinner-#{category.id}').show()
• Oct 29, 2009

  issue 43 (Clash with jquery's slideUp and slideDown methods) commented on by cosmos99123   -   yep, I'm having the same exact problem .. and I'm also using the work around as described above.

  yep, I'm having the same exact problem .. and I'm also using the work around as described above.
• Sep 19, 2009

  issue 27 (Effects not working in Opera) commented on by gatis.tomsons   -   On Opera 10.0 it's working

  On Opera 10.0 it's working
• Jul 30, 2009

  issue 44 (Element.show is not a function) reported by wlaver   -   What steps will reproduce the problem? 1. use link_to_remote tag 2. 3. What is the expected output? What do you see instead? Having issues with link_to_remote_tag Element.show. I am getting the following error. "Error: Element.show is not a function" <%= link_to_remote "more ...", :url => show_all_tags_path(:category => category.name), :update => { }, :loading => "Element.show('tag-spinner-#{category.id}')", :complete => "Element.hide('tag-spinner-#{category.id}')" %> What version of the product are you using? On what operating system? jrails, but am using jQuery v1.3.2 and jquery-ui Please provide any additional information below.

  What steps will reproduce the problem? 1. use link_to_remote tag 2. 3. What is the expected output? What do you see instead? Having issues with link_to_remote_tag Element.show. I am getting the following error. "Error: Element.show is not a function" <%= link_to_remote "more ...", :url => show_all_tags_path(:category => category.name), :update => { }, :loading => "Element.show('tag-spinner-#{category.id}')", :complete => "Element.hide('tag-spinner-#{category.id}')" %> What version of the product are you using? On what operating system? jrails, but am using jQuery v1.3.2 and jquery-ui Please provide any additional information below.
• Jul 10, 2009

  issue 43 (Clash with jquery's slideUp and slideDown methods) reported by b.cand...@pobox.com   -   > What steps will reproduce the problem? 1. Install jrails 2. Replace jquery with jquery-1.3.2 3. Write javascript using slideDown/slideUp animations I found that slideDown and slideUp were working wrongly: slideDown was making the page jump to create a hole, and then filling the hole. Conversely, slideUp was scrolling out the content and then collapsing the hole. It has taken me about half a day to nail this down, and it turns out to be down to jrails; jrails is replacing jquery's slideDown and slideUp methods with its own methods of the same name. As a workaround, I have patched jrails.js to rename slideUp to jslideUp and slideDown to jslideDown. There must be better names :-) I'm not sure why jrails is doing this, given that even jquery-1.2.6 already has slideDown and slideUp methods. Maybe there should be a run-time flag to choose either behaviour. > What version of the product are you using? On what operating system? I am using jrails from subversion (r96) with the supplied jrails-1.2.6 replaced by jrails-1.3.2, running under Rails 2.3.2 under Ubuntu 9.04 and ruby 1.8.7. Firefox 3.0.11 demonstrates the differing slide behaviours.

  > What steps will reproduce the problem? 1. Install jrails 2. Replace jquery with jquery-1.3.2 3. Write javascript using slideDown/slideUp animations I found that slideDown and slideUp were working wrongly: slideDown was making the page jump to create a hole, and then filling the hole. Conversely, slideUp was scrolling out the content and then collapsing the hole. It has taken me about half a day to nail this down, and it turns out to be down to jrails; jrails is replacing jquery's slideDown and slideUp methods with its own methods of the same name. As a workaround, I have patched jrails.js to rename slideUp to jslideUp and slideDown to jslideDown. There must be better names :-) I'm not sure why jrails is doing this, given that even jquery-1.2.6 already has slideDown and slideUp methods. Maybe there should be a run-time flag to choose either behaviour. > What version of the product are you using? On what operating system? I am using jrails from subversion (r96) with the supplied jrails-1.2.6 replaced by jrails-1.3.2, running under Rails 2.3.2 under Ubuntu 9.04 and ruby 1.8.7. Firefox 3.0.11 demonstrates the differing slide behaviours.
• Jun 21, 2009

  issue 42 ( I found and fixed what seems to be a bug in form_remote_tag...) reported by lucianorosa   -   What steps will reproduce the problem? 1. Use form_remote_tag with both :loading and :loaded parameters 2. Both :load and :loaded functionas are added to beforeSend callback 3. Create a form with form_remote_tag with both :loaded and :loading parameters and take a look at the generated Ajax code What is the expected output? What do you see instead? :loading and :loaded should be called respectively before and after the Ajax request What version of the product are you using? On what operating system? 0.4.0, on both Linux and Leopard Please provide any additional information below. JRails 0.4.0 When using jrails I noticed that the :loaded parameter in the form_remote helper was being added to the $.ajax "beforeSend" callback along with the :loading parameter causing them to be both executed when loading. :loaded should be added to the "complete" callback. Here is the fix... code: /vendors/plugins/jrails/lib/jrails.rb in the build_callbacks method change At the top take the ",:loaded" out... [:uninitialized,:loading,:loaded].each do |key| options[:beforeSend] << (options[key].last == ';' ? options.delete (key) : options.delete(key) << ';') if options[key] end So it will look like this [:uninitialized,:loading].each do |key| options[:beforeSend] << (options[key].last == ';' ? options.delete (key) : options.delete(key) << ';') if options[key] end add this line options[:complete] = options.delete(:loaded) if options[:loaded] before options.delete(:beforeSend) if options[:beforeSend].blank? deploy the new jrails.rb and restart your server.

  What steps will reproduce the problem? 1. Use form_remote_tag with both :loading and :loaded parameters 2. Both :load and :loaded functionas are added to beforeSend callback 3. Create a form with form_remote_tag with both :loaded and :loading parameters and take a look at the generated Ajax code What is the expected output? What do you see instead? :loading and :loaded should be called respectively before and after the Ajax request What version of the product are you using? On what operating system? 0.4.0, on both Linux and Leopard Please provide any additional information below. JRails 0.4.0 When using jrails I noticed that the :loaded parameter in the form_remote helper was being added to the $.ajax "beforeSend" callback along with the :loading parameter causing them to be both executed when loading. :loaded should be added to the "complete" callback. Here is the fix... code: /vendors/plugins/jrails/lib/jrails.rb in the build_callbacks method change At the top take the ",:loaded" out... [:uninitialized,:loading,:loaded].each do |key| options[:beforeSend] << (options[key].last == ';' ? options.delete (key) : options.delete(key) << ';') if options[key] end So it will look like this [:uninitialized,:loading].each do |key| options[:beforeSend] << (options[key].last == ';' ? options.delete (key) : options.delete(key) << ';') if options[key] end add this line options[:complete] = options.delete(:loaded) if options[:loaded] before options.delete(:beforeSend) if options[:beforeSend].blank? deploy the new jrails.rb and restart your server.
• Apr 13, 2009

  issue 41 (jRails error when attempting to use Rails ajax helpers) commented on by brentmc79   -   I figured out the problem. I was passing in a url as an argument, but as a string, not as a hash with a :url key. I understand that I was passing in option parameter incorrectly, but I still think there ought to be some sort of option checking and meaningful error messages.

  I figured out the problem. I was passing in a url as an argument, but as a string, not as a hash with a :url key. I understand that I was passing in option parameter incorrectly, but I still think there ought to be some sort of option checking and meaningful error messages.
• Apr 12, 2009

  issue 41 (jRails error when attempting to use Rails ajax helpers) reported by brentmc79   -   What steps will reproduce the problem? 1. Install the latest jRails from SVN 2. Use link_to_remote, remote_function, or any Rails ajax helper 3. Attempt to render the page What is the expected output? What do you see instead? It should render properly, but intead I get this: index 116545 out of string with this stack trace: vendor/plugins/jrails/lib/jrails.rb:197:in `[]=' vendor/plugins/jrails/lib/jrails.rb:197:in `build_callbacks' vendor/plugins/jrails/lib/jrails.rb:119:in `options_for_ajax' vendor/plugins/jrails/lib/jrails.rb:51:in `remote_function' vendor/plugins/facebox_render/lib/facebox_render_helper.rb:4:in `facebox_link_to' The use of the facebox plugin can be ignored. I was receiving the same error on link_to_remote before I ever installed the facebox plugin. What version of the product are you using? On what operating system? jRails 0.4 OS X Rails 2.2.2 Please provide any additional information below.

  What steps will reproduce the problem? 1. Install the latest jRails from SVN 2. Use link_to_remote, remote_function, or any Rails ajax helper 3. Attempt to render the page What is the expected output? What do you see instead? It should render properly, but intead I get this: index 116545 out of string with this stack trace: vendor/plugins/jrails/lib/jrails.rb:197:in `[]=' vendor/plugins/jrails/lib/jrails.rb:197:in `build_callbacks' vendor/plugins/jrails/lib/jrails.rb:119:in `options_for_ajax' vendor/plugins/jrails/lib/jrails.rb:51:in `remote_function' vendor/plugins/facebox_render/lib/facebox_render_helper.rb:4:in `facebox_link_to' The use of the facebox plugin can be ignored. I was receiving the same error on link_to_remote before I ever installed the facebox plugin. What version of the product are you using? On what operating system? jRails 0.4 OS X Rails 2.2.2 Please provide any additional information below.
• Mar 25, 2009

  issue 40 (sortable_element doesn't send a hash with sortable elements,...) commented on by jcontonio   -   I can verify that this is the case. I am having the same problems. Updated to the latest jquery-ui as well.

  I can verify that this is the case. I am having the same problems. Updated to the latest jquery-ui as well.
• Mar 06, 2009

  issue 40 (sortable_element doesn't send a hash with sortable elements,...) reported by ralfgraf   -   What steps will reproduce the problem? Create a sortable-thingy like it's explained in Railscast 147 and try to sort. What is the expected output? What do you see instead? sortable_element only sends the id of the one sortable thingy moved in the sortable-list as params to the controller, it should be a hash containing all elements like it's done with prototype. From my dev-log, with prototype, my sortable stuff is "lessonelements": Parameters: {"authenticity_token"=>"BLA", "lessonelements"=>["1", "2"]} Same action with jrails: Parameters: {"authenticity_token"=>"BLA", "lessonelements"=>"2"} What version of the product are you using? On what operating system? The current jrails from github, tried the one from http://ennerchi.googlecode.com/svn/trunk/plugins/jrails before, makes no difference. The docs don't make clear which one is the newer one to use.

  What steps will reproduce the problem? Create a sortable-thingy like it's explained in Railscast 147 and try to sort. What is the expected output? What do you see instead? sortable_element only sends the id of the one sortable thingy moved in the sortable-list as params to the controller, it should be a hash containing all elements like it's done with prototype. From my dev-log, with prototype, my sortable stuff is "lessonelements": Parameters: {"authenticity_token"=>"BLA", "lessonelements"=>["1", "2"]} Same action with jrails: Parameters: {"authenticity_token"=>"BLA", "lessonelements"=>"2"} What version of the product are you using? On what operating system? The current jrails from github, tried the one from http://ennerchi.googlecode.com/svn/trunk/plugins/jrails before, makes no difference. The docs don't make clear which one is the newer one to use.
• Feb 18, 2009

  issue 39 (using link_to_remote with do block) reported by m...@acidfx.org   -   What steps will reproduce the problem? 1. <% link_to_remote "val" :values do %>.... <% end %> Doesn't create output. What is the expected output? What do you see instead? The same like the default link_to method What version of the product are you using? On what operating system? jRails 0.4.0 Please provide any additional information below. I attached the jrails.rb with the fix which works for me fine. I hope it helps. Sorry for my english.

  What steps will reproduce the problem? 1. <% link_to_remote "val" :values do %>.... <% end %> Doesn't create output. What is the expected output? What do you see instead? The same like the default link_to method What version of the product are you using? On what operating system? jRails 0.4.0 Please provide any additional information below. I attached the jrails.rb with the fix which works for me fine. I hope it helps. Sorry for my english.
• Feb 06, 2009

  issue 38 (Update Home Page Install instructions to use new Rake task) reported by m...@seebq.com   -   Update the Home page's install instructions to instruct the user to use: rake jrails:install:javascripts instead of: "Then copy the javascript files in the plugin folder to your javascripts directory." If you provide source to the web, page, I'd be happy to help! Thanks!

  Update the Home page's install instructions to instruct the user to use: rake jrails:install:javascripts instead of: "Then copy the javascript files in the plugin folder to your javascripts directory." If you provide source to the web, page, I'd be happy to help! Thanks!
• Jan 06, 2009

  issue 36 (form_remote_tag didn't recognize Element.show) commented on by iamghetto   -   Can I check out this out of the tree and fix it? It appears to be very simple fix - all the prototype code was not removed from that methods output.

  Can I check out this out of the tree and fix it? It appears to be very simple fix - all the prototype code was not removed from that methods output.

Older

• Dec 11, 2008

  issue 36 (form_remote_tag didn't recognize Element.show) reported by phil.meads   -   What steps will reproduce the problem? this rails code, which works with prototype, didn't work with jrails <% form_remote_tag :url => { :action => "getSql" }, :update => "sqlstmt", :before => "Element.show('spinner')", :complete => "Element.hide('spinner') " do %> firebug says Element.show not a valid function it works w/out ref to Element <% form_remote_tag :url => { :action => "getSql" }, :update => "sqlstmt" do %> on mac/ff 3.0.4

  What steps will reproduce the problem? this rails code, which works with prototype, didn't work with jrails <% form_remote_tag :url => { :action => "getSql" }, :update => "sqlstmt", :before => "Element.show('spinner')", :complete => "Element.hide('spinner') " do %> firebug says Element.show not a valid function it works w/out ref to Element <% form_remote_tag :url => { :action => "getSql" }, :update => "sqlstmt" do %> on mac/ff 3.0.4
• Dec 04, 2008

  issue 35 (Observe Field doesn't take an :on option.) reported by scidept   -   Observe Field doesn't accept the :on option. It looks like it's commented out in jrails.rb I think it's because the javascript doesn't accept an option for a different event type (such as blur or focus).

  Observe Field doesn't accept the :on option. It looks like it's commented out in jrails.rb I think it's because the javascript doesn't accept an option for a different event type (such as blur or focus).
• Dec 02, 2008

  r96 (default to post ) committed by aaronchi   -   default to post

  default to post
• Dec 02, 2008

  r95 (reset ) committed by aaronchi   -   reset

  reset
• Dec 02, 2008

  r94 (update to form observer ) committed by aaronchi   -   update to form observer

  update to form observer
• Dec 02, 2008

  r93 (declare with 'var' for local variables ) committed by aaronchi   -   declare with 'var' for local variables

  declare with 'var' for local variables
• Dec 02, 2008

  r92 (fixed when radio button observed and old value gimmick ) committed by aaronchi   -   fixed when radio button observed and old value gimmick

  fixed when radio button observed and old value gimmick
• Dec 02, 2008

  r91 (Simply changed the init.rb to define the jquery var for noCo...) committed by aaronchi   -   Simply changed the init.rb to define the jquery var for noConflict() purposes. Could really do with this being set outside of the plugin.

  Simply changed the init.rb to define the jquery var for noConflict() purposes. Could really do with this being set outside of the plugin.
• Nov 10, 2008

  issue 34 (Support for jquery.ajaxQueue) reported by erol.fornoles   -   May I suggest adding support for the jquery.ajaxQueue plugin via :type from the options hash, using the additional values below: :queue = Queue the AJAX requests, submitting new requests only after the previous one has returned [:single, #port] = Ignore additional AJAX requests until the first instance has returned There are two versions of the ajaxQueue plugin AFAIK: the "official" plugin and the one pre-packaged in jquery.autocomplete. I have a patch which works with the later and will gladly share it if this feature request is approved.

  May I suggest adding support for the jquery.ajaxQueue plugin via :type from the options hash, using the additional values below: :queue = Queue the AJAX requests, submitting new requests only after the previous one has returned [:single, #port] = Ignore additional AJAX requests until the first instance has returned There are two versions of the ajaxQueue plugin AFAIK: the "official" plugin and the one pre-packaged in jquery.autocomplete. I have a patch which works with the later and will gladly share it if this feature request is approved.
• Oct 31, 2008

  issue 33 (quick fix for observing a field of the type 'search') reported by kozymedia   -   What steps will reproduce the problem? 1. observe a field with a type of 'search' What is the expected output? What do you see instead? Only on blur the form submits. Should be on every key change. What version of the product are you using? On what operating system? current Please provide any additional information below. a quick fix, at line 62: - else if (obs && field.type == 'text' || field.type == 'textarea') e = 'keyup'; + else if (obs && field.type == 'text' || field.type == 'textarea' || field.type == 'search') e = 'keyup'; thanks

  What steps will reproduce the problem? 1. observe a field with a type of 'search' What is the expected output? What do you see instead? Only on blur the form submits. Should be on every key change. What version of the product are you using? On what operating system? current Please provide any additional information below. a quick fix, at line 62: - else if (obs && field.type == 'text' || field.type == 'textarea') e = 'keyup'; + else if (obs && field.type == 'text' || field.type == 'textarea' || field.type == 'search') e = 'keyup'; thanks
• Sep 15, 2008

  r90 (options[:method] ||= "post") committed by aaronchi   -   options[:method] ||= "post"

  options[:method] ||= "post"
• Sep 14, 2008

  r89 (add enable/disable) committed by aaronchi   -   add enable/disable

  add enable/disable
• Sep 14, 2008

  issue 32 ([patch] link_to_remote with 'post' method doesn't send empty...) Status changed by aaronchi   -  

  Status: Fixed

  Status: Fixed
• Sep 14, 2008

  r88 (add an empty data string so that all posts have a content le...) committed by aaronchi   -   add an empty data string so that all posts have a content length

  add an empty data string so that all posts have a content length
• Sep 14, 2008

  r87 (add some more options to sortables/droppables for proper js ...) committed by aaronchi   -   add some more options to sortables/droppables for proper js quoting

  add some more options to sortables/droppables for proper js quoting
• Sep 14, 2008

  r86 (make sure insertion is a string) committed by aaronchi   -   make sure insertion is a string

  make sure insertion is a string
• Sep 07, 2008

  r85 (update jsmin) committed by aaronchi   -   update jsmin

  update jsmin
• Sep 07, 2008

  r84 (add note about scriptaculous effect names) committed by aaronchi   -   add note about scriptaculous effect names

  add note about scriptaculous effect names
• Sep 07, 2008

  r83 (fix fadeToggle) committed by aaronchi   -   fix fadeToggle

  fix fadeToggle
• Sep 07, 2008

  r82 (mirror scriptaculous for effect names) committed by aaronchi   -   mirror scriptaculous for effect names

  mirror scriptaculous for effect names
• Sep 07, 2008

  r81 (js cleanup) committed by aaronchi   -   js cleanup

  js cleanup
• Sep 07, 2008

  r80 (add support for page[:element_id].visual_effect(:effect) as ...) committed by aaronchi   -   add support for page[:element_id].visual_effect(:effect) as well as page.visual_effect(:effect, :element_id)

  add support for page[:element_id].visual_effect(:effect) as well as page.visual_effect(:effect, :element_id)
• Sep 07, 2008

  r79 (add form.reset support to jrails.js) committed by aaronchi   -   add form.reset support to jrails.js

  add form.reset support to jrails.js
• Sep 07, 2008

  r78 (fix for select in JavaScriptElementCollectionProxy) committed by aaronchi   -   fix for select in JavaScriptElementCollectionProxy

  fix for select in JavaScriptElementCollectionProxy
• Aug 01, 2008

  issue 32 ([patch] link_to_remote with 'post' method doesn't send empty...) reported by etoastw   -   Web servers such as Nginx (and versions of Webrick) don't like POSTs to have no Content-Length -- and jQuery doesn't send a Content-Length unless the .ajax call has a data param specified. I put the following line just before the end of the options_for_ajax method: js_options['data'] = "''" if js_options['type'] == "'post'" && js_options['data'].nil? So, basically, if it's a post and no data param has been made for some other reason, then make one that's just an empty string. This means jQuery sends a Content-Length of zero, and people are happy.

  Web servers such as Nginx (and versions of Webrick) don't like POSTs to have no Content-Length -- and jQuery doesn't send a Content-Length unless the .ajax call has a data param specified. I put the following line just before the end of the options_for_ajax method: js_options['data'] = "''" if js_options['type'] == "'post'" && js_options['data'].nil? So, basically, if it's a post and no data param has been made for some other reason, then make one that's just an empty string. This means jQuery sends a Content-Length of zero, and people are happy.
• Jul 24, 2008

  r77 (evil typo) committed by aaronchi   -   evil typo

  evil typo