| Age | Commit message (Collapse) | Author |
|---|
|
* reran the simple form initializer.
* wrapped submit buttons are now broken and need a fix.
* disabled confirmation validation in client side validations as the
error message always is attached to the wrong field.
|
|
enable testing error responses on the full rack stack.
|
|
If you inherit respond to and call it again in your controller
it will not overwrite the previous but add to it.
Since we always have some exceptions from the rules it's probably
easiest to be explicit in the controllers that require it themselves.
|
|
with_config is not mean to test the current config. It will
set the config. So instead we need to look into APP_CONFIG.
|
|
There was a lot of special case handling going on in the users_controller
for this. Lot simpler this way.
|
|
This way we do not need to specify it all the times.
In the functional tests defaults do not get added automatically.
Introduced api_{get,put,post,delete} to add format and version default.
One to two functional tests failing, everything else passes.
|
|
|
|
It somehow managed to fail for a certain test order. Seems rather
rare though - have not been able to reproduce it in 5 runs.
Failed with --seed 60219.
|
|
This way the changed flash hash still is recognized.
Also changed the generic 'no_such_thing' i18n key to more specific 'no_such_user'.
The former is very hard to translate as the gender of thing may affect the translation of the 'no such' part.
|
|
|
|
|
|
|
|
we need to require 'capybara/rails' so that Capybara::DSL is available.
ActionController::RecordIdentifier was moved to ActionView
|
|
configured auth token.
|
|
get re-enabled.
|
|
|
|
|
|
Through the config param 'invite_required', providers can decide whether users need to provide an invite code upon signup.
The default setting is false.
|
|
Handing freshly generated invite codes to Factory Girl to make the tests pass
|
|
|
|
|
|
valid user for the tests again
|
|
|
|
|
|
We're not testing the redirects anymore. But the error messages should be pretty clear already. We can start testing redirects again once we redirect to different places for different actions.
|
|
|
|
There's an identities tab now for admins that will allow unblocking blocked handles. It should be easy to expand for aliases and forwards and other types of actions such as editing.
|
|
hash token with sha512 against timing attacs #3398
|
|
|
|
|
|
Only storing the date as that should suffice for normal expiry and is less useful for identifying users by timestamps
|
|
|
|
|
|
|
|
|
|
We should respect the users choice. We can still get their email from the user id if we really need to.
|
|
preparing for #5664 with some test improvements i ran into this issue
This commit includes a fix and the test improvements. In particular it
adds BrowserIntegrationTest#login - so there is no need to go through the signup procedure everytime you want a user to be logged in.
|
|
Hiding them using two mechanisms in case one fails:
.hidden class - bootstrap hides them then
style='display:none' - so they are hidden even if css load fails
|
|
it may not have been required before the RackTest support class.
|
|
|
|
some message tests are failing for me right now.
|
|
|
