summaryrefslogtreecommitdiffstats
path: root/models/users.js
Commit message (Collapse)AuthorAgeFilesLines
* Fix merge conflict.Lauri Ojansivu2017-03-051-1/+44
|\
| * wording change, email sending optimization, add texts to i18nlkisme2017-02-261-5/+5
| |
| * Admin panel:lkisme2017-02-241-1/+44
| | | | | | | | | | | | | | Only invited user can register in strict mode, Set mail server in admin panel, Switch strict mode in admin panel, Invite people to system in admin panel
* | [ENH] Invite user with lower case emailFlorent MONTHEL2017-03-041-2/+3
|/
* fixed few overseightsMario Orlicky2016-11-251-1/+1
|
* New option to set up minimum limit to show cards count for each list in boardMario Orlicky2016-11-251-0/+17
|
* Fixed buildMario Orlicky2016-11-191-2/+2
|
* New change settings option and possibility to hide system messagaesMario Orlicky2016-11-191-0/+21
|
* Fix login on Sandstorm by not creating welcome boardsDrew Fisher2016-11-031-17/+23
| | | | | | | | | | | | | | | | | This one is a pretty strange chain of events: * fetching /.sandstorm-login via accounts-sandstorm's rendezvous protocol causes a user to be created in the users collection * models/users.js has hooks to create a board and lists when a user is created * models/activities.js has a hook to create activity entries when a list is created * this hook does not handle not having no boardId, which results in attempting to run the hook with boardId: 'false'. 'false' does not have a title attribute, which causes the whole method call to throw an exception. * This makes the initial login fail. While there may be other bugs, the simple fix is to not create the board and lists when running under Sandstorm, where you only have one board anyway.
* Merge #616 into develMaxime Quandalle2016-07-181-30/+109
|\
| * Welcome board: Allow localizationAlexander Sulfrian2016-06-031-4/+3
| |
| * Fix initial board creationAlexander Sulfrian2016-06-031-13/+19
| | | | | | | | | | | | | | | | | | | | We cannot rely on the automatic userId setting of the collection hooks. If a user is created during invitation, the userId field will contain the id of the inviting user. This fix this, by mocking the CollectionHooks.getUserId function and returning the userId of the new user for all new documents after creating the user.
| * Remove duplicated logicAlexander Sulfrian2016-06-031-7/+0
| | | | | | | | | | | | The duplicated logic was nessessary because the before.insert hook was not called before validation, when inserting was initiated on the server. Using autoValues fixed this problem.
| * Meteor.users: Add SimpleSchemaAlexander Sulfrian2016-06-031-8/+90
| | | | | | | | Replace before.insert hook with SimpleSchema and autoValue.
* | profile.name is called profile.fullname (#615)Alexander Sulfrian2016-07-111-2/+2
|/ | | | The name of the profile field was changed log ago. This fixes the remaining wrong references.
* Fix initials avatar generation (#577)Alexander Sulfrian2016-04-211-2/+2
| | | | The ES5 reduce method also needs a initial value. This bug was introduced in aa974aa54ab6e5b7db7450206d12b44ffb3a0306.
* Improve PR, adding more commentsfloatinghotpot2016-01-061-7/+7
|
* Add notification, allow watch boards / lists / cardsLiming Xie2016-01-051-7/+74
|
* Send invite email in the server console in development modeMaxime Quandalle2016-01-011-5/+2
| | | | | | Meteor support that use case for us, we don't need to implement our own validate strategy on top of that. This was also discussed as part of the #454 review.
* Fix avatar support on SanstormMaxime Quandalle2015-12-301-13/+0
| | | | | | | | | | The bug comes for 9154b06 which this commit partially reverts. The synchronization between the user document profile and the Sandstorm HTTP headers is still not perfect. Having a clean model may requires the `accounts-sandstorm` to expose a hook to modify the user document just after the `services.sandstorm` credentials are updated. Fixes #460
* Partially revert aae5030Maxime Quandalle2015-12-241-1/+1
| | | | | | | As discussed in #370 and announced in the official Eslint-meteor plugin repository (https://github.com/dferber90/eslint-plugin-meteor), it is recommended to not use this plugin anymore has the author has it is currently broken and the author has abandoned it.
* bugfix: only care active members, also optimize some codefloatinghotpot2015-12-081-6/+2
|
* add: invite user via email, invited user can accept or decline, allow member ↵floatinghotpot2015-12-071-0/+105
| | | | to quit
* i18n-ize meteor email templatesfloatinghotpot2015-12-041-0/+10
|
* merge with /develXavier Priour2015-11-131-14/+18
|\
| * Add eslint-plugin-meteorDominik Ferber2015-10-271-13/+19
| | | | | | | | | | | | | | | | Add rules for eslint-plugin-meteor. Use local version of eslint and eslint-plugin-meteor, instead of relying on global versions. Ensures consistent versions of eslint and eslint-plugin-meteor for all developers.
* | Import members: UI flow okXavier Priour2015-11-131-1/+3
|/
* Prefer ES5 methods over underscore utilitiesMaxime Quandalle2015-10-221-8/+8
| | | | | | | | | | | | | | Since 07cc454 (ie the switch to Meteor 1.2) we includes the `es5-shim` polyfill to support methods like `Array.prototype.forEach` in a consistent way across all supported browsers (IE8+). MDG recently released a blog post recommending the use of these native methods instead of underscore [0]. We know follow this recommendation. This commit also favor some ES6 features (argument defaults, destructing assignment) in places where we didn’t use them. [0]: http://info.meteor.com/blog/es2015-get-started
* Upgrade kenton:accounts-sandstorm package to 0.1.6Maxime Quandalle2015-10-211-0/+13
| | | | | We now delegates more user attributes sync (avatar and permissions) to this package instead of doing it ourselves.
* Centralize all mutations at the model levelMaxime Quandalle2015-09-081-0/+157
This commit uses a new package that I need to document. It tries to solve the long-standing debate in the Meteor community about allow/deny rules versus methods (RPC). This approach gives us both the centralized security rules of allow/deny and the white-list of allowed mutations similarly to Meteor methods. The idea to have static mutation descriptions is also inspired by Facebook's Relay/GraphQL. This will allow the development of a REST API using the high-level methods instead of the MongoDB queries to do the mapping between the HTTP requests and our collections.
generated by cgit v1.2.3-1-g7c22 (git 2.25.1) at 2024-10-31 11:16:24 +0000