Make WordPress Core

Opened 11 years ago

Closed 3 months ago

Last modified 3 months ago

#30227 closed defect (bug) (fixed)

Inaccurate wording when creating a user with a reserved email address

Reported by: trepmal's profile trepmal Owned by: realloc's profile realloc
Milestone: 6.9 Priority: normal
Severity: normal Version: 3.3.2
Component: Networks and Sites Keywords: has-patch has-copy-review commit
Focuses: multisite, ui-copy Cc:

Description

If you try to create a user on multisite using an email address that is tied to an unconfirmed user, you'll get this notice

That email address has already been used. Please check your inbox for an activation email. It will become available in a couple of days if you do nothing.

"Please check your inbox" seems to imply that the logged in user should check their own inbox for an activation email. Not sure of the best way to reword that so it's clear without being overly wordy. Possibly something like

That email address is reserved pending activation. It will become available in a couple of days if left unconfirmed.

or

That email address is reserved. An activation email has been sent to that address. If left unconfirmed it will become available in a couple of days.

Also, "couple of days" could be any time less than 2 days, so perhaps a dynamic value could be used here giving a better approximatation of the time remaining till the unconfirmed address will be freed up.

This is referenced in #20817

Attachments (2)

30227.diff (1.0 KB) - added by valendesigns 11 years ago.
30227.1.diff (1006 bytes) - added by valendesigns 11 years ago.

Download all attachments as: .zip

Change History (20)

#1 @jeremyfelt
11 years ago

  • Milestone changed from Awaiting Review to Future Release

The "please check your inbox" text could be a prompt for a user that had attempted to register that same email address already.

Another attempt that combines @trepmal's approach and leaves a bit of the original in:

That email address is currently pending activation and is not available for new registration. If you have made a previous attempt with this email address, please check your inbox for an activation email. If left unconfirmed, it will become available in a couple of days.

I also like the idea of making that number dynamic. We already have the # of seconds available to us and can pass that with the string.

#2 follow-up: @johnbillion
11 years ago

"It will become available in a couple of days if you do nothing."

AFAIK this is not the case at all. There is no expiry time on pending user activations.

#3 in reply to: ↑ 2 @jeremyfelt
11 years ago

Replying to johnbillion:

"It will become available in a couple of days if you do nothing."

AFAIK this is not the case at all. There is no expiry time on pending user activations.

wpmu_validate_blog_signup() deletes a pending signup after 2 days if another is requested on the same email address.

// If registered more than two days ago, cancel registration and let this signup go through.
if ( $diff > 2 * DAY_IN_SECONDS )
	$wpdb->delete( $wpdb->signups, array( 'user_email' => $user_email ) );

This ticket was mentioned in Slack in #core by kienstra. View the logs.


11 years ago

@valendesigns
11 years ago

#5 @valendesigns
11 years ago

  • Keywords has-patch needs-testing added

I think @jeremyfelt text is well written. I've added it to a patch.

Cheers,
Derek

#6 @jeremyfelt
11 years ago

Thanks for the patch @valendesigns. Rereading, I think we can be a bit tighter.

Maybe:

"That email address is pending activation and not available for new registration. If you made a previous attempt with this email address, please check your inbox for an activation email. If left unconfirmed, it will become available in a couple of days."

Is it a security annoyance (not really risk) to report the specific time? I'm not imagining a scenario where it would be bad.

"If left unconfirmed, it will be come available in about X hour(s)." could be interesting.

#7 @valendesigns
11 years ago

I don't think we necessarily need to insert the time it becomes available. They should have an activation email in their inbox if they signed up with an email address they actually own. This is really just a reminder. In either case, I've updated the patch with the new string above.

#8 @BurlesonBrad
11 years ago

In case a user deleted the email, should there not also be an option to simply resend it?

#9 @garrett-eclipse
6 years ago

  • Component changed from Text Changes to Login and Registration
  • Focuses ui-copy added

#10 @SirLouen
7 months ago

  • Keywords has-copy-review added; needs-testing removed

I think this can be easily merged, just a copy improvement.
It seems that has been validated by multiple users.

The patch is failing to apply, but it's applied directly here for reference

cc @spacedmonkey @realloc

#11 @SirLouen
7 months ago

  • Component changed from Login and Registration to Networks and Sites

This ticket was mentioned in PR #9107 on WordPress/wordpress-develop by @realloc.


7 months ago
#12

This PR updates the user-facing message displayed when attempting to create a user with an email address that is already pending activation in a WordPress Multisite network.

References

#13 @realloc
7 months ago

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

#14 @realloc
3 months ago

  • Milestone set to 6.9

#15 @spacedmonkey
3 months ago

  • Keywords commit added

This looks good to me. Making as commit.

#16 @westonruter
3 months ago

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

In 61074:

Multisite: Improve wording when creating a user with a reserved email address.

This updates the user-facing message displayed when attempting to create a user with an email address that is already pending activation in a multisite network.

Props realloc, valendesigns, jeremyfelt, SirLouen, westonruter, trepmal, johnbillion, BurlesonBrad, garrett-eclipse, spacedmonkey, westonruter.
Fixes #30227.

#17 @westonruter
3 months ago

(Doubled self-prop in r61074 was not intentional!)

@westonruter commented on PR #9107:


3 months ago
#18

Committed in r61074.

Note: See TracTickets for help on using tickets.