Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-2333

Verify and/or Fix CiviMail Token Behaviors


    • Type: Task
    • Status: Done/Fixed
    • Priority: Major
    • Resolution: Fixed/Completed
    • Affects Version/s: 1.9
    • Fix Version/s: 1.9
    • Component/s: CiviMail
    • Labels:


      Tasks for this issue:

      • Make upload and compose methods use the same logic for validation. (These tokens are NOT valid for Send Mailing context: {resubscribe.group} {unsubscribe.group} {welcome.group} {subscribe.group}


      • Remove the donate token. We will look at implementing trackable links for contribution pages in 2.1 (CRM-2332)
      • Test the {action.forward) token. It should be "valid" only in the "Send Mailing" context (body, header, footer). It's use is for forwarding mailings to up to five email addresses. It should resolve to an URL with a form for the forwardees' addresses. When this form is submitted, email is forwarded and the forward action is tracked/shows up in the Mailing Report.
      • Verify that all four domain.* tokens "work" in the following elements:
      • Send Mailing Body (upload or compose)
      • Send Mailing Footer / Header
      • Reply, Subscribe, Welcome, Unsubscribe, Optout, Resubscirbe
        automated messages
      • Add new tokens for subscribe email and URL: {action.subscribe}



        . action.subscribe requires a GROUP ID parameter (e.g. action.subscribe.2). Group ID is optional for action.subscribeUrl

      • Review token validation logic and update this issue with needed fixes if any. We do NOT want to introduce bottlenecks in the code - but ideally we should check for unrecognized tokens and tokens that are not valid in a given context (e.g. welcome.group is NOT valid in a Mailing body).




            • Assignee:
              shailesh Shailesh Lende
              dgg David Greenberg
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: