Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
Don't know if this is useful for other people but for our site we want the a number to be available to be used up until the point of confirmation. Patch included below.
Comments
Comment #1
artkon CreditAttribution: artkon commentedComment #2
christianchristensen CreditAttribution: christianchristensen commentedRe-rolling this patch to properly apply with make/patch and specifically against 6.x-1.0 branch.
Comment #3
christianchristensen CreditAttribution: christianchristensen commentedRelated issue: #1330402: Checking for number confirmation status.
Comment #4
christianchristensen CreditAttribution: christianchristensen commentedLooked at this a little closer and it looks like the previous patches have some missing components (possible patch of patch); please see attached.
Comment #5
christianchristensen CreditAttribution: christianchristensen commentedThis removes the accidental site specific verbiage in the previous patch.
Comment #6
maksim24 CreditAttribution: maksim24 commentedWhat we should do if user see that his phone number is used other user? I think we should add link where new user can confirm his number.
Comment #7
almaudoh CreditAttribution: almaudoh commentedI don't agree with the idea that users can use unconfirmed numbers to send messages. This exposes vulnerability for spamming with fake phone numbers. On the other hand, for sites that have such a use case as in this issue, we may consider making this configurable via the admin UI.
This feature may be considered for 8.x-1.x version.
Comment #8
dpiPerhaps a better solution is if a phone number is already claimed, then the phone number is removed on the other user. Its not a good idea to expose the existing usage of a number.
Comment #9
dpiwordy
Comment #10
C.E.A CreditAttribution: C.E.A commentedI so agree with the #8 comment especially that Facebook uses the same approach.
As per comment #7:
I believe this should be a must and let the administrator decide on whether to enable/disable this on his own website.
So... after years, any update on this issue ?
Thank you,