Ralph Shnelvar wrote: > Sharagoz -- wrote: >> You are using warden. Does the issue occur without warden? >> If not, the first thing you can do is to update to the latest version of >> warden (0.9.0). If that doesnt solve the problem, maybe post an issue at >> github if you feel it is warden related. >> http://github.com/hassox/warden/issues > > Well ... I upgraded. Jeez, that was hard. Devise changed several of > its interfaces and it was a joy and a half tracking all(?) of them down.
If you have comprehensive tests, then the tests tell you where things changed. If you don't have comprehensive tests, write some *now*, before you write any more application code. Then get in the habit of doing all new development test-first. > > Anyway ... same problem. > > I have no idea how I would pull out warden and still have anything left > working. > Stub the methods you need? > So ... I'm gonna go heads down and learn FireBug and see what the hell > is going on. Firebug won't help unless this is a JavaScript issue, which it almost certainly is not. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- 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-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
