Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Does not work properly with STI (single table inheritance) #195
I'm using rails 3 beta2, and I've tried both the master branch, and 1.1.rc0. When I use devise_for in my routes, the routes are never created. 'rake routes' never shows any session/devise related routes, just those that I've created.
It doesn't throw any errors or break anything, the routes just don't come through. I have to manually set them for them to work.
Thanks for looking at it.
A couple notes. I'm doing some craziness with the routes, mapping anything missing to pages#show (its a pretty dynamic cms). I thought maybe my namespace or routes were messing with it, so I tried removing everything but root :to and the devise_for line but still had no success.
I also know that you guys dropped support for mongo_mapper, so I just used the devise/orm/mongo_mapper from the version prior to master. It is actually working fine (creating passwords correctly etc).
Here are my routes and Gemfile
Here is the output from 'rake routes'
Mongomapper is not supposed to modify the routing part, so this is not the cause.
Actually, I cannot see anything in both Gemfile and config/routes.rb that could be causing the issue. Thus I need to ask you to try to isolate this issue in a smaller application that you can publish in Github.
Yeah thats what I was thinking as well.
After creating a fresh project, I think I've narrowed it down. My admin model was extending user (sti). Using devise_for :users works as expected. I went back and added the devise (w/options) method to my admin model as well and that cleared it up.
Seems it wasn't inheriting from the User model. Wouldn't consider that a problem really, but it would be useful if it did :)