similar to: [PATCH] prototype rails.js fix for forms with multiple submit buttons

This patch fixes an issue with protected methods becoming public if they are memoized. Looking for +1''s and/or a commit by core... https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5695 Thanks. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to

hi all, I''ve built a simple javascript datepicker for use with Rails. I''m sure others exist, but think this one is quite decent without being overengineered. http://projects.exactlyoneturtle.com/date_picker/ At present there''s no Rails HTML generator method for it; later I will package it in a script/generator, but for now it is quite easy to use with Rails and

Hi all, I wanted to draw some attention to a couple of very small multibyte-related patches I believe should be included before Rails 3.0 RC1: * Use String#bytesize rather than String#length in exception templates: This is a simple case where string length is checked, but bytes is needed, so it breaks with string with multibyte chars.

Hi all Right now i am working on rails 3. Is there any possible way to increase the css and js file loading speed .I tried bundle fu plugin. Please help me Regards Chandrashekar -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Hi, when trying to migrate Signal to Rails 3 I tried to use the shorthand route for: match ''/projects/status(.:format)'' but it thrown an error because the controller was not specified. This happend because actually the shorthand routes only work with routes without optional parameters. The modification to support routes ending with a optional parameters is very simple, as can

We''ve been threatening to open source this for a while, most recently during Alex and Brian''s talk at Railsconf [1]. See the readme [2] for more info, and the source/rdocs for all the gory details. Feedback and contributions are very welcome. Thanks, pt. [1] http://www.slideshare.net/alexchaffee/fullstack-webapp-testing-with-selenium-and-rails [2] == Introduction Welcome to

I''ve submitted a couple of patches in Ligththouse. Provide NoStore implementation of ActiveSupport::Cache::Store This patch provides a NoStore implementation of ActiveSupport::Cache::Store suitable for use in development and test environments where the code need to use the cache interface, but actually caching data is not desired.

The way Rails handles root nodes in JSON and XML serialization is inconsistent. This has been discussed before: https://rails.lighthouseapp.com/projects/8994/tickets/2584-232-activeresource-json-doesnt-send-parameters-with-root-node This seems mostly taken care of with ActiveModel::Base.include_root_in_json, especially if/when it ends up in ActiveResource. However, there is also the issue of how

Hallo -- is there a way anyone know of that I can add a :confirm clause to a form submit? Something like: <%= submit_tag ''commit'', :confirm=>"are you certain?" %> Does anyone know how to achieve this? Cheers, doug. -- Posted via http://www.ruby-forum.com/.

Hello. I have run into a new form that contains multiple submit buttons. Currently my code for working with forms looks just like this example. require ''rubygems'' require ''mechanize'' a = WWW::Mechanize.new { |agent| agent.user_agent_alias = ''Mac Safari'' } a.get(''http://google.com/'') do |page|

Hi, How do i differentiate different submits tags / buttons on one form. Say I want to create an edit form and I want to provide two buttons; one to save and one to cancel. I would have: <%= submit_tag ''Ok'' %> <%= submit_tag ''Cancel'' %> How do I know which button get pressed by the user? One more thing, how to specify the default selection in a

Maybe I''m anal but I like fat-free JS, so I pulled the Proptotype and core Scriptaculous files into one single JS file at 49Kb. It''s "packed" so if you care about that kind of thing, it''s also "obfuscated". Download from my personal site at www.alistercameron.com. - Alister PS. Of course this is the current version as posted on the

I setup a form_remote_tag with several submit buttons, all of them share the same name ( ''do_action'' ) and their values differ. eg. button1 named do_action with value ACTION1 button2 named do_action with value ACTION2, etc No matter which button I press the value passed is always the one defined for the first of these buttons ( the correct value associated with the pressed

Hi, Is it normal that a call to $(''some_form'').submit() doesn''t result in the execution of an onsubmit event handler on ''some_form''? Thanks, - Rowan -- Morality is usually taught by the immoral. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I noticed that 2 days ago that this ticket was marked "stale". https://rails.lighthouseapp.com/projects/8994/tickets/6171 But the issue is still here (I checked just now), and it reminded me I had a patch for it I forgot to submit, so I attached the patch file to the ticket. Since I''m still new on this, can someone please point me the right procedure ? Should I have

Hello! Could someone review the patch attached to [1] and provide feedback? Briefly, it targets rails 3, and fixes "rails g model admin/post". The generated migration creates a "admin_posts" table while the model expects a table simply named "posts". With the patch, the migration creates "posts". Thank you! --phil-- [1]

Can somebody please review my ticket: https://rails.lighthouseapp.com/projects/8994/tickets/4879 It''s a trivial bugfix ("option_groups_from_collection_for_select should produce an HTML-safe string") before RC, I think. Cheers, Wincent -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group,

Hi all, I''ve created and submitted a patch to resolve an issue I had while attempting to meet the OpenSocial API specifications, which dictates that the xml output have tags formatted as lower camelcase (as opposed to upper camelcase, which is currently the only option). With this patch, simply passing :camelize => true still begets the current behavior, but you can now enable lower

Hi I''ve contributed a patch which fixes an incorrect example in the documentation for auto_link in ActionView::Helpers::TextHelper. The example uses truncate in the old style of tuncate(text, length) which no longer works, so I''ve patched it to use the new tuncate(text, :length => n) style.

class Brake scope :good, where(:quality => ''good'') end Brake.all.select &:nil? #=> works fine Brake.good.select &:nil? #=> FAILS Last statement fails because Brake.good.select is returning ActiveRecord::Relation and not an array. I have posted a detailed discussion on ticket #4589 .