meteor-useraccounts / core Goto Github PK

View Code? Open in Web Editor NEW

529.0 529.0 282.0 1.19 MB

Meteor sign up and sign in templates' core functionalities

Home Page: http://useraccounts.meteor.com/

License: MIT License

JavaScript 99.71% HTML 0.29%

core's People

Contributors

Stargazers

Watchers

Forkers

xiaolinlu djhi tmnsun pranayshah cutemachine rgoomar wzalazar nate-strauser radiegtya sivli-embir praneybehl aselbie dcsan rootedsoftware html5cat lumatijev shelkie yanivnizry ixdi alethes fpoirier1 danieldent pfafman solox312 bumbleblym strikeout serkandurusoy timothyarmes dalgard adrianmcli mivida2023 kevohagan rdrey bryansd dcworldwide petr24 ravic1995 pbrekelmans philippspo futurama56 rclai manuelmateus16 afuggini aladine steveodom bodhihu davecromberge mcoenca rawgem adamdawkins ysyhy5100 sumitk maxhodges redwraith2 midtownninja sawima lemmih pcorey sd031 elgusto cooloney sharpenedspoon artem-russkikh heyiam batmunkh sbrichardson pierre-ferreira shekharrajak gaelan chiester setohe0909 challett aserranom 7being parktastic gwendall jonxduo cyclops24 zeroasterisk chongyunpeng abernix jxm262 evgentraytyak dovrosenberg carrot93 katel phocks dineshsdm devwaker fesp21 rainice jjeffwarner logankoester flyeven gevou came niole afric84 styel07 d-a-g-e

core's Issues

throw an error in case no account service is present

in case no social oauth packages nor accounts-password package are installed, an error should be thrown.

This is to prevent the form to be rendered almost empty. See #21

New release

Hi There,

Is it possible to create a new release together with the bootstrap package? Im still running on the trunk to include the forbid account creation from client side.

Thanks :)

Regards,
Riaan

Any way to have different placeholder text for password in signIn and signUp fields?

I would like to use "at least 6 characters" as the placeholder text in the signUp form. But when I display the signIn form, I'd like to have "enter password" or just "password."

Is there any way to have the password placeholder be different for these two situations?

Thanks.

Log user out when accessing enroll-account

Because of the auto-login, wouldn't be better to log the user out when accessing the enroll path and ask to create password OR to login with another account ? Security wise, I think it would be best since a user receiving an enroll invite isn't suppose to have an account.

better server validation

add use of Accounts.validateNewUser to have more robust signUp validation

see https://github.com/meteor/meteor/blob/devel/packages/accounts-base/accounts_server.js#L1039

{{> loginForm}} Doesn't exist

From the README.md file, routing section:

This custom template should include, anywhere convenient, {{> loginForm}} in order to get the provided sign-up form.

The problem is that {{> loginForm}} doesn't exist and if I use {{> signinForm}} (which is the one that works) it renders the signin form instead of the signup form.
I'm doing this because I want to have different pages for signin and signup.

MinLength validation on password not working

The minLength validation of the password is not working. The signUp form routes to the home page with no error and no user is created. I have it set to 6 and tried entering just 3 characters. Here are my Account.Templates.configure settings.

AccountsTemplates.configure({
// Behaviour
confirmPassword: false,
enablePasswordChange: true,
forbidClientAccountCreation: false,
overrideLoginErrors: false,
sendVerificationEmail: false,

// Appearance
showAddRemoveServices: false,
showForgotPasswordLink: true,
showLabels: true,
showPlaceholders: true,

// Client-side Validation
continuousValidation: false,
negativeFeedback: true,
negativeValidation: true,
positiveValidation: true,
positiveFeedback: true,

// Privacy Policy and Terms of Use
// privacyUrl: 'privacy',
// termsUrl: 'terms-of-use',

// Redirects
homeRoutePath: '/'

});

So far, aside from this, the customizations of the string items is fabulous!

