Found it - the code was looking in the wrong place to see if forgery protection was enabled. Give this commit a try:
http://github.com/tablatom/hobo/commit/837937111a5e94d15f7184234087dabc8a3a14b8 --Matt On Dec 29, 2008, at 5:51 PM, Tiago Franco wrote: > > Ok, I've made a simple test. > > The following lines were commented in users_controller.rb: > > #hobo_user_controller > #auto_actions :all, :except => [:new, :create ] > > This removes the inheritance from hobo's user controller. The test > doesn't throw the forgery exception. > > I wasn't able to trace the error further. > > TF > > On Dec 29, 1:09 pm, solars <[email protected]> wrote: >> Hi Tom, >> >> No, I don't think it's a hobo problem. I'll do some more controller >> testing this week and report if it is caused by Hobo, but I don't >> think so. >> >> On Mon, Dec 29, 2008 at 12:05:47PM +0000, Tom Locke wrote: >> >>>> @controller.class.protect_from_forgery :secret => "mysecret" >> >>>> to work around this, but this is very quick and dirty, came across >>>> it once when testing controller tests in hobo >> >>> So this is a problem introduced by Hobo? You don't normally need >>> this? >> >>> Tom > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
