summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
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-08moved cert into the api pathAzul
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 'feature/email-forwards-for-users'Azul
2012-12-07fixed test to work with edit view that includes email and email forward.Azul
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-07bumping version to 0.1.10.1.1Azul
This version has basic user and help tickets management
2012-12-07Merge branch 'develop'Azul
2012-12-07Merge branch 'feature/improve-editing-user-settings' into developAzul
2012-12-06forgot to add new partialAzul
2012-12-06seperated login and password changes in settingsAzul
2012-12-06Merge branch 'feature/user-cancel-account' into developAzul
2012-12-05trying to work around a gem issue with the ruby racer 0.11.nAzul
2012-12-04Requiring libv8 gem so therubyracer gem will work.jessib
2012-12-03refactored tests with new find_record helperAzul
find_record User will return a stubbed user record and make sure User.find_by_id(user.id) returns the same so it can be used in controllers.
2012-12-03enable users to cancel their accountAzul
2012-12-03enable admin to edit usersAzul
2012-12-03make tests pass on an empty dbAzul
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-26forgot the user partialAzul
2012-11-26Merge branch 'feature/admin-users-list' into developAzul
2012-11-26basic typeahead and user querying workingAzul
2012-11-26hide buttons in table-hover unless hovered over trAzul
2012-11-26basic users index with typeahead searchAzul
2012-11-26added admin menu and user index actionAzul
2012-11-26Merge branch 'feature/users-change-passwords' into developAzul
2012-11-26fixed login error message on wrong usernameAzul
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-23Merge branch 'feature/users-change-passwords' into developAzul
2012-11-23refactored creation of record stubsAzul
2012-11-23test editing user settingsAzul
2012-11-22basic user edit form and actionsAzul
2012-11-22ship config file so CI can testAzul
2012-11-22Merge branch 'feature/error-messages-on-login' into developAzul
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-22don't collabse the navAzul
2012-11-20ui tweaks to the menuAzul
2012-11-20fixed mocha version stringAzul