Feature proposal #1547
closedAdd new parameter to allow synchronization or not of email address
Description
As discussed here:
[7:34:18 μμ] Nicholas G. Antimisiaris: Kyle?
[7:34:30 μμ] Nicholas G. Antimisiaris: testing new fb now and have small question
[7:35:00 μμ] Kyle (krileon): sure
[7:35:13 μμ] Nicholas G. Antimisiaris: the fb email thing
[7:35:23 μμ] Nicholas G. Antimisiaris: the email is not synced right?
[7:35:33 μμ] Nicholas G. Antimisiaris: i mean a user can change it afterwards?
[7:36:19 μμ] Kyle (krileon): yes it's synced but i can change that
[7:36:39 μμ] Nicholas G. Antimisiaris: perhaps we should follow same example as twitter here
[7:36:49 μμ] Kyle (krileon): agreed
[7:36:57 μμ] Nicholas G. Antimisiaris: will add to forge
[7:37:01 μμ] Kyle (krileon): asking each user permission just ins't practical
[7:37:09 μμ] Nicholas G. Antimisiaris: now followup question
[7:37:27 μμ] Nicholas G. Antimisiaris: can we somehow inform the user that the email needs to change?
[7:38:02 μμ] Kyle (krileon): it already ensures you change the email before unlinking.. as long as they're linked it won't perticularly matter
[7:38:45 μμ] Nicholas G. Antimisiaris: if they don't update their email, then no notifications will be received from cb site
[7:38:54 μμ] Nicholas G. Antimisiaris: so no onw can send this user an email
[7:39:04 μμ] Kyle (krileon): correct
[7:39:21 μμ] Nicholas G. Antimisiaris: so will be 2nd class user
[7:39:34 μμ] Kyle (krileon): basically
[7:39:40 μμ] Nicholas G. Antimisiaris: need to also try if autowelcome works with fb connect
[7:40:06 μμ] Kyle (krileon): probably won't as registration authentication API hasn't been made yet, but field validation triggers so.. possibly?
[7:42:23 μμ] Kyle (krileon): will set facebook to create a dummy email same as twitter on registration and add another parameter to select if a user wants to synchronize the proxied email and to what field
[7:42:50 μμ] Kyle (krileon): sound good?