No submission button on sign-in page?

[misutowolf]

Not sure if this is something wrong on my end as far as user error, or a bug in the package, but when I try to log in to my small app with /sign-in, there's no button to submit the sign-in form, and hitting Enter doesn't work either. Registration is fine.

[misutowolf]

I think I found the problem in client/views/signIn/signIn.html.

I made a small one-line tweak and hopefully that fixes it.

[nunohvidal]

@misutowolf I am having exactly the same issue. Can you please post the tweak you made?

[misutowolf]

@nunohvidal The following fixes the problem, I'm using it with no issues (of this kind, anyway) right now:

Fork: Fixes issue #229

[aramk]

Can the merge conflicts in #240 be fixed and merged in? As it stands the stable version of this package is broken when using passwordSignupFields: 'USERNAME_ONLY'.

[aramk]

It also relies on a package which isn't available for 0.9 yet, so shouldn't it transitively be marked unavailable for 0.9? https://atmospherejs.com/joshowens/simple-form

[aramk]

And there's a PR for the simple-form library to make it compatible with 0.9 but it's been a month without a response, forcing anyone who depends on this library to fork their own version or sit on their hands. If the owner can't find the time to maintain the project, perhaps a collaborator is in need.
thespacedojo/simple-form#20

[queso]

This package installs and works just fine with 0.9. I built a brand new app for the Mastering Meteor class on 0.9 and used accounts-entry as the login system with the one issue of redirection after login.

What exactly makes you think you can't use accounts-entry?

[aramk]

When I install this with the option passwordSignupFields: 'USERNAME_ONLY' the submit button disappears because of this unless block: https://github.com/Differential/accounts-entry/blob/master/client/views/signIn/signIn.html#L38. #240 fixes this issue but I wasn't sure why it hadn't been merged in. I thought perhaps it was intentionally in that block but couldn't understand why.

[aramk]

@queso Just wondering - is #240 ok to merge in? It seems like an important fix, otherwise the signup button doesn't appear with `passwordSignupFields: 'USERNAME_ONLY'.