Age | Commit message (Collapse) | Author |
|
|
|
password (they can leave either the same if they just want to change one, but we should make this clearer.)
|
|
|
|
warden srp strategy in lib has it all.
|
|
|
|
There was a weird case with reloading the user in the test if the public key had been unset.
|
|
|
|
|
|
Conflicts:
users/app/views/users/edit.html.haml
|
|
want to leak ID information.
|
|
|
|
|
|
changed the way the presenter works. Will need functional testing
|
|
|
|
|
|
different display.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
users/app/views/emails/_email.html.haml
|
|
Refactoring of tickets controller to fetch the ticket in a before filter...
|
|
Fixing routes with api
|
|
|
|
This isn't ready to merge, as there is an issue with logging in as an admin in the test.
|
|
Conflicts:
users/app/controllers/users_controller.rb
|
|
test after merging in show view for users.
|
|
|
|
|
|
This involves a number of other changes like making sure the comparison between aliases and emails still works.
Will do that by removing the @domain.tld from aliases as well.
|
|
|
|
is an admin, they should see an alert that the object wasn't found, and be redirected to the current controller.
If the object isn't found and the current user is not an admin, then we will continue to give an error about no access, so as not to leak information about what IDs do and don't exist.
|
|
listing the tickets. Give a message if a user has no tickets.
|
|
|
|
Just found out that render(@collection) returns nil for emtpy collections. So that is usefull for putting messages about the emtpy collection in an or clause.
|
|
partials have specific CSS for another use, so we will likely want to tweak this.
|
|
Conflicts:
users/test/functional/users_controller_test.rb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In case we need them at some point - now it's
new_api_user_path instead of new_user_path for example.
This way they should not conflict with the normal route generation
|
|
|
|
|