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.
Bug
Major
Paul Phillips
created issue -
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.