You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Loopback PUT Request turn emailVerified to "false" #3059
It doesn't, this happen any change you do in the User's model.
I've fixed it changing user.js at line 863:
// return data.email != ctx.data.email; original
return ctx.data.email && data.email != ctx.data.email; //fix
Temporary workaround for those in need:
With any PUT to the User model, you can include the existing/current email address, and it will save everything else correctly without invalidating the email.
Activity
rusackas commentedon Jan 3, 2017
Experiencing the same problem here. We have an admin tool that sets emailVerified to true via a pot request, but it stopped working.
benbrown commentedon Jan 4, 2017
This appears to be caused by a change in v2.36.2, which is attempting to set emailVerified to false when a user changes their email address.
This should ONLY happen when the email address actually changes, not ANY time a user record is modified!
gaecer commentedon Jan 5, 2017
It doesn't, this happen any change you do in the User's model.
I've fixed it changing user.js at line 863:
// return data.email != ctx.data.email; original
return ctx.data.email && data.email != ctx.data.email; //fix
rusackas commentedon Jan 5, 2017
Temporary workaround for those in need:
With any PUT to the User model, you can include the existing/current email address, and it will save everything else correctly without invalidating the email.
davidcheung commentedon Jan 10, 2017
this bug should be fixed in #3053 or in (2.x) #3072, please ping me in this thread if issue persists to reopen. Closing now.
gaecer commentedon Jan 10, 2017
dancingshell commentedon Jan 11, 2017
tl;dr... was/is this an issue for loopback 3.x.x?