search

formtools / module-submission_accounts

The Submission Accounts module.
https://docs.formtools.org/modules/submission_accounts/
GNU General Public License v3.0
2 stars 7 forks source link

Login page - Email vs. username field? #6

Open ocbroadband opened 6 years ago

ocbroadband commented 6 years ago

I have this working in v3.0.6. Appears its just a label issue. When you get to the login page, it says 'Email' for the username. However, it does NOT want your email, it wants the username field you specified in the configuration. If I switch the target fields around in the configuration of the Submission account, it works as expected based on the naming on the login page.

image

benkeen commented 6 years ago

Hey @ocbroadband, sorry it's not terribly clear - agreed.

The "Username" field should be whatever field you want to act as the login username. So in the screenshot above, you've chosen to use the Email Address field. That's pretty normal: users will then login using their email address to identify them.

But the "Email Field" is mapped to the "Username" field in your form, which means that any emails get sent out (e.g. the "forgot password" email) will be sent to whatever value is in the Username field. Which obviously won't work.

ocbroadband commented 6 years ago

Well, the point I was trying to make is the 'label' on the actual login page says 'Email', so its a bit confusing when I put the fields correctly on the backend, but on the front end, when someone looks at the page, and it says, enter my email, they do, and it doesn't allow them to login because its actually looking for their 'username' to be in that field. :) My suggestion was to place the label 'username' on the field as the label so that it matches what your putting on the backend. Based on what your saying, I have to change it back so it matches on the backend as well due to it needing the email in the email field. How can I change the label on the front end to match the field name correctly.

[image: image.png] The above should really say 'username'. Or, in the backend, give a option to select either the 'username' or the 'email' to be used as the login. But I would figure it would be easier and make more sense to just update the label of the field to match what its expecting. :)

On Fri, Sep 7, 2018 at 10:06 PM Benjamin Keen notifications@github.com wrote:

Hey @ocbroadband https://github.com/ocbroadband, sorry it's not terribly clear - agreed.

The "Username" field should be whatever field you want to act as the login username. So in the screenshot above, you've chosen to use the Email Address field. That's pretty normal: users will then login using their email address to identify them.

But the "Email Field" is mapped to the "Username" field in your form, which means that any emails get sent out (e.g. the "forgot password" email) will be sent to whatever value is in the Username field. Which obviously won't work.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/formtools/module-submission_accounts/issues/6#issuecomment-419613488, or mute the thread https://github.com/notifications/unsubscribe-auth/ANAF8_HWXoVTvYlURLygBcZoOPvlLdecks5uY1BlgaJpZM4WfHok .