…s requested, closes #377
…rs as well.
…data issues, closes #356
…scope defined by devise_for. You are now allowed to do: devise_for :users do # Non conventional sign_in route get "/sign_in" => "devise/sessions#new" end And it should work as expected.
…, start to remove usage of assert_template.
…s from Devise and Rails.
…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.