Skip to:
Content

BuddyPress.org

Opened 3 months ago

Closed 3 months ago

Last modified 3 months ago

#9267 closed defect (bug) (fixed)

Buddypress v14.3.3 does not check if the user_email exists in the signups when creating a new signup

Reported by: pratiklondhe's profile pratiklondhe Owned by:
Milestone: Awaiting Review Priority: high
Severity: major Version: 14.3.2
Component: Members Keywords:
Cc:

Description

hi, it seems in the new Buddypress version, the code that checked if the email address exists in a signup or not has been removed causing issue where users are able to signup using same emails multiple times as long as that email is not activated.

svn link for the 14.4.4 tag : https://buddypress.trac.wordpress.org/browser/tags/14.3.3/src/bp-members/bp-members-functions.php?rev=14094#L1604

GitHub link where the signup validation does exists:

https://github.com/buddypress/buddypress/blob/f1bffedb2c7835744169a4623c3955bea6d2796f/src/bp-members/bp-members-functions.php#L1639-L1652

Change History (7)

#1 in reply to: ↑ description @pratiklondhe
3 months ago

Replying to pratiklondhe:

hi, it seems in the new Buddypress version, the code that checked if the email address exists in a signup or not has been removed causing issue where users are able to signup using same emails multiple times as long as that email is not activated.

svn link for the 14.4.4 tag : https://buddypress.trac.wordpress.org/browser/tags/14.3.3/src/bp-members/bp-members-functions.php?rev=14094#L1604

GitHub link where the signup validation does exists:

https://github.com/buddypress/buddypress/blob/f1bffedb2c7835744169a4623c3955bea6d2796f/src/bp-members/bp-members-functions.php#L1639-L1652

correction: the svn link is for 14.3.3v tag

#2 follow-up: @espellcaste
3 months ago

  • Resolution set to fixed
  • Status changed from new to closed

duplicate of #9137

#3 in reply to: ↑ 2 @pratiklondhe
3 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Replying to espellcaste:

duplicate of #9137

may I know where is this fixed?

#4 follow-up: @espellcaste
3 months ago

  • Resolution set to fixed
  • Status changed from reopened to closed

@pratiklondhe This is fixed in 15, at #9137, at [14071] it won't be ported back to legacy versions.

#5 in reply to: ↑ 4 @pratiklondhe
3 months ago

Replying to espellcaste:

@pratiklondhe This is fixed in 15, at #9137, at [14071] it won't be ported back to legacy versions.

so in the next release right ?
any idea why this was removed in the first place as I am able to see it being there earlier but later removed.

#6 follow-up: @espellcaste
3 months ago

@pratiklondhe The github link you pointed to goes to trunk, this one goes to the 14.3.3 version. It doesn't have that code yet.

I'm not sure if you saw it in trunk and incorrectly assumed it was available before, because as far as I know, this issue always existed before it was patched.

Last edited 3 months ago by espellcaste (previous) (diff)

#7 in reply to: ↑ 6 @pratiklondhe
3 months ago

Replying to espellcaste:

@pratiklondhe The github link you pointed to goes to trunk, this one goes to the 14.3.3 version. It doesn't have that code yet.

I'm not sure if you saw it in trunk and incorrectly assumed it was available before, because as far as I know, this issue always existed before it was patched.

  • ahh got it, I assumed wrong, thanks for being patient with this!
Note: See TracTickets for help on using tickets.