…data issues, closes #356
…ange deprecates use_default_scope. If you have non conventional routes and want to specify the scope for a controller, you can do that at the router level: as :user do get "/sign_in", :to => "devise/session#new" end This is saying: when accessing "/sign_in", devise should use the user scope. Meaning that users signed through that form will be signed to the user scope.
…as flag for those using Devise as git with bundler due to the latest changes.
Devise 1.1.0 will be released soon. This new version will support activerecord and mongoid as default ORMs. From now on, Devise will prefer ORM extensions as gems since this is the best way to handle dependencies. For example, to allow Devise to work with Datamapper, it requires at least activemodel, dm-rails and dm-timestamps. If the ORM support comes from Devise gem, we cannot add dm-rails and dm-timestamps as dependencies, relying on the developer and documentation to find these out and install them. Other ORMs may still be added to Devise, as long as they are supported by the community, extend Devise test suite to have all tests passing and they necessarily use ActiveModel::Validations.
…esponse object for non active accounts, closes #341.
…ng a strategy for devise, you now need to call validate(resource), since Devise has now a default API to validate resources before and after signing them in. You can still use other Warden::Strategies with Devise, but they won't work with a few modules like unlockable (they never did, but now we have a single point to make it work).
…as moved to a middleware in Rails 3.
…a look at Highrise API for a good example). This basically allows you to pass the authentication token as HTTP Basic Auth username.