When a new user is awaiting administrator approval, he still receives the same message as normal sign-up. This is very confusing for the new user who might think that the account is approved already and the email is announcing it. Two ways to improve this:

1. Just delay that email until the administrator approves the application.
2. Send two emails, one as a feedback sign-up request received / approval pending and another one that is send when the administrator has approved the request with login info.

Comments

webchick’s picture

There actually is a "pending approval" email which you can edit under admin/settings/user to not look the same as the "I just created an account" e-mail. But I agree that "normal" e-mails should be sent out when the user is actually approved. The tricky part here is that there's no way to determine when a blocked user moved to active signifiies approval by an admin or whether you've just unbanned a user, to my knowledge..?

LAs4n’s picture

Version: x.y.z » 7.x-dev

Still a feature request?

Moving to cvs.

ñull’s picture

Even though you can change the text of the message, the administrator still needs to warn the user manually that he is approved. There is no automatic facility for that in Drupal.

The problem of distinguishing can be solved when you allow a user to have a deactivated "Authenticated user" role. You then get the following states:

1. User anonymous never signed up, never logged in. No user record
2. User signed up but not yet approved by Admin: User is Active but "Authenticated user" role is not set so he has no other roles then an anonymous user.
3. User signed up and approved by Admin: User is Active, "Authenticed user" role is active (and any other role the Admin activated ). Turning on "Authenticated user" role should trigger the warning message that the user was approved.
4. User signed up or not, but Admin decided to block him: User is inactive, the roles can be active but became without effect. A block message can be sent when there was a change from Active to Blocked.

With this scheme Active / Blocked takes on a unique meaning of being banned from login or not, while the (undeletable default) role "Authenticated user" takes on the meaning of being approved or not.

So with this solution I think it is still a valid feature request. Please keep it.

valthebald’s picture

Version: 7.x-dev » 8.x-dev

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dpi’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Both Drupal 7 and 8 have:

Account details for [user:name] at [site:name] (approved) and Account details for [user:name] at [site:name] (pending admin approval) templates.