We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
move versions sections to latest first
Add reference to the simpler approach
confirm! deprecated in devise 4.2.0, use confirm instead
make errors i18n compatible
In rails 5.1 skip_before_filter is deprecated
intializers -> initializers
Add note for specifying override of password_required? in Devise 3.5.2+. Otherwise it seems as if it is not necessary.
Added missing password_match function for User model. Clarified instructions.
Updating activation template - Throws an error when there is no user_name field present on User model.
Devise 3.5.2+ should use same code as Devise 2.x-3.0
Add note about devise 3.5.2 that removed encrypted confirmation_tokens
Added reminder to update confirmations view and `User#password_required?`
the method #with_unconfirmed_confirmable and #do_show always returns a new user with errors as the digest is stored in the record, whereas comparison was done using the non-digest version of the token
Updated How To: Override confirmations so users can pick their own passwords as part of confirmation activation (markdown)
Updated confirmations_controller for Devise 3.1 and above (with encrypted confirmation_token)
grammar: changed indicative to imperative
Better English grammar
see my previous edit message (same issue) ...
Previous was confusing. Omitting has_no_password? (which is specified for rails3/devise1.2 only)
set the `resource` correctly when re-rendering `new` action during update error-case.
According with commit https://github.com/plataformatec/devise/commit/eb640ed344fb5e227e82b1f3a914ca9fabb938e0, confirmation tokens no longer digests
Treat @confirmable as the model it is. See http://stackoverflow.com/questions/25176010/error-undefined-method-add-error-on-for-confirmationscontrollerclass-rails4-d for the confusion the previous version caused.
Revert 8ce08ba96f2367c64286a1065b6334ab1566e120 ... 0b7da1683d8b30e175a1b41f47afaf92bb35989f on How To: Override confirmations so users can pick their own passwords as part of confirmation activation
There is no need to define a proxy method. Just call the new method name!
Revert faa4a4571d0bf654f2699ecc6f43d837b3054c8a ... 5b86103af6f9aa323207f4fae0cf34d30d8380f2 on How To: Override confirmations so users can pick their own passwords as part of confirmation activation