Forgot password form no return link to SignIn form

see meteor-useraccounts/bootstrap#5

ReferenceError: postSignInRedirect is not defined

Exception in delivering result of invoking 'login': ReferenceError: postSignInRedirect is not defined
    at http://localhost:3000/packages/accounts-templates-core.js?2481bb7e7c4035b25669bdb0ef70955a167fa843:1364:25
    at Meteor.loginWithPassword.Accounts.callLoginMethod.userCallback (http://localhost:3000/packages/accounts-password.js?ce021e15955713b9b2558024f0cda32e3b328ef9:81:21)
    at _.once (http://localhost:3000/packages/underscore.js?0a80a8623e1b40b5df5a05582f288ddd586eaa18:801:19)
    at Accounts.callLoginMethod.loggedInAndDataReadyCallback (http://localhost:3000/packages/accounts-base.js?7b90b1939a52b5c6ad91265df4dd167bd5f4ebdb:467:5)
    at Meteor.bindEnvironment [as _callback] (http://localhost:3000/packages/meteor.js?7a66be7a03504cd2c18dd47b699e6233b60675ed:821:22)
    at _.extend._maybeInvokeCallback (http://localhost:3000/packages/livedata.js?edca5d3826d0b2bd3507cac956e98d83559da4d8:3782:12)
    at _.extend.receiveResult (http://localhost:3000/packages/livedata.js?edca5d3826d0b2bd3507cac956e98d83559da4d8:3802:10)
    at _.extend._livedata_result (http://localhost:3000/packages/livedata.js?edca5d3826d0b2bd3507cac956e98d83559da4d8:4817:9)
    at onMessage (http://localhost:3000/packages/livedata.js?edca5d3826d0b2bd3507cac956e98d83559da4d8:3647:12)
    at http://localhost:3000/packages/livedata.js?edca5d3826d0b2bd3507cac956e98d83559da4d8:2709:11

Support for verify-email route

...to be used after Accounts.sendVerificationEmail.
Accounts.verifyEmail should be called with provided token.

Change meteor-accounts-t9n dependency

As soon as all new keys are merged to the master branch and @softwarerero releases a new version, the smart.json should be changed to point to the original repo.

Asinc check what 'func' function returns after event fired (eg. keydown, blur, submit)

This would make easier implementing custom validation.

postSignInRoutePath

Should there maybe be a postSignInRoutePath ? how is this implemented at the moment? :)
Awesome work again luca!

Change server-side validation not to use Accounts.onCreateUser

Despite I had in mind to use Accounts.validateNewUser, I ended up using Accounts.onCreateUser by mistake. Actually it is working great but can be called only once, and hence, at the moment, I'm preventing anyone else to use it to set an initial user object :-(

A solution to be able to check fields content beforehand could be to implement something similar to https://github.com/meteor/meteor/blob/devel/packages/accounts-password/password_server.js#L637 and https://github.com/meteor/meteor/blob/devel/packages/accounts-password/password_server.js#L666 inside a custom server-side method.
The only thing is the password should be sent to the server already hashed!

How does the forbidClientAccountCreation work in latest release [Question]

Hi,

I used to define the forbidClientAccountCreation on the normal accounts package and it worked 100%.

I upgraded to the latest accounts-templates-core release and now im getting the following error:

20140702-19:55:43.804(2)? (STDERR) /home/riaan/.meteor/tools/858c88b520/lib/node_modules/fibers/future.js:173
W20140702-19:55:43.804(2)? (STDERR)                         throw(ex);
W20140702-19:55:43.805(2)? (STDERR)                               ^
W20140702-19:55:43.823(2)? (STDERR) Error: Can't set `forbidClientAccountCreation` more than once
W20140702-19:55:43.823(2)? (STDERR)     at packages/accounts-base/accounts_common.js:81
W20140702-19:55:43.825(2)? (STDERR)     at Array.forEach (native)
W20140702-19:55:43.825(2)? (STDERR)     at Function._.each._.forEach (packages/underscore/underscore.js:105)
W20140702-19:55:43.826(2)? (STDERR)     at Object.Accounts.config (packages/accounts-base/accounts_common.js:78)
W20140702-19:55:43.826(2)? (STDERR)     at app/shared/ATConfig.js:1:45
W20140702-19:55:43.828(2)? (STDERR)     at app/shared/ATConfig.js:11:3
W20140702-19:55:43.829(2)? (STDERR)     at /home/riaan/Projects/prostock/.meteor/local/build/programs/server/boot.js:155:10
W20140702-19:55:43.829(2)? (STDERR)     at Array.forEach (native)
W20140702-19:55:43.830(2)? (STDERR)     at Function._.each._.forEach (/home/riaan/.meteor/tools/858c88b520/lib/node_modules/underscore/underscore.js:79:11)
W20140702-19:55:43.830(2)? (STDERR)     at /home/riaan/Projects/prostock/.meteor/local/build/programs/server/boot.js:82:5

Any ideas?

Thanks.

Regards,
Riaan

AccountsTemplates.ensureSignedIn not working if defined in a Controller

so i have a basiccontroller defined

@BasicController = RouteController.extend(
  layoutTemplate: "layout"
  onBeforeAction: [
    BeforeHooks.animateContentOut
    BeforeHooks.startNProgress
    AccountsTemplates.ensureSignedIn
  ]

it doesn't seem to pick up the ensureSignedIn.

Defining it outside of the controller works

errStr localization problem

Hi again @splendido 😊,
I'm having problems trying to localize the 'errStr' parameter: when using for example 'T9n.get('error.invalidEmail')' even if the active language is 'it', it still returns the english one.

I also tried writing T9n.get('error.invalidEmail') into the browser javascript console and it returns the italian string as it should be, but errStr stil uses the english one.

Is there a way to disable account creation

How can I restrict account creation?

To disable account creation from the client-side I can use:

Accounts.config({
  forbidClientAccountCreation : true
});

But this does not work in this situation because it only restricts the createUser call from the client. Must I just remove the sign-up link with a helper function?

Thanks,
Riaan

meteor-accounts-t9n broken after latest update

@splendido I am sorry I couldn't create the issue on the package repo as its a fork of the original package.
I am getting this error when trying to install the package:

accounts-t9n
branch: https://github.com/splendido/meteor-accounts-t9n.git#master
ERROR: 1 Command failed: error: you need to resolve your current index first

STDOUT: t9n/de.coffee: needs merge
t9n/en.coffee: needs merge
t9n/es.coffee: needs merge
t9n/it.coffee: needs merge
t9n/pl.coffee: needs merge

STDERR: error: you need to resolve your current index first

/usr/local/lib/node_modules/meteorite/lib/sources/git.js:181
self.checkoutType + ": " + (self.commit || self.head);
^
There was a problem checking out branch: master

Any help will be appreciated.

Change erro thrown if not logged in

Now it throws this:

>error.accounts.Must be logged in!<

Doesn't come back to previous route after social login

Add support for server only validation (signup with a code)

Usecase: beta access program where only users with a correct invitation code can sign up. You obviously don't want the regex to be on client code :)

This may be a duplicate of #4.

Create account with username and e-mail and login with username

Would it be possible to add the option to register a new user with username, e-mail adres and password and then let a user log-in with username.

Currently in Meteor's Accounts.createUser it's already possible to send an username variable. Hopefully this makes it easier to incorporate :)

signin route should redirect in case the user is already logged in

INCOMPATIBLE WITH METEOR 0.9.0 OR LATER

The auto-migration to the new package system seems to have failed with this package (and all the upstream ones).

I love the path you are taking with this package. I would love to use this but I, foolishly, locked my project to the new package system. I see there is a lot of work being done on this package and was wondering if you had plans to push to the new package server any time soon?

can't get this working

got this:

Pass arguments to redirect path

Are there plans for passing arguments to the redirect path? I think it might be useful to redirect to something like /:username.

Enrollment page

Were you planning creating a view for when a user is invited via the Accounts.sendEnrollmentEmail and click the url with the reset token ?

Would be great to update history

Can i help with this?

Accounts-meld, accounts-merge usability

Hey, I am working on a project and am using Facebook, Google as well as Twitter for logins. I would like to know what are the issues still with using the accounts-merge option? Also I see there is a different branch for that in your tree altogether. With mrt add, I assume I have the master tree. What difference does this make? Would you stay this has reached a point where it is possible to start using the accountsMerge option, because the readme file has not been changed since the very early days of this package. Also how much of accounts-meld has already been integrated?

Cannot change between signIn and signUp pages since update to 0.0.18

Since updating to v0.0.18 I cannot use the links to change between the signIn and signUp pages (using accounts-templates-foundation). The URL fragment updates correctly, but the router does not trigger a page change.

However if I refresh the page after the URL is changed, the correct page is displayed.

Unable to require username AND email for new accounts

I have created a bare bones app to play around with accounts-template-bootstrap. I have a basic flow working, but I have been unable to determine the correct configuration to require both username and email address when creating a new account. I've tried the following in my at_config.js.

AccountsTemplates.addField({
_id: 'username_and_email',
type: 'text',
displayName: 'User Name'
});

That doesn't seem to make any difference. I don't get any additional fields beyond email, password, and passwordAgain.

I tried adding Meteor's accounts-ui package and configuring it with their USERNAME_AND_EMAIL for the password signup fields, but that also had no effect (so I removed it).

What am I missing?

Also, as I understand it, all of the additional fields are added to the profile object in the user's document. However, Meteor typically places the username field at the top level of the Meteor.user() object, alongside the profile object and the emails array. If username is added via an "additional field," I think it's important that it go at the top level of the user object in the database.

Thanks for your help.

form is not rendered

Hi,
this work is awesome but I have problems shown with the views, on my router.js I got:

this.route('home', {
path: '/',
template: 'home',
onBeforeAction: function(){
AccountsTemplates.setState('sgin');
}
});

and in my home template I got:

In my ATConfig.js I just got:

AccountsTemplates.init();

And this just output:

Sign In

I sure something is missing, I try with the examples but, I got the same result, or is necessary create the login form ?

Thanks.

the form is shown, when I reload the page and I am logged

Hello again,
I got this question, is there any way to compensate the reload ? I mean when I reload the page, and I am logged, shown the sign in form and then shows me the welcome message.

Thanks !

Continuous validation only on sign up

Hi,

Is there a way to only show continuous validation messages when a user signs up? I do not want to show everyone the password requirements when a user signs in.

Thank you.

Regards,
Riaan

layoutTemplates not respected

Hey @splendido just wanted to let you know that I am still having this issue (mentioned in #50). I have a layout defined in my Router.configure and that is showing up despite the following:

AccountsTemplates.configureRoute 'signIn',
  template: 'fullPageAtForm'
  layoutTemplate: 'emptyLayout'
  redirect: '/'

<template name="emptyLayout">
  <!-- noop -->
</template>

issue with 0.12

No such function : stateIs

reproduction repo is for example https://github.com/splendido/test-accounts-templates-semantic-ui

Exception from Deps recompute function: Error: No such function: stateIs
    at http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:2494:15
    at Spacebars.call (http://localhost:3000/packages/spacebars.js?8717c3bee1160f47e7a46ea4e1bd0796f944cad8:169:18)
    at Spacebars.mustacheImpl (http://localhost:3000/packages/spacebars.js?8717c3bee1160f47e7a46ea4e1bd0796f944cad8:106:25)
    at Object.Spacebars.dataMustache (http://localhost:3000/packages/spacebars.js?8717c3bee1160f47e7a46ea4e1bd0796f944cad8:138:39)
    at http://localhost:3000/packages/accounts-templates-semantic-ui.js?689d0c26ab6bc9892c21dcaee4d98940a1bfe72d:63:24
    at null.<anonymous> (http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:2275:44)
    at http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:1805:16
    at Object.Blaze.withCurrentView (http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:2038:12)
    at viewAutorun (http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:1804:18)
    at Deps.Computation._compute (http://localhost:3000/packages/deps.js?d9b2b2601bdab0f57291b38e7974a7190b8aac01:214:36)

Logout not working in Firefox

When trying to logout I get the following error message :

ReferenceError: event is not defined

Looks like you have to specify the event obect in work method parameters. Like this :

'click #at-btn-logout': function(event) {      
        event.preventDefault(); 
        if (AccountsTemplates.isDisabled())  
            return;  
        AccountsTemplates.clearFieldErrors(); 
        Meteor.logout();  
    }

Why can't click forgot password when form is disabled ?

Here is the code blocking the link

AT.prototype.signinFormEvents = {
    'click #at-fpwd': function(event) {
        event.preventDefault();
        if (AccountsTemplates.isDisabled())
            return;

Meteor 0.8.3 issue - Error: No such function: stateIs

Hi,

When I log out I get the following error:

Meteor startup main.js?0896a4f518e153ee1943201a40d81ccbdb62e1f5:5
Exception from Deps recompute function: Error: No such function: stateIs
    at http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:2494:15
    at Spacebars.call (http://localhost:3000/packages/spacebars.js?8717c3bee1160f47e7a46ea4e1bd0796f944cad8:169:18)
    at Spacebars.mustacheImpl (http://localhost:3000/packages/spacebars.js?8717c3bee1160f47e7a46ea4e1bd0796f944cad8:106:25)
    at Object.Spacebars.dataMustache (http://localhost:3000/packages/spacebars.js?8717c3bee1160f47e7a46ea4e1bd0796f944cad8:138:39)
    at http://localhost:3000/packages/accounts-templates-bootstrap.js?882d157f25c21362a804ed24f30af2daf2cb9f4d:65:24
    at null.<anonymous> (http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:2275:44)
    at http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:1805:16
    at Object.Blaze.withCurrentView (http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:2038:12)
    at viewAutorun (http://localhost:3000/packages/blaze.js?309c2a3b573dca998c07c493ba4953d451b2c963:1804:18)
    at Deps.Computation._compute (http://localhost:3000/packages/deps.js?d9b2b2601bdab0f57291b38e7974a7190b8aac01:214:36)

Im working on the accounts-templates-core trunk

Do you know what the problem is?

Thanks.

Riaan

fields' value validation

Perform server-side validation on form data 'submission' only.

Unable to change passwordAgain displayName or placeholder

I tried to use the remove/add sequence to alter the passwordAgain field, but it seems that this field is not replaceable. The label reads as passwordAgain as does the placeholder text. It should probably read Password Again, or Confirm Password.

The more I think about this, it would be nice to not require the password confirmation. Since we have the "forgot password" capability, I don't think it's that important to require the user to confirm their password and I'd really like to reduce the friction of the account creation process. If you look at LinkedIn and Mixpanel as examples, they only have one Password field in their signup flow.

I look forward to your thoughts on this.

Can be fixed by changing atForm.js from this:

if (state === 'resetPwd')
                pwd_field_name = 'password';
            else
                pwd_field_name = 'new_password';
            password = t.find('#AT_field_' + pwd_field_name).value;

to this:

if (state === 'resetPwd')
                pwd_field_name = 'password';
            else
                pwd_field_name = 'password';
            password = t.find('#AT_field_' + pwd_field_name).value;

meteor-useraccounts / core Goto Github PK

core's People

Contributors

Stargazers

Watchers

Forkers

core's Issues

Sign In

Recommend Projects

Recommend Topics

Recommend Org