Skip to:

Opened 11 months ago

Closed 3 months ago

#8977 closed enhancement (fixed)

Ability to trigger resend of account activation email via REST API

Reported by: niftythree's profile niftythree Owned by: espellcaste's profile espellcaste
Milestone: 14.0.0 Priority: normal
Severity: normal Version: 12.4.0
Component: REST API Keywords: has-patch


Hi there,

We are seeing examples of users creating an account (triggering an account activation email to be sent), but then choose not to activate their account, returning at a later date to try and sign into their account again without realising that they haven't activated their account. If this happens on the website, it's not generally too much of a problem because they're provided with a link to resend an activation email when they attempt to login.

However, users are now more frequently accessing our app, so we would like to also provide the option for them to resend the activation email via the REST API. Is this something that can be implemented into the REST API via an additional endpoint?


Change History (10)

#1 @imath
11 months ago

  • Milestone changed from Awaiting Review to Up Next

Thanks for your report @niftythree once again, I agree:

#2 @niftythree
11 months ago

Thank you @imath 🙂

#3 @imath
7 months ago

  • Milestone changed from Up Next to 14.0.0

#4 @espellcaste
7 months ago

  • Owner set to espellcaste
  • Status changed from new to assigned

I plan to work on this feature.

#5 @espellcaste
3 months ago

  • Keywords has-patch added
  • Version set to 12.4.0

provided with a link to resend an activation email when they attempt to login.

I just realized this is not a core feature. Maybe we should add it.

@niftythree I have a pull request ready.

But I'd like a second opinion on the schema of the response. Currently, I'm only returning this if the resend action is successful:

  "sent": true

I don't think we need to return the whole signup object. Only if it failed and/or if it succeded. Thoughts?

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

This ticket was mentioned in Slack in #buddypress by espellcaste. View the logs.

3 months ago

#7 @niftythree
3 months ago

Hi @espellcaste

Thanks for the update.

We're not sure if you were wanting an opinion from us, but we agree with your approach. 🙂

#8 @espellcaste
3 months ago

@niftythree That's correct. I'd like an opinion about the returned schema/response. The example provided, to me, is sufficient.

#9 @niftythree
3 months ago

Thanks @espellcaste. We agree that the schema/response is sufficient. Thanks for your work on this.

#10 @espellcaste
3 months ago

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

Thanks! That's going to be bundled with the next release.

Note: See TracTickets for help on using tickets.