-
Bug
-
Resolution: Fixed
-
Minor
-
4.0.9, 4.0.10, 4.0.11, 4.0.12, 4.1.4, 4.1.5, 4.1.6, 4.1.7, 4.1.8, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, 4.3, 4.3.1, 4.3.2
Hi,
I have detected that whether the new login notification is enabled or disabled, the system always adds a new adhoc task to the queue and it always ends in success, reporting that it has sent the email.
Actually I have detected two cases, in both cases the task is added to the queue, but the output is different:
1. Notification active at site level but disabled by default and unlocked. The task is always queued, runs, ends as success and the log says:
Sending login notification to <username>
Notification successfully sent
however, no email is sent. The log is confusing as it says a notification has been sent and it hasn't. Also, I understand that the task should not have been queued in the first place (for users who do not have it active in their profile either).
2. Notification disabled at site level completely. The task is always queued, runs as success and the log says:
Sending login notification to <username>
Failed to send notification
In this case no email is sent either. The output is also confusing as the task is listed as success and then its log says failure. In any case, I understand that the task should not have been queued either if the feature is disabled.
Regards
- has been marked as being related by
-
MDL-80330 Deactivate "new login notifications" from site settings requires manually purging caches when "config settings" cache definition is set to APCu
-
- Open
-