CRM-19690 - Task_AdhocMailing - Use highest-priority template type
authorTim Otten <totten@civicrm.org>
Tue, 17 Jan 2017 09:41:39 +0000 (01:41 -0800)
committerTim Otten <totten@civicrm.org>
Tue, 17 Jan 2017 09:41:39 +0000 (01:41 -0800)
commit0051bad38249263b754b10bead872ace0887aba2
tree6dfa0c066600cadaca1da0657768df109215efe9
parent3197bbcbb90c13b10ff53c35631da16d4a6cf809
CRM-19690 - Task_AdhocMailing - Use highest-priority template type

If you perform a contact search and create a new mailing, it would use
`template_type=traditional`, even if another template type had greater
priority. With this patch,  it respects the priority.

Note: I considered changing the default in Mailing.create API to always
match most-preferred template-type.  However, that would break some existing
API consumers (e.g.  headless consumers or ones who define their own UI).
For external API-based integrations, we should preserve the default
semantics of `body_text`/`body_html` by defaulting to
`template_type=traditional`.

The preference in CRM-19690 is that any use-case based on the screen
`civicrm/a/#/mailing/{id}` should have its default determined by weight.
CRM/Mailing/Form/Task/AdhocMailing.php