search for: marohnić

Hi - quick question: when will "TODO" comment/rake support come out? Tks --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to

A Rails 2.3.9 app with Active Record or Memcache session store will never send the session ID cookie to a client if the client doesn''t send any HTTP cookies in its requests. Rails integration tests didn''t catch this because they always send the HTTP_COOKIE header, even if it''s empty. This is a huge bug, as it can break keeping sessions on sites which don''t set

Just trying to implement a simple helper over the past few days had me really confused. messages = '''' messages << content_tag(:p, ''dave'') #=> &lt;p&gt;dave&lt;\p%;gt; Eventually I realised the original empty string was not html_safe message = ''''.html_safe message << content_tag(:p, ''dave'') #=>

class User end class Agent < User end script/console production User.find_by_name ''john'' SELECT "people".* FROM "people" WHERE ((("people"."type" = ''User'' OR "people"."type" = ''Manager'') OR "people"."type" = ''Agent'')) AND

Yesterday I answered a question regarding polymorphic URL helpers on Core ML and noticed that the module has no documentation. I''ve documented it and rewritten unit tests using Mocha. I also optimized some of the code slightly (nothing major, though). The patch also includes two fixes by Geoff Buesing, who has done awesome work in this area in the past.

Hi, http://dev.rubyonrails.org/ticket/8453 http://dev.rubyonrails.org/ticket/8371 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-3227 I came across the above by accident. While I am subscribed to the so called rails security list where supposed announcement of security issues were to be posted, neither of the above problem made the list. While I use rails a lot and like it, the above

I was just wondering what about a report that I made almost 2 months ago: Active Record observers broken<https://rails.lighthouseapp.com/projects/8994/tickets/4087-activerecord-observers-cant-be-used-for-before-callbacks> I think it''s a pretty big bug. In Rails 3, creating an observer with a "before_save" callback (for instance) will result in all observed models being

Hi, I just put in a patch that allows you to DRY up this: <%= link_to @company.name, @company %> to this: <%= link_to :name, @company %> The symbol indicates the method to be called on the object passed in the link_to options. http://dev.rubyonrails.org/ticket/8789 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the

Hello all, You can easily reproduce with Rails 2.0.2 gems: $ irb >> require ''rubygems'' >> require ''active_support'' >> require ''action_pack'' >> require ''action_view'' *BOOM* You should get an error: MissingSourceFile: no such file to load -- html/document This is because

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

As it currently stands, ActiveRecord has alot of private and protected methods in the Base class. >> ActiveRecord::Base.methods.size => 427 >> ActiveRecord::Base.protected_methods.size => 32 >> ActiveRecord::Base.private_methods.size => 193 I really loved the suggestion by Courtenay in Refactoring AR::Base.find (http://groups.google.com/group/rubyonrails-core/

According to "Ruby On Rails", the layout call is suppose to be inherited: (page 508) "Subclasses of a controller will use the parent''s layout unless they override it using the layout directive" I have a case where this is not working. I have not spent time to concoct a stand alone test. I wanted to verify that David''s book is correct first. Can someone

I haven''t had a chance to work on fixing multiple controller view paths recently. My original patch attempt was: http://dev.rubyonrails.org/ticket/8582 It was rejected due to the fact that it was fixing the symptom more than the problem. However, I think it''s critical that this problem get fixed, otherwise the whole concept of view_paths is severely neutered and

Is there any reason why AR has never supported foreign-key constraints? I can understand the lack of support for triggers and stored procedures since they are highly dependent on the database to create a wrap API around them. But this is not the case for foreign keys. This is specially important for open-source projects like Redmine/Chiliproject and Gitorious where you shouldn''t be

In Rails 3.0 (both RC and edge), any constant that''s defined while loading a file in development mode will get unloaded on each request, regardless of whether it comes from an autoload path in the application or from external code such as a gem. Example file (tested on a fresh edge app): # kittens.rb require ''nibbler/json'' # "nibbler" is a gem specified

Hello, I posted this on the rails talk group but received no response. Perhaps someone on this list could weigh in on whether this is expected/desired behavior or a bug that I should file and develop failing tests for (I doubt I have the active record method_missing fu to actually patch it). Test Scenario: I would like to find or initialize a new user and base the find on the users email

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''

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. > >