Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.5.0-b4
-
Fix Version/s: None
-
Component/s: Modules
-
Labels:None
Description
The Universal Module currently sets the
{% debug %}email template tag by default for products. We should remove that tag from being set by default. This will improve usability by not requiring them to remove it.
We should consider updating the notification tags to include an array of these field names. This would help categorize field names, and avoid the possibilty of fields being overwritten if the package field name is the same as the service field name.
Consider:
Package field names -> {_package_fields} (e.g. {_package_fields.name})
Service field names -> {_service_fields} (e.g. {_service_fields.name})
Existing fields would need to be maintained for backward compatibility.
Issue Links
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
Link | This issue relates to CORE-788 [ CORE-788 ] |
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
Description |
The Universal Module currently sets the {% debug %} email template tag by default for products. We should remove that tag from being set by default. This will improve usability by not requiring them to remove it.
See http://www.blesta.com/forums/index.php?/topic/4533-debug-tag-added-by-default-in-the-universal-module/ |
The Universal Module currently sets the {% debug %} email template tag by default for products. We should remove that tag from being set by default. This will improve usability by not requiring them to remove it.
See http://www.blesta.com/forums/index.php?/topic/4533-debug-tag-added-by-default-in-the-universal-module/ We should consider updating the notification tags to include an array of these field names. This would help categorize field names, and avoid the possibilty of fields being overwritten if the package field name is the same as the service field name. Consider: Package field names -> {_package_fields} (e.g. {_package_fields.name}) Service field names -> {_service_fields} (e.g. {_service_fields.name}) Existing fields would need to be maintained for backward compatibility. |
Tyson Phillips (Inactive)
made changes -
Story Points | 1 |
Tyson Phillips (Inactive)
made changes -
Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.1.0 Sprint 4 [ 41 ] |
Tyson Phillips (Inactive)
made changes -
Assignee | Tyson Phillips [ tyson ] |
Jonathan Reissmueller
made changes -
Assignee | Jonathan Reissmueller [ jonathan ] |
Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
Status | Open [ 1 ] | In Progress [ 3 ] |
Automated transition triggered when Jonathan Reissmueller created pull request #3 in Stash -
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #3 in Stash -
Status | In Review [ 5 ] | Closed [ 6 ] |