Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-5089

Universal Module: Suspend reason isn't included in notifications

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.9.0
    • Fix Version/s: 5.10.0-b1
    • Component/s: Modules
    • Labels:
      None

      Description

      When a service is suspended that uses the universal module, the suspend reason is not sent in the notifications. The notification seems to include the "previous" pre-update state/information rather than the most current. Suspend reason should be included in a suspend action and anything else that may have changed.

        Activity

        Hide
        admin Paul Phillips added a comment -

        Abdy Franco

        To reproduce, do the following:

        1. Create a universal module product. For Suspend enter your email address. Under "Email Notification" add the tag:

        {% debug%}

        so that everything is included.
        2. Create a Package using the product.
        3. Add a service using the Package to a client.
        4. Manually suspend the service as an admin and enter a reason.
        5. The Universal Module sends you an email with debug information (all tag/data info)

        Note that [_service] element contains:
        [suspension_reason] =>

        Which is an empty response.

        Next:

        1. Unsuspend the services
        2. Suspend the service again and enter a DIFFERENT reason
        3. Note that the email contains the PREVIOUS/ORIGINAL reason for the suspension

        [suspension_reason] => This is my original reason for suspension.

        Show
        admin Paul Phillips added a comment - Abdy Franco To reproduce, do the following: 1. Create a universal module product. For Suspend enter your email address. Under "Email Notification" add the tag: {% debug%} so that everything is included. 2. Create a Package using the product. 3. Add a service using the Package to a client. 4. Manually suspend the service as an admin and enter a reason. 5. The Universal Module sends you an email with debug information (all tag/data info) Note that [_service] element contains: [suspension_reason] => Which is an empty response. Next: 1. Unsuspend the services 2. Suspend the service again and enter a DIFFERENT reason 3. Note that the email contains the PREVIOUS/ORIGINAL reason for the suspension [suspension_reason] => This is my original reason for suspension.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              5/Apr/24

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours, 48 minutes
              2h 48m

                Agile