If you select 'approve' on a role application, the user account is automatically activated, which is fine, but, the account activation email is not sent, which is critical because it contains the one time log on link which users need to create their account password.

Comments

Soren Jones’s picture

Status: Active » Postponed (maintainer needs more info)

Can you provide the setup and steps to reproduce? Please include the list of modules you're using. Thanks!

spencer95@gmail.com’s picture

Hi,

The steps to recreate this are:

  1. Install Apply for role
  2. Configure Apply for role so that it allows users to apply for the 'Member' role
  3. Check the permissions so that guests can apply for role
  4. User completes registration form, then checks 'member' role
  5. User gets email message saying account awaiting approval
  6. Admin user gets email (using Trigger/Actions) saying - account applications ready to approve)
  7. Admin goes to People > Apply for role and selects 'Approve'
  8. User account is now activated, with its requested role, but they have no activation email, and therefore, no way to go to the one time login, and therefore can't set a password

These are the modules that I have installed (Yes I know it's a lot!):

acl
admin_menu
advanced_forum
apply_for_role
backup_migrate
backup_migrate_files
better_exposed_filters
better_formats
calendar
captcha
carousel
cf
chain_menu_access
ckeditor_link
conditional_fields
config_perms
content_access
context
context_menu_block
ctools
ctoolsPREV
custom_breadcrumbs
custom_view_modes
date
devel
devel_themer
enabled_modules
entity
entity_example
epsacrop
features
feeds
feeds_fetcher_directory
field_collection
field_permissions
field_slideshow
filefield_sources
filelist.txt
flood_control
forum_access
gmap
google_cse
imce
imce_filefield
imce_wysiwyg
job_scheduler
libraries
link
location
logintoboggan
mail_edit
media
media_update
memcache
menu_block
menu_link
nodeaccess
panels
panels_breadcrumbs
pathauto
pathauto_persist
pathologic
references
rules
security_review
site_map
subscriptions
superfish
tabtamer
taxonomy_display
themekey
token
validate_number
views
views_bulk_operations
views_slideshow
webform
workbench
workbench_access
workbench_files
workbench_media
workbench_moderation
wysiwyg
xmlsitemap

Soren Jones’s picture

Category: bug » support
Priority: Critical » Normal

Thanks!

8. User account is now activated, with its requested role, but they have no activation email, and therefore, no way to go to the one time login, and therefore can't set a password

What are your account settings (Administer > Configuration > People > Account settings)?
What are your Logintoboggan settings?
How are you determining that a user account is activated by approving the 'member' role?

spencer95@gmail.com’s picture

StatusFileSize
new162.44 KB
new48.34 KB

I've attached screenshots of the Account settings and LoginToboggan settings.
I've just tried the approval process again, and after pressing 'Approve' the 'member' role, the user account does not become 'active'. Is this the correct behaviour?

What I would have thought should happen is for the account to be approved, and the one time login email automatically sent, when any role was approved.

Soren Jones’s picture

Category: support » feature
Status: Postponed (maintainer needs more info) » Active

I've just tried the approval process again, and after pressing 'Approve' the 'member' role, the user account does not become 'active'. Is this the correct behaviour?

Yes. That's the correct behavior. AFR doesn't activate or block accounts. It just saves the user with the new role(s).

The behavior you want could be implemented. Rules would be one option, if AFR supported Rules.

spencer95@gmail.com’s picture

Ok, thanks for the feedback. I think it would be good to give the admin the option to auto approve user accounts when approving a user's role, or putting both approve options on the 'Approve role applications' page. Rules integration would also be great.

jnicola’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)

Per notes from previous maintainer, works as designed. Users are approved for role, but their actual account isn't approved.

Tieing the two in may be desirable... but may not be?

If more feature requests come in for this, we'll handle it.