Hi all,
I''m running edge rails, and didn''t update for a day or two.
Then I just
updated today (revision 6088) and now my functional tests are all
breaking. The problem seems to arise anytime I use get with a session
variable, such as
get :login, {}, {:login_id => 1}
The session info does not seem to be used at all. Has the get method
been changed for functional tests? Any help would be greatly
appreciated.
Cheers!
--
Posted via http://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
I had a similar problem yesterday that ended up being [afaik] a stricter version of RESTful routing. I was testing that put :update [with no id] redirected to the index but now it fails. You might want to see if the way you''ve set up routes might be looking for an id that isn''t given. I also had the same problem with :destroy . RSL On 1/29/07, Raymond O''connor <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > > Hi all, > > I''m running edge rails, and didn''t update for a day or two. Then I just > updated today (revision 6088) and now my functional tests are all > breaking. The problem seems to arise anytime I use get with a session > variable, such as > > get :login, {}, {:login_id => 1} > > The session info does not seem to be used at all. Has the get method > been changed for functional tests? Any help would be greatly > appreciated. > > Cheers! > > -- > Posted via http://www.ruby-forum.com/. > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Confirmed that it was a bug introduced by a patch. Here is the ticket: http://dev.rubyonrails.org/ticket/7372 -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Can anyone confirm that this bug was introduced into Rails 1.2.2? I think I''m encountering it with the 1.2.2 Gem, but I want to be certain that I''m not overlooking a different problem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I seem to be having the same problem with 1.2.2 On Feb 7, 12:05 pm, "Jared" <jared.hawo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Can anyone confirm that this bug was introduced into Rails 1.2.2? I > think I''m encountering it with the 1.2.2 Gem, but I want to be certain > that I''mnotoverlooking a different problem.--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---