summaryrefslogtreecommitdiff
path: root/users/app
AgeCommit message (Collapse)Author
2012-12-11make sure can login twiceAzul
2012-12-10email format validationsAzul
2012-12-10make sure client side validations also run after tabs were switchedAzul
2012-12-10use consistent naming scheme across CA, webapp and couchDB installAzul
2012-12-10created generic Email class and use it with EmailAliasesAzul
2012-12-10actually allow adding email aliasesAzul
2012-12-09basic form added to user settings, simple model createdAzul
2012-12-09first steps towards email aliasesAzul
* unit tests draft * controller draft
2012-12-08serve api version 1 in /1/Azul
Just a very simple start for now. Do we want to use the api for the secure remote password auth from js?
2012-12-07Merge branch 'master' into help_developjessib
Conflicts: app/views/layouts/application.html.haml help/app/controllers/tickets_controller.rb help/test/functional/tickets_controller_test.rb users/test/support/stub_record_helper.rb
2012-12-07fixed signup and removed flash that was not getting displayedAzul
I also tried flash.keep(:notice) but that did not help - not sure how to keep the flash until the root url has rendered.
2012-12-07adding a bunch of translationAzul
2012-12-07first stub at displaying success messagesAzul
2012-12-07refactor: use seperate form for signupAzul
creating and editing users differ so much now it's not worth reusing the complex user_form_with for the signup.
2012-12-07using normal requests for user updates except passwordAzul
password requires ajax for secure remote password to work
2012-12-07refactored views to ease adding of email formAzul
2012-12-06forgot to add new partialAzul
2012-12-06seperated login and password changes in settingsAzul
2012-12-03enable users to cancel their accountAzul
2012-12-03enable admin to edit usersAzul
2012-12-01Merge branch 'develop' into help_developAzul
2012-11-28admins can destroy usersAzul
I changed the permissions a little to be more consistent. Now: * admins can edit users * users can destroy themselves. There's no ui for either of them but theoretically they could. Not sure this is what we want though.
2012-11-26removing merge leftoversAzul
2012-11-26Merge branch 'develop' into help_developAzul
2012-11-26forgot the user partialAzul
2012-11-26Merge branch 'develop' into help_developjessib
2012-11-26Merge branch 'develop' into help_developjessib
Conflicts: users/app/views/sessions/_nav.html.haml
2012-11-26basic typeahead and user querying workingAzul
2012-11-26basic users index with typeahead searchAzul
2012-11-26added admin menu and user index actionAzul
2012-11-26simplified controller and adjusted testsAzul
Also added #assert_json_error to tests.
2012-11-26minor: client side validations fixed + .json requestAzul
2012-11-26basic changing of password and login workingAzul
2012-11-23identify user by id so rerendering the form does not use new invalid loginAzul
2012-11-23test editing user settingsAzul
2012-11-22basic user edit form and actionsAzul
2012-11-22fixed testsAzul
2012-11-22beautify login workflowAzul
* translating error messages * not caching login and password in js anymore * catching non responses
2012-11-22using client side validations for loginAzul
2012-11-22using the new srp.js apiAzul
2012-11-20ui tweaks to the menuAzul
2012-11-20ui tweaks to the menuAzul
2012-11-19Merge branch 'develop' into help_developjessib
Conflicts: app/assets/javascripts/application.js ui_dependencies.rb
2012-11-13using client side validations during signupAzul
2012-11-12Merge branch 'develop' into help_developjessib
Conflicts: help/test/functional/tickets_controller_test.rb users/test/functional/application_controller_test.rb users/test/support/auth_test_helper.rb
2012-11-12Merge branch 'develop' into feature-client-side-validationsAzul
Conflicts: Gemfile.lock
2012-11-12adding client side validations to the mixAzul
2012-11-12fixed signup bug and refactored a bitAzul
2012-11-09Merge branch 'develop' into help_developjessib
2012-11-09got integration test and login flow to workAzul