* remove unnecessary quoting * apply consistent sorting of keys
There is a configuration option that allows for sign up to easily be disabled. With this enabled, the `sign_up_path` route helper is not defined. This causes a 500 when a user login fails because the default I18n message uses `sign_up_path` for interpolation. I opted to remove the interpolation, and thus the sign up link, from the default sign in failure message. This is perhaps somewhat less helpful, but it makes for a working out of the box experience for people who disable sign up. An alternative would be to add another flash message specifically for this case and add conditionals to `DefaultSignInGuard` (or a helper object) to handle it. I felt that the increased complexity of that solution wasn't worth it.
There are many instances where you don't want users to be able to sign up (e.g. admin-only system). Clearance can now disable sign up by setting: Clearance.configure do |config| # other configuration options config.allow_sign_up = false end in `config/initializers/clearance.rb`.
* remove `new_user`, `new_session` and :delete to `new_sessions` * these are superceded by `sign_in`, `sign_out` and * `sign_up` * these helpers were not documented
* Take off _paragraph prefix because text does not contian <p> tags * Change password text copy to be more clear. * Sort i18n keys alphabetically. * Resolves #248
As reported on: #250 By default, the text on the password reset page read: > We will email you a link to reset your password. This implies that the system is already in the process of sending an email, and that no further action is required by the user. We have had multiple users of our application fail to complete the password reset flow because of this confusion. Here's how these users got stuck: * Visit the login page. * Enter their email address and an incorrect password. * The application denies login with "Bad email or password" error. * User gives up and clicks "Forgot password?" link. * Reset password page loads with the text "We will email you a link to reset your password.". User thinks they are done. (After all, they already provided their email address on the login page.) * User never completes the reset password form. Telephones support complaining their password is not being reset. Our fix was to change the password reset text to: > To be emailed a link to reset your password, please enter your email > address.
* Change routes to use `get` instead of `match`. * Don't allow multiline strings for email format. * Rails 4 issues an exception when validates_format_of encounters regex that uses ^ and $ rather than /A and /Z. See this pull request: rails/rails#6569 * `sign_out` should use DELETE, not GET. * Remove irrelevant spec for testing regex. * Test against latest security-patched Rails versions.
* Fixes inconsistency with input wrapper classes. * Improves markup for secondary links. Adds sign in link to sign up form for better navigation. #252
+ Updated views, and flashes to use I18n + Updated News file + Updated specs to use I18n
* Use single quotes unless interpolating. * Do not align tokens. * Add a newline between lines of code and blocks. * Alphabetize methods and lists of attributes. Additional refactoring: * Refactor new_indexes to more appropriately use a Hash. * Refactor collections to use Symbol#to_proc to shorten lines. * Use consistent naming patterns (existing_*, new_*). * Remove `each` naming convention on enumerators. * Remove now unnecessary GOALS file.
… triggered by the block parameter.
…give more control to the application developer.
This reverts commit e2601db.
…erface, changing routes to meet groupies experience.