summaryrefslogtreecommitdiff
path: root/users/app
AgeCommit message (Collapse)Author
2014-01-13Comment for how to call view that we aren't now using.jessib
2014-01-09Some more cleanup, but still want to make sure ↵jessib
by_user_ids_to_show_and_created_at view is right before issuing pull request.
2014-01-07Some refactoring, to simplify user model, optimize, and allow messages to be ↵jessib
sorted by date (although are not now.) Also, rather than use whenever gem, will have cron job created to call task.
2014-01-07Merge branch 'develop' into feature/messages_apijessib
2014-01-07only emit pgp keys if they are actually setAzul
if doc.keys has not been set doc.keys[pgp] will raise an error. We always upload the key after signup - but this might fail and there is some time in between. Not checking for this condition lead to errors in the couch logs.
2014-01-07remove outdated views that cause errorsAzul
The datastructure changes to that email_aliases is not available on the user record anymore. Keeping these views leads to errors on couch servers.
2013-12-31Add authentication to API, but not sure it is best way.jessib
2013-12-31Removing join-model we are no longer using.jessib
2013-12-31Cleanup of code for messages API and cron job for 1 month payment warning. ↵jessib
Authentication still remaining piece.
2013-12-30Fixes to initial go at job to send one month warnings.jessib
2013-12-30Merge branch 'feature/messages_api' into feature/messages_cronjessib
2013-12-30Change structure to be more no-sql-y, rather than relational.jessib
2013-12-30Not actually how we want to do this, but at least finish outlined part, that ↵jessib
will later be replaced.
2013-12-26Very very rough start to having messages for payment automatically created.jessib
2013-12-24Catching some corner cases & new tests.jessib
2013-12-24Add API tests and some refactoring of messages so we can get a user's ↵jessib
messages within the webapp.
2013-12-24API method to mark a user's message as read (will refactor)jessib
2013-12-24Initial start to messages API.jessib
2013-12-23Merge remote-tracking branch 'jessib/feature/3389_download_links' into developAzul
Conflicts: core/app/views/common/_home_page_buttons.html.haml users/app/views/users/show.html.haml
2013-12-22locale prefix support:elijah
* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path
2013-12-20enable billing engine by default, consolidate APP_CONFIG[:payments] and ↵elijah
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree]
2013-12-19Put download link on user page.jessib
2013-12-16Fix issue 4756: /login should not crash if one goes there when logged in.jessib
2013-12-16Merge pull request #123 from azul/refactor/standartize-user-routesjessib
refactor: remove Overview controller - we can use Users#show
2013-12-13refactor: remove Overview controller - we can use Users#showAzul
we were only using Users#show to redirect to the edit action. So I replaced that with the overview and we have no more use for the extra controller. This also simplifies linking to the users in question a lot.
2013-12-13make the possible actions for users and admins configurableAzul
with tests
2013-12-13refactor: move edit sections into partialsAzul
2013-12-09Merge pull request #119 from jessib/feature/service_levelazul
Feature/service level
2013-12-06make sure key responses are plain textelijah
2013-12-06simple validation for pgp key formatAzul
2013-12-06ignore attempts to empty public_key, refactorAzul
refactor: prepare validations of the uploaded pgp keys
2013-12-05We won't want service levels in production mode, and have it so this initial ↵jessib
service level code won't break anything if it isn't set in the config.
2013-12-03Some simplification of code.jessib
2013-12-03Add ServiceLevel class to wrap config and give accessors. Has some hacky ↵jessib
parts, but seems like okay generic start for now.
2013-12-02Merge branch 'develop' into feature/service_leveljessib
2013-11-26simple validation for pgp key formatAzul
2013-11-26ignore attempts to empty public_key, refactorAzul
refactor: prepare validations of the uploaded pgp keys
2013-11-25Give 404 error if one goes to /key/user for non-existing user.jessib
2013-11-21Refactoring of code, and tests.jessib
2013-11-18Need to cleanup some, but start to show public key for /key/usernamejessib
2013-11-18Start of service level code, which will be tweakedjessib
* stores desired & effective service level * whenever desired level is changed, effective level will be updated * allows user to set their desired service level * allow admin to update desired & effective service level
2013-11-12Merge pull request #110 from azul/feature/cleanup-expired-tokensjessib
Feature/cleanup expired tokens
2013-11-08fix cornercase of non expiring tokensAzul
2013-11-08Token.destroy_all_expired to cleanup expired tokens (#4411)Azul
2013-11-06use the account lifecycle from UsersController#destroyAzul
2013-11-06destroy all tickets created by a user when account is destroyedAzul
In order to keep the users engine independent of the tickets engine i added a generic load hook to the account model. The tickets engine then monkeypatches the account destruction and destroys all tickets before the user is destroyed. The tickets are destroyed first so that even if things break there should never be tickets with an outdated user id. I would have prefered to use super over using an alias_method_chain but I have not been able to figure out a way to make account a superclass of the account extension and still refer to Account from the users engine.
2013-11-05Identity.destroy_all_disabled will clean up disabled identitiesAzul
This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date.
2013-11-05disabled identities to block handles after a user was deletedAzul
2013-11-05refactor: Identity.disable_all_for(user) on user destructionAzul
This way the identity model defines how identities should be disabled. We currently still destroy them. But it will be easy and nicely isolated to change this next.
2013-10-30notify user their account was successfully deleted (refs #4216)Azul
Also fixes a cornercase when admins deleted their own account. So far they would be redirected to the users list - which then refused access. Now they'll be redirected to the home landing page as well.