You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 6, 2019. It is now read-only.
When the registration type is none, creating a user and ticking the checkbox to notify him does not send an email to the user.
Steps to reproduce
List the steps to reproduce the behavior:
In Security -> Member Accounts, set the registration type to none
In Users, create a new user and tick the "Send an email to the new user" checkbox
Current result
The admin receives an email but not the user
Expected result
The user should receive the email
Additional context
This was previously discussed here dnnsoftware/Dnn.Platform#2424 and an inital PR #2492 was merged to bring the logic in to the core but the corresponding UI part needs to be updated to use this new method signature. The signature just accepts one additional bool parameter to notify the user or not and already checks the registration mode of the site to decide which email to send.
Affected version
9.2.2
9.2.1
9.2
[?] 9.1.1
[?] 9.1
[?] 9.0
The text was updated successfully, but these errors were encountered:
Description of bug
When the registration type is none, creating a user and ticking the checkbox to notify him does not send an email to the user.
Steps to reproduce
List the steps to reproduce the behavior:
Current result
The admin receives an email but not the user
Expected result
The user should receive the email
Additional context
This was previously discussed here dnnsoftware/Dnn.Platform#2424 and an inital PR #2492 was merged to bring the logic in to the core but the corresponding UI part needs to be updated to use this new method signature. The signature just accepts one additional bool parameter to notify the user or not and already checks the registration mode of the site to decide which email to send.
Affected version
The text was updated successfully, but these errors were encountered: