similar to: Routing error after [6959]

Please check out this ticket (which would explain almost everything): http://dev.rubyonrails.org/ticket/8762 So basically, Rails to_json methods produces invalid JSON out of the box as it doesn''t quote all hash keys. This is valid JSON: { "id": 6589, "code": "SIN", "name": "Singapore" } This is not (Rails'' JSON encoders

The new router in Rails 3 is clean and concise and marks the acceptance of instance_exec as a method for writing a gorgeous DSL. I''m wondering should something similar be applied to the default form helpers? Moving from this: <%= form_for(@post) do |f| %> <%= f.text_field :title %> <% end %> to this: <%= form_for(@post) do %> <%= text_field :title %>

Hi, I recently tried to adopt localized resource names usage, in particular using the http://github.com/kwi/i18n_routing plugin, but faced a problem with HTML escaped non ANSI characters in route names. I''ve created a ticket to track this down: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4896 The problem was introduced with

Just a quick pointer to some ActiveSupport patches hoping for reviews: Puts Array#to_query and Object#to_query in the right places in ActiveSupport - http://dev.rubyonrails.org/ticket/10395 Preserve user-specified content type for XML and JSON rendering (currently it''s overridden and set to Mime::XML/Mimi::JSON - http://dev.rubyonrails.org/ticket/10388 Oh and a tiny patch for

Hi all, I just noticed that in ActiveRecord::ConnectionAdapters::Column.type_cast[1] (and type_cast_code[2]) the type casting for float columns simply does value.to_f, whereas all the others have a rescue or call out to a method, the default implementations of which have rescues or enough logic in that I don''t think they''d fail. Imagine the following: create_table :vehicle do

If you run form_for(@post, :remote => true) {|f| ... } you will get "ActionView::Template::Error (You have a nil object when you didn''t expect it! You might have expected an instance of Array. The error occurred while evaluating nil.[]=)" My patch fixes this error.

Anyone else notice that changeset 5980[1] hosed several of the db adapters? Specifically: activerecord/lib/active_record/connection_adapters/frontbase_adapter.rb activerecord/lib/active_record/connection_adapters/mysql_adapter.rb activerecord/lib/active_record/connection_adapters/openbase_adapter.rb activerecord/lib/active_record/connection_adapters/oracle_adapter.rb Someone has already filed

Looking over the discussions and Trac tickets am I correct in assuming that the simply_helpful''s form_for not respecting the default_url_options (specifically only_path) is a side-effect of some other default behavior choices? Personally, I set only_path to true as my default as I think except were you are dealing with https it makes life much easier (especially in testing) and is just

I do not closely follow the core source commits, but please bare with me. I will keep it short. Recently, changeset#5685 [1] caught my attention as I''ve been waiting for some date_helper love for a VERY long time. What bothered me is that when this changeset was merged into the 1.2- pre-release branch (at changeset#5686 [2]) a change to caching.rb crept in [3], which was not in

Would someone mind taking a look at this verified ticket and give feedback/apply it? Thanks, -- Mark Van Holstyn, Partner / Software Developer mvanholstyn@mutuallyhuman.com, (616) 706-6842 Mutually Human Software, http://mutuallyhuman.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails:

Can someone explain this: http://dev.rubyonrails.org/changeset/7419 there''s no background information linked in via the changeset. As far as I can tell, this change will significantly affect the baseline performance of every existing deployed rails application. Is this a correct assessment? b. --~--~---------~--~----~------------~-------~--~----~ You received this message because you

The revised patch submitted on #4748 broke the build, I''m looking to sort out why. Also note that this auto-test email didn''t make it to rails-core because it was too big (every test failed, so the resulting email was huge). I''ll patch my auto-testing script to truncate the email to no larger than a few kb. Michael Schoen wrote: > "marcel" made

I came across this when switching from rails 1.2.6 to 2.0.2, there is a change in the way routes are generated between these to version due to the routing optimization in rails 2.0.2. In version 1.2.6 it was possible to overwrite the default_url_options method in ActionController::Base to define parameters attached to each generated url. Due to the routing optimization in rails 2.0.2 this is not

On 10/3/07, Glenn Rempe <glenn.rempe@gmail.com> wrote: > > > You may want to also take a look at this bug report that I filed. I > had the same problem and running the ''rake rails:freeze:edge > TAG=rel_2-0-0_PR'' TWO times resolved the issue for me when upgrading a > 1.2.3 app. Explanation in the bug report. > >

In http://dev.rubyonrails.org/changeset/5358 and the new alternative deprecation method, deprecate :link_image_to => :link_to_image should probably use the message version, as both link_image_to and link_to_image should be deprecated (according to the comments at least): deprecate :link_image_to => "Use link_to(image_tag()) instead"

I love form_for, but I really hate <% form_for :person, @person, :url => {...} do |f| %> ... <%= render :partial => ''form'', :locals => {''f'' => f} ... <% end %> I''ve been thinking of instead allowing <% form_for :person, @person, :url => {...} do |f| %> ... <%= f.partial ''form''

After much ado about the naming of model adn controllers... model : Expense controller : Expenses route : map.resources :expenses Here I am using mysql database and created a unique index, since db:migrated created an id object and made it as primary key. Now in the def create @expense = Expense.new(params[:expense]) if @expense.save flash[:viola] = ''New expense saved.. be

I''m stumped on how to get past this. It''s Rails 2.0.2. I have a class, Show. Using STI, I''m using that as a base class, and have DayShow and NightShow that inherit from it. ### class Show < ActiveRecord::Base end class DayShow < Show end ### In my shows/edit.html.erb, I have: <% form_for(@show) do |f| %> However, when I use it with a @show that has

Hello, I wish to route a sinatra application in my Rails 3 app. As said by Yehuda, it should be possible. http://yehudakatz.com/2009/12/26/the-rails-3-router-rack-it-up/ However I see the route isn''t recognized and I get ActionController::RoutingError problems. It works well with simple rack apps however (the test in actionpack with a lambda passes well). I''ve written a test

Can I get some feedback on ticket 5838? I''ve got a patch and testcase that works. Rick seems to be opposed to the patch because I''m not solving all the join issues, but I''d argue that you should at the very least get the sort of object your asked for back. Account.find_by_sql() should -never- return something other than Account objects. -- Kevin Clark