require: '^crmUiIdScope',
restrict: 'EA',
scope: {
- // {title, name, help}
+ // {title, name, help, helpFile}
crmUiField: '='
},
templateUrl: function(tElement, tAttrs){
transclude: true,
link: function (scope, element, attrs, crmUiIdCtrl) {
$(element).addClass('crm-section');
- scope.crmUiHelpFile = scope.$parent.crmUiHelpFile; // propagate default
+ // Inherit helpFile from parent scope if not specified
+ scope.crmUiHelpFile = scope.crmUiField.helpFile || scope.$parent.crmUiHelpFile;
}
};
})
});
scope.crmMailingConst = CRM.crmMailing;
scope.ts = CRM.ts(null);
- scope.crmUiHelpFile = 'CRM/Mailing/Form/Upload';
+ scope.crmUiHelpFile = 'CRM/Mailing/MailingUI';
scope[directiveName] = attr[directiveName] ? scope.$parent.$eval(attr[directiveName]) : {};
$q.when(crmMetadata.getFields('Mailing'), function(fields) {
scope.mailingFields = fields;
scope.crmMailingConst = CRM.crmMailing;
scope.crmMailingABCriteria = crmMailingABCriteria;
scope.ts = CRM.ts(null);
+ scope.crmUiHelpFile = 'CRM/Mailing/MailingUI';
var fieldsModel = $parse(attr[directiveName]);
scope.fields = fieldsModel(scope.$parent);
-->
<div class="crm-block" ng-form="subform" crm-ui-id-scope>
<div class="crm-group" ng-controller="EmailBodyCtrl">
- <div crm-ui-field="{name: 'subform.header_id', title: ts('Mailing Header')}">
+ <div crm-ui-field="{name: 'subform.header_id', title: ts('Mailing Header'), help: 'header'}">
<select
crm-ui-id="subform.header_id"
name="header_id"
<option value=""></option>
</select>
</div>
- <div crm-ui-field="{name: 'subform.footer_id', title: ts('Mailing Footer')}">
+ <div crm-ui-field="{name: 'subform.footer_id', title: ts('Mailing Footer'), help: 'footer'}">
<select
crm-ui-id="subform.footer_id"
name="footer_id"
<a crm-icon="disk" ng-click="saveTemplate(mailing)" class="crm-hover-button" title="{{ts('Save As')}}"></a>
</div>
</div>
- <div crm-ui-field="{name: 'subform.fromAddress', title: ts('From'), help: 'id-from_email'}">
+ <div crm-ui-field="{name: 'subform.fromAddress', title: ts('From'), help: 'from_email'}">
<div ng-controller="EmailAddrCtrl" crm-mailing-from-address="fromPlaceholder" crm-mailing="mailing">
<select
crm-ui-id="subform.fromAddress"
-->
<div class="crm-block" ng-form="subform" crm-ui-id-scope>
<div class="crm-group">
- <div crm-ui-field="{name: 'subform.mailingName', title: ts('Mailing Name')}">
+ <div crm-ui-field="{name: 'subform.mailingName', title: ts('Mailing Name'), help: 'name'}">
<div>
<input
crm-ui-id="subform.mailingName"
name="mailingName" />
</div>
</div>
- <div crm-ui-field="{name: 'subform.campaign', title: ts('Campaign')}" ng-show="crmMailingConst.campNames.length > 0">
+ <div crm-ui-field="{name: 'subform.campaign', title: ts('Campaign'), help: 'id-campaign_id', helpFile: 'CRM/Campaign/Form/addCampaignToComponent'}" ng-show="crmMailingConst.campNames.length > 0">
<select
crm-ui-id="subform.campaign"
name="campaign"
</div>
- <div crm-ui-field="{name: 'subform.fromAddress', title: ts('From')}" ng-if="fields.fromAddress">
+ <div crm-ui-field="{name: 'subform.fromAddress', title: ts('From'), help: 'from_email'}" ng-if="fields.fromAddress">
<span ng-controller="EmailAddrCtrl" crm-mailing-from-address="fromPlaceholder" crm-mailing="abtest.mailings.a">
<select
crm-ui-id="subform.fromAddress"
</select>
</span>
</div>
- <div crm-ui-field="{name: 'subform.fromAddressA', title: ts('From (A)')}" ng-if="fields.fromAddressA">
+ <div crm-ui-field="{name: 'subform.fromAddressA', title: ts('From (A)'), help: 'from_email'}" ng-if="fields.fromAddressA">
<span ng-controller="EmailAddrCtrl" crm-mailing-from-address="fromPlaceholder" crm-mailing="abtest.mailings.a">
<select
crm-ui-id="subform.fromAddressA"
</select>
</span>
</div>
- <div crm-ui-field="{name: 'subform.fromAddressB', title: ts('From (B)')}" ng-if="fields.fromAddressB">
+ <div crm-ui-field="{name: 'subform.fromAddressB', title: ts('From (B)'), help: 'from_email'}" ng-if="fields.fromAddressB">
<span ng-controller="EmailAddrCtrl" crm-mailing-from-address="fromPlaceholder" crm-mailing="abtest.mailings.b">
<select
crm-ui-id="subform.fromAddressB"
{{ts('A/B testing allows you to send two test mailings to a random subset of your recipients. After collecting and
comparing metrics, the more successful mailing will be sent to the remaining recipients.')}}
</div>
- <div crm-ui-field="{name: 'setupForm.abName', title: ts('Name')}" ng-if="fields.abName">
+ <div crm-ui-field="{name: 'setupForm.abName', title: ts('Name'), help: 'name'}" ng-if="fields.abName">
<input
crm-ui-id="setupForm.abName"
name="abName"
placeholder="A/B Test Name"
required/>
</div>
- <div crm-ui-field="{name: 'setupForm.campaign', title: ts('Campaign')}" ng-show="crmMailingConst.campNames.length > 0"
+ <div crm-ui-field="{name: 'setupForm.campaign', title: ts('Campaign'), help: 'id-campaign_id', helpFile: 'CRM/Campaign/Form/addCampaignToComponent'}" ng-show="crmMailingConst.campNames.length > 0"
ng-if="fields.campaign">
<select
crm-ui-id="setupForm.campaign"
--- /dev/null
+{*
+ +--------------------------------------------------------------------+
+ | CiviCRM version 4.4 |
+ +--------------------------------------------------------------------+
+ | Copyright CiviCRM LLC (c) 2004-2013 |
+ +--------------------------------------------------------------------+
+ | This file is a part of CiviCRM. |
+ | |
+ | CiviCRM is free software; you can copy, modify, and distribute it |
+ | under the terms of the GNU Affero General Public License |
+ | Version 3, 19 November 2007 and the CiviCRM Licensing Exception. |
+ | |
+ | CiviCRM is distributed in the hope that it will be useful, but |
+ | WITHOUT ANY WARRANTY; without even the implied warranty of |
+ | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
+ | See the GNU Affero General Public License for more details. |
+ | |
+ | You should have received a copy of the GNU Affero General Public |
+ | License and the CiviCRM Licensing Exception along |
+ | with this program; if not, contact CiviCRM LLC |
+ | at info[AT]civicrm[DOT]org. If you have questions about the |
+ | GNU Affero General Public License or the licensing of CiviCRM, |
+ | see the CiviCRM license FAQ at http://civicrm.org/licensing |
+ +--------------------------------------------------------------------+
+*}
+{htxt id="name"}
+ <p>
+ {ts}Assign a unique name to each of your mailings. Select a naming convention that will help keep your mailings organized and easy to find when you want to review and compare mailing results. For example, if you do a monthly general-interest newsletter - you might use the following naming convention:{/ts}
+ </p><p>
+ <strong>{ts}General Monthly Newsletter: 200709{/ts}</strong>
+</p>
+{/htxt}
+
+{htxt id ="from_email"}
+ <p>{ts}Select the "FROM" Email Address for this mailing from the dropdown list. Available email addresses are configurable by users with Administer CiviCRM permission. EXAMPLE: "Client Services" <clientservices@example.org>{/ts}</p>
+{if call_user_func(array('CRM_Core_Permission','check'), 'administer CiviCRM') }
+ {capture assign="fromConfig"}{crmURL p="civicrm/admin/options/from_email_address" q="reset=1"}{/capture}
+ <p>{ts 1=$fromConfig}Go to <a href='%1'>Administer CiviCRM » Communications » FROM Email Addresses</a> to add or edit email addresses. Make sure these email addresses are valid email accounts with your email service provider.{/ts}</p>
+{else}
+ {ts}Contact your site administrator if you need to use a "FROM" Email Address which is not in the dropdown list.{/ts}
+{/if}
+{/htxt}
+
+{htxt id="html"}
+ <p>{ts}You can choose to send BOTH an <strong>HTML</strong> and a plain <strong>TEXT</strong> version of your mailing, OR you can send a <strong>TEXT</strong> version only.{/ts}</p>
+ <p>{ts}If you create only an <strong>HTML</strong> version, CiviMail will automatically create a <strong>TEXT</strong> version for your recipients who have chosen NOT to receive HTML email.{/ts}</p>
+ <h1>{ts}Required Elements{/ts}</h1>
+ <p>{ts}CiviMail email messages must include an <strong>opt-out</strong> link ("Opt out via web page"), and the <strong>postal address</strong> of your organization. These elements help reduce the chances of your email being categorized as SPAM. They can be included in the main message body OR in a re-usable <strong>message footer</strong>. Refer to the online documentation for details on how to include required links and contact information as well as sample messages.{/ts} {docURL page="Sample CiviMail Messages" resource="wiki"}</p>
+{/htxt}
+
+{htxt id="text"}
+ <p>{ts}You can send your email as a simple text-only message, as an HTML formatted message, or both. Text-only messages are sufficient for most email communication - and some recipients may prefer not to receive HTML formatted messages.{/ts}</p>
+ <p>{ts}HTML messages have more visual impact, allow you to include images, and may be more readable if you are including links to website pages. However, different email programs may interpret HTML formats differently - so use this option cautiously unless you have a template format that has been tested with different web and desktop email programs.{/ts}</p>
+{/htxt}
+
+{htxt id="header"}
+ <p>{ts}You may choose to include a pre-configured Header block above your message.{/ts}</p>
+{/htxt}
+
+{htxt id="footer"}
+ <p>{ts}You may choose to include a pre-configured Footer block below your message. This is a good place to include the required unsubscribe, opt-out and postal address tokens.{/ts}</p>
+{/htxt}
\ No newline at end of file
projects / civicrm-core.git / commitdiff