CRM-15854 - CiviMail workflow, old UI - Consistent interpretation of 'access CiviMail'
authorTim Otten <totten@civicrm.org>
Tue, 3 Mar 2015 02:06:01 +0000 (18:06 -0800)
committerTim Otten <totten@civicrm.org>
Tue, 3 Mar 2015 03:56:32 +0000 (19:56 -0800)
commitcb7b73f07667c97923cf922b4edd483797b2a590
tree40166c087bf0554ce5353c1c7b11d44bdd378733
parentbf5ba10fd9975cff4aa33e8efad316f483c0d3ee
CRM-15854 - CiviMail workflow, old UI - Consistent interpretation of 'access CiviMail'

There are inconstencies in how permissions are interpreted:
 1. Some parts of the UI treat 'access CiviMail' as an overarching permission
    (which implies create+schedule+approve mailings) and treat
    create+schedule+approve as standalone permissions.
 2. Other parts treat 'access CiviMail' as a pre-requisite for create+schedule+approve.

This revision updates various legacy UI's to consistently use the first approach.
CRM/Mailing/Form/Approve.php
CRM/Mailing/Form/Schedule.php
CRM/Mailing/Page/View.php
CRM/Mailing/StateMachine/Send.php
CRM/Mailing/xml/Menu/Mailing.xml