CRM-16237 CiviMail: 4.6.0 ignores "mandatory tokens" in message footers

          Details

          • Type: Bug
          • Status: Done/Fixed
          • Priority: Major
          • Resolution: Fixed/Completed
          • Affects Version/s: 4.6
          • Fix Version/s: 4.6.1
          • Component/s: CiviMail
          • Labels:
            None
          • Documentation Required?:
            None

            Description

            From forum: http://forum.civicrm.org/index.php?topic=36239

            "When composing a new message or resuming a draft, I get a "required tokens are missing" error. The only way to clear the error is to place both the

            {domain.address}

            token and an OptOut or Unsubscribe token in the BODY of the message. The fact that one or both of these tokens is already present in my message footer does not matter. The setting of "Disable mandatory tokens" also makes no difference."

              Attachments

                Activity

                [CRM-16237] CiviMail: 4.6.0 ignores "mandatory tokens" in message footers
                Tim Otten added a comment -

                PR: https://github.com/civicrm/civicrm-core/pull/5579

                David Greenberg added a comment -

                PR fixes problem w/ mandatory tokens not recognized in footer.

                However, the mandatory token check is NOT being disabled when I check the box to "Disable check for mandatory tokens" under CiviMail Component Settings.

                Tim Otten added a comment -

                PR for respecting the "Disable" option: https://github.com/civicrm/civicrm-core/pull/5585

                David Greenberg added a comment -

                Tested both options (w/ and w/o tokens requirement disabled). Works as expected.

                  People

                  • Assignee:
                    David Greenberg
                    Reporter:
                    Tim Otten

                    Dates

                    • Created:
                      Updated:
                      Resolved: