Sending email for unselected level type

Created on 30 April 2024, 7 months ago
Updated 8 August 2024, 3 months ago

Problem/Motivation

I am seeing email for "warning" type emails. I only have the following level types selected: Emergency, Alert, Critical, Error.

Steps to reproduce

This is a fresh install of version 4.0.2 of this module.

πŸ› Bug report
Status

Postponed: needs info

Version

4.0

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States irodriguez

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @irodriguez
  • Assigned to praveen rani
  • Hi, I resolved above issue now all types are selected by default and created MR. Please review it.

    Thank you.

  • Issue was unassigned.
  • Status changed to Needs review 7 months ago
  • πŸ‡ΊπŸ‡ΈUnited States irodriguez

    I am sorry for my ignorance. How do you review the issue?

  • πŸ‡·πŸ‡΄Romania Kosa Ilma

    Hi everyone.

    @praveen rani sorry, but your MR does not solve the originally reported bug. The bug means, that the module sends an email about an unselected severity type (warning). The fix for this is not to select all severity types by default. If all severities are selected by default, but someone unselects the Warning, the problem returns.

    We intentionally configured the module not to send emails about all severity types by default. We wanted to get emails about major problems on sites. We gave the oportunity module users to to configure the module to get emails about different severities, but not by default.

    I tried to reproduce the reported bug, but couldn't.
    I turned this module on a 10.3.0 drupal core, did not change the default configurations, the module did not send emails about warnings.
    I have tried with 2 versions of this module: 4.0.5, which is the latest release and 4.0.2, which is the version reported by the issue.

    @irodriguez, if you have any information about the problem, please write it down for us.

    Thank you!

  • Hello,
    I also tried to reproduce the error as mentioned by @irodriguez but could not. I tried to reproduce it for 4.0.2 release as well as the 4.0.x-dev branch, but found everything working as expected.

  • Status changed to Postponed: needs info 3 months ago
  • πŸ‡­πŸ‡ΊHungary szato
Production build 0.71.5 2024