eventespresso / event-espresso-core

admin_pages/messages/templates/ee_msg_mt_settings_content.template.php

Indentation +3 added lines, -3 removed lines

@@ -7,9 +7,9 @@
 <form method="POST" action="" class="mt-settings-form<?php echo $show_form; ?>">
     <?php echo $template_form_fields; ?>
     <?php
-    foreach ($hidden_fields as $name => $field) {
-        echo $field['field'];
-    } ?>
+	foreach ($hidden_fields as $name => $field) {
+		echo $field['field'];
+	} ?>
     <input type="submit" value="<?php _e('Submit', 'event_espresso'); ?>"
            class="button-secondary mt-settings-submit no-drag"/>
 </form>

admin_pages/messages/templates/ee_msg_messages_templates_editor_help_tab.template.php

Indentation +56 added lines, -56 removed lines

@@ -4,97 +4,97 @@
 <p><?php echo $img1; ?></p>
 <p>
     <?php printf(
-        esc_html__(
-            'The Event Editor title is very helpful in indicating which template you are currently editing.  In the example above, we can see that we are editing the template that for the %1$sEmail%2$s messenger, the %1$sPayment%2$s message type, and the %1$sEvent Admin%2$s context (which for this message type means "recipient").',
-            'event_espresso'
-        ),
-        '<strong>',
-        '</strong>'
-    ); ?></p>
+		esc_html__(
+			'The Event Editor title is very helpful in indicating which template you are currently editing.  In the example above, we can see that we are editing the template that for the %1$sEmail%2$s messenger, the %1$sPayment%2$s message type, and the %1$sEvent Admin%2$s context (which for this message type means "recipient").',
+			'event_espresso'
+		),
+		'<strong>',
+		'</strong>'
+	); ?></p>
 <p><strong><?php esc_html_e('2. "Context Switcher" and Preview Button', 'event_espresso'); ?></strong></p>
 <p><?php echo $img2; ?></p>
 <p>
     <?php esc_html_e(
-        'The context switcher allows you to quickly switch between templates. The current context you are working on is displayed in the dropdown. You can switch to any other template for contexts available to the messenger and message type template group you are working on.',
-        'event_espresso'
-    ); ?></p>
+		'The context switcher allows you to quickly switch between templates. The current context you are working on is displayed in the dropdown. You can switch to any other template for contexts available to the messenger and message type template group you are working on.',
+		'event_espresso'
+	); ?></p>
 <p>
     <?php esc_html_e(
-        'Remember that contexts can represent different things. In this example they represent "recipients" and so they are labelled as such. In this example (for email payment confirmations), you may want Event Administrators to receive different information than Primary Registrants (the other context available to edit).',
-        'event_espresso'
-    ); ?></p>
+		'Remember that contexts can represent different things. In this example they represent "recipients" and so they are labelled as such. In this example (for email payment confirmations), you may want Event Administrators to receive different information than Primary Registrants (the other context available to edit).',
+		'event_espresso'
+	); ?></p>
 <p>
     <?php printf(
-        esc_html__(
-            'The %sPreview%s button is simply a link to a special view of the current template displayed to give you an idea of how the actual message will look when delivered. More information on what the preview displays is available in the content of the help tab on the preview page.',
-            'event_espresso'
-        ),
-        '<strong>',
-        '</strong>'
-    ); ?>
+		esc_html__(
+			'The %sPreview%s button is simply a link to a special view of the current template displayed to give you an idea of how the actual message will look when delivered. More information on what the preview displays is available in the content of the help tab on the preview page.',
+			'event_espresso'
+		),
+		'<strong>',
+		'</strong>'
+	); ?>
 </p>
 <p><strong><?php esc_html_e('3. Template Form Fields', 'event_espresso'); ?></strong></p>
 <p>
     <?php echo $img3; ?><?php esc_html_e(
-        'The middle area of the page is dedicated to all the fields related to the message template. These fields are dynamic in the sense that different messengers may require different fields (and sometimes different message types will add or subtract fields as well.',
-        'event_espresso'
-    ); ?></p>
+		'The middle area of the page is dedicated to all the fields related to the message template. These fields are dynamic in the sense that different messengers may require different fields (and sometimes different message types will add or subtract fields as well.',
+		'event_espresso'
+	); ?></p>
 <p>
     <?php printf(
-        esc_html__(
-            'When editing a "Email Payment Template", you will notice that there is a field labelled "Event List" along with "Main Content". The Event List field is a special field that holds the template for whenever the %1$s[EVENT_LIST]%2$s shortcode is used in the "Main Content" field. This is so you can more finely control how each "event" in the event list displays when shown in the Main content. The "Email Registration Template", has an additional field called "Registration List". It functions much the same except that the contents of the "Registration List" field are used to indicate how each registrant is listed in the Main Content when the %1$s[ATTENDEE_LIST]%2$s shortcode is parsed.',
-            'event_espresso'
-        ),
-        '<strong>',
-        '</strong>'
-    ); ?></p>
+		esc_html__(
+			'When editing a "Email Payment Template", you will notice that there is a field labelled "Event List" along with "Main Content". The Event List field is a special field that holds the template for whenever the %1$s[EVENT_LIST]%2$s shortcode is used in the "Main Content" field. This is so you can more finely control how each "event" in the event list displays when shown in the Main content. The "Email Registration Template", has an additional field called "Registration List". It functions much the same except that the contents of the "Registration List" field are used to indicate how each registrant is listed in the Main Content when the %1$s[ATTENDEE_LIST]%2$s shortcode is parsed.',
+			'event_espresso'
+		),
+		'<strong>',
+		'</strong>'
+	); ?></p>
 <div style="clear:both"></div>
 <p><strong><?php esc_html_e('4. Valid Shortcodes Metabox', 'event_espresso'); ?></strong></p>
 <p>
     <?php echo $img4; ?><?php esc_html_e(
-        'The "Valid Shortcodes" metabox contains a list of all the shortcodes that can be used for the displayed template. This list is dynamic and will vary between templates.',
-        'event_espresso'
-    ); ?>
+		'The "Valid Shortcodes" metabox contains a list of all the shortcodes that can be used for the displayed template. This list is dynamic and will vary between templates.',
+		'event_espresso'
+	); ?>
 </p>
 <p>
     <?php _e(
-        'This box is at a fixed height, but contents are scrollable. You can click the question mark to find out what the given shortcode will parse to when used in your template.',
-        'event_espresso'
-    ); ?></p>
+		'This box is at a fixed height, but contents are scrollable. You can click the question mark to find out what the given shortcode will parse to when used in your template.',
+		'event_espresso'
+	); ?></p>
 <p>
     <?php printf(
-        esc_html__(
-            '%sAn important note:%s The system has been designed so that when you save the template, checks will be performed on each field to make sure that only valid shortcodes (or values) are used within them.  You will get a warning box with clear instructions if you\'ve tried to use a particular shortcode in a field that does not support it.  Also, you\'ll want to try the Preview button if you\'ve made any changes to the template to see if the changes are as you expected!',
-            'event_espresso'
-        ),
-        '<strong>',
-        '</strong>'
-    ); ?>
+		esc_html__(
+			'%sAn important note:%s The system has been designed so that when you save the template, checks will be performed on each field to make sure that only valid shortcodes (or values) are used within them.  You will get a warning box with clear instructions if you\'ve tried to use a particular shortcode in a field that does not support it.  Also, you\'ll want to try the Preview button if you\'ve made any changes to the template to see if the changes are as you expected!',
+			'event_espresso'
+		),
+		'<strong>',
+		'</strong>'
+	); ?>
 </p>
 <div style="clear:both"></div>
 <p><strong><?php esc_html_e('5. Override All Custom', 'event_espresso'); ?></strong></p>
 <p>
     <?php echo $img5; ?>
     <?php printf(
-        esc_html__(
-            'When you are editing a template that is a global template (not a custom event template), you\'ll see an option in the Publish metabox in the right column labelled "Override all custom". When this option is selected, custom event templates for that %1$smessenger%2$s, %1$smessage type%2$s, and %1$scontext%2$s will be ignored and the global template will be used. Why would you want to do this? For this given example, you may want to be able to allow custom event templates to be able to modify the looks and content of what goes out to Primary Registrant but to never affect what the Event Administrator receives (as set by the global template).',
-            'event_espresso'
-        ),
-        '<em>',
-        '</em>'
-    ); ?>
+		esc_html__(
+			'When you are editing a template that is a global template (not a custom event template), you\'ll see an option in the Publish metabox in the right column labelled "Override all custom". When this option is selected, custom event templates for that %1$smessenger%2$s, %1$smessage type%2$s, and %1$scontext%2$s will be ignored and the global template will be used. Why would you want to do this? For this given example, you may want to be able to allow custom event templates to be able to modify the looks and content of what goes out to Primary Registrant but to never affect what the Event Administrator receives (as set by the global template).',
+			'event_espresso'
+		),
+		'<em>',
+		'</em>'
+	); ?>
 </p>
 <p>
     <strong><?php esc_html_e('Recommendations', 'event_espresso'); ?></strong><br/>
     <?php _e(
-        'Want to see a tour of this screen? Click on the Message Template Editor Tour button which appears on the right side of the page. <br />To learn more about the options on this page, take a look at the different tabs that appear on the left side of the page.',
-        'event_espresso'
-    ); ?>
+		'Want to see a tour of this screen? Click on the Message Template Editor Tour button which appears on the right side of the page. <br />To learn more about the options on this page, take a look at the different tabs that appear on the left side of the page.',
+		'event_espresso'
+	); ?>
 </p>
 <p>
     <strong><?php esc_html_e('Screen Options', 'event_espresso'); ?></strong><br/>
     <?php _e(
-        'You can customize the information that is shown on this page by toggling the Screen Options tab. Then you can add or remove checkmarks to hide or show certain content.',
-        'event_espresso'
-    ); ?>
+		'You can customize the information that is shown on this page by toggling the Screen Options tab. Then you can add or remove checkmarks to hide or show certain content.',
+		'event_espresso'
+	); ?>
 </p>
\ No newline at end of file

admin_pages/messages/templates/ee_msg_message_templates_help_tab.template.php

Indentation +13 added lines, -13 removed lines

@@ -1,20 +1,20 @@
 <h2><?php esc_html_e('What are Message Templates', 'event_espresso'); ?></h2>
 <p>
     <?php printf(
-        esc_html__(
-            'Message Templates are the %1$sformat%2$s of the messages going out. Think of them like a “Form letter”. Templates are used to tell the system what you want your messages to look like and the content they will have when they are delivered.',
-            'event_espresso'
-        ),
-        '<em>',
-        '</em>'
-    ); ?></p>
+		esc_html__(
+			'Message Templates are the %1$sformat%2$s of the messages going out. Think of them like a “Form letter”. Templates are used to tell the system what you want your messages to look like and the content they will have when they are delivered.',
+			'event_espresso'
+		),
+		'<em>',
+		'</em>'
+	); ?></p>
 <p>
     <?php esc_html_e(
-        'There is a template created for each messenger/message type AND context combination. So example, Emails that are sent for the Payment confirmation have a template for Event Administrator and a different one for Primary Registrant.  Whereas, emails that are sent for the Registration confirmation have 3 templates, one for Event Administrator, Primary Registrant, and Registrant.',
-        'event_espresso'
-    ); ?></p>
+		'There is a template created for each messenger/message type AND context combination. So example, Emails that are sent for the Payment confirmation have a template for Event Administrator and a different one for Primary Registrant.  Whereas, emails that are sent for the Registration confirmation have 3 templates, one for Event Administrator, Primary Registrant, and Registrant.',
+		'event_espresso'
+	); ?></p>
 <p>
     <?php esc_html_e(
-        'With the Event Espresso Messages system, every Messenger, Message Type and Context will have a global template created with some default content on creation.  You have the ability to edit this global template that will be used for all events you create.  However, you also have the ability to create custom templates for each event on the edit event page for the event (in a metabox labelled "Notifications").',
-        'event_espresso'
-    ); ?></p>
\ No newline at end of file
+		'With the Event Espresso Messages system, every Messenger, Message Type and Context will have a global template created with some default content on creation.  You have the ability to edit this global template that will be used for all events you create.  However, you also have the ability to create custom templates for each event on the edit event page for the event (in a metabox labelled "Notifications").',
+		'event_espresso'
+	); ?></p>
\ No newline at end of file

admin_pages/messages/templates/ee_msg_admin_overview.template.php

Indentation +6 added lines, -6 removed lines

@@ -15,9 +15,9 @@ 
             <?php foreach ($active_messengers as $messenger => $args) : ?>
                 <option value="<?php echo $messenger; ?>">
                     <?php
-                    echo ucwords(
-                        str_replace('_', ' ', $messenger)
-                    ); ?></option>
+					echo ucwords(
+						str_replace('_', ' ', $messenger)
+					); ?></option>
             <?php endforeach; ?>
         </select>
         <input id="submit-ee-messenger-filters-sbmt" class="button-secondary" type="submit" value="Filter Messenger">
@@ -26,9 +26,9 @@ 
             <?php foreach ($active_message_types as $message_type => $args) : ?>
                 <option value="<?php echo $message_type; ?>">
                     <?php
-                    echo ucwords(
-                        str_replace('_', ' ', $message_type)
-                    ); ?></option>
+					echo ucwords(
+						str_replace('_', ' ', $message_type)
+					); ?></option>
             <?php endforeach; ?>
         </select>
         <input id="submit-ee-message-type-filters-sbmt" class="button-secondary" type="submit"

admin_pages/messages/templates/ee_msg_messages_settings_help_tab.template.php

Indentation +32 added lines, -32 removed lines

@@ -3,56 +3,56 @@
 
 <h3><?php _e('1. Defaults', 'event_espresso'); ?></h3>
 <p><?php _e(
-    'When Event Espresso is first activated, the plugin takes care of setting up the core messenger (Email) and message types (Registration, and Payment).  This is so users don\'t have to worry about any setup of templates etc. and it just works right out of the box.  So when you first visit the page you\'ll see the Email messenger displayed with those two message types in the "Active" area for that messenger',
-    'event_espresso'
+	'When Event Espresso is first activated, the plugin takes care of setting up the core messenger (Email) and message types (Registration, and Payment).  This is so users don\'t have to worry about any setup of templates etc. and it just works right out of the box.  So when you first visit the page you\'ll see the Email messenger displayed with those two message types in the "Active" area for that messenger',
+	'event_espresso'
 ); ?></p>
 <h3><?php _e('2. Activating or Deactivating Messengers', 'event_espresso'); ?></h3>
 <p><?php _e(
-    'You can select messengers via the tabs across the top of the settings page.  The available messengers you see depends on what version of Event Espresso you have and what addons are installed.  Every install will see at the very least an "Email" messenger tab.  When you click one of those tabs it will display that messenger.',
-    'event_espresso'
+	'You can select messengers via the tabs across the top of the settings page.  The available messengers you see depends on what version of Event Espresso you have and what addons are installed.  Every install will see at the very least an "Email" messenger tab.  When you click one of those tabs it will display that messenger.',
+	'event_espresso'
 ); ?></p>
 <p><?php _e(
-    'There are two ways to determine whether a messenger is active or not.  The first way is via the messenger tab itself.',
-    'event_espresso'
+	'There are two ways to determine whether a messenger is active or not.  The first way is via the messenger tab itself.',
+	'event_espresso'
 ); ?></p>
 <p><?php echo $img1;
-    _e('The green colored gear indicates that this messenger is currently active.', 'event_espresso');
-    echo $img2;
-    _e(
-        'Here the white colored gear indicates the messenger is inactive. This is very helpful for seeing at a glance all the messengers that are active when you first view the page.',
-        'event_espresso'
-    ); ?></p>
+	_e('The green colored gear indicates that this messenger is currently active.', 'event_espresso');
+	echo $img2;
+	_e(
+		'Here the white colored gear indicates the messenger is inactive. This is very helpful for seeing at a glance all the messengers that are active when you first view the page.',
+		'event_espresso'
+	); ?></p>
 <p><?php _e(
-    'The second way to determine whether a messenger is active or not is via the "on/off" button in the top right corner of the active messenger displayed content:',
-    'event_espresso'
+	'The second way to determine whether a messenger is active or not is via the "on/off" button in the top right corner of the active messenger displayed content:',
+	'event_espresso'
 ); ?></p>
 <p><?php echo $img3;
-    printf(
-        __('On means of course that the messenger is active and %s means the messenger is inactive.', 'event_espresso'),
-        $img4
-    ); ?></p>
+	printf(
+		__('On means of course that the messenger is active and %s means the messenger is inactive.', 'event_espresso'),
+		$img4
+	); ?></p>
 <p><?php _e(
-    'Incidentally, the on/off toggle is also what you use to activate or deactivate a messenger.',
-    'event_espresso'
+	'Incidentally, the on/off toggle is also what you use to activate or deactivate a messenger.',
+	'event_espresso'
 ); ?></p>
 <p><?php _e(
-    'What happens when you click the toggle to activate is the messenger is activated and the system determines what default message types are activated with the messenger.  Then, if there are any default settings for either the messenger or message types those settings are saved.  Next, the system will generate any default templates (if none have been generated before, if there are previously generated templates then they are reactivated).  Finally, you will see the display change to reflect that the messenger is active. If the messenger has settings you can modify them then.  Any message types that have settings will also automatically expand so you can see the default settings and make any changes as necessary to fit your needs. Usually the defaults are sufficient however.',
-    'event_espresso'
+	'What happens when you click the toggle to activate is the messenger is activated and the system determines what default message types are activated with the messenger.  Then, if there are any default settings for either the messenger or message types those settings are saved.  Next, the system will generate any default templates (if none have been generated before, if there are previously generated templates then they are reactivated).  Finally, you will see the display change to reflect that the messenger is active. If the messenger has settings you can modify them then.  Any message types that have settings will also automatically expand so you can see the default settings and make any changes as necessary to fit your needs. Usually the defaults are sufficient however.',
+	'event_espresso'
 ); ?></p>
 <p><?php _e(
-    'When you deactivate a messenger, the system will first check if there are any custom event templates for that messenger.  If there are you will be unable to deactivate the messenger.  This is a fail safe to make sure you know that no messages will go out for those specific events so you don\'t accidentally deactivate.  If this check passes, then the system will deactivate any global templates for that messenger (note the templates are not erased, they just become inactive, so if you decide to reactivate the messenger later all your customizations are preserved). Then the display will change to reflect the deactivation.',
-    'event_espresso'
+	'When you deactivate a messenger, the system will first check if there are any custom event templates for that messenger.  If there are you will be unable to deactivate the messenger.  This is a fail safe to make sure you know that no messages will go out for those specific events so you don\'t accidentally deactivate.  If this check passes, then the system will deactivate any global templates for that messenger (note the templates are not erased, they just become inactive, so if you decide to reactivate the messenger later all your customizations are preserved). Then the display will change to reflect the deactivation.',
+	'event_espresso'
 ); ?></p>
 <p><?php printf(
-    __(
-        '%sVery important!%s Although customizations made to global templates are preserved when a messenger is deactivated, any settings for that messenger (or the message types that were attached to it) are lost on deactivation.  Keep that in mind. Also, once you deactivate a messenger, no more messages will be delivered using that messenger for any of your events.',
-        'event_espresso'
-    ),
-    '<strong>',
-    '</strong>'
+	__(
+		'%sVery important!%s Although customizations made to global templates are preserved when a messenger is deactivated, any settings for that messenger (or the message types that were attached to it) are lost on deactivation.  Keep that in mind. Also, once you deactivate a messenger, no more messages will be delivered using that messenger for any of your events.',
+		'event_espresso'
+	),
+	'<strong>',
+	'</strong>'
 ); ?></p>
 <h3><?php _e('3. Activating or Deactivating Message Types', 'event_espresso'); ?></h3>
 <p><?php _e(
-    'There may be times where you just want to deactivate (or activate new) message types for a particular messenger.  The messages system makes it super easy to do so.  To deactivate, what you do is drag the message type box from the "active area" below the messenger description (of an active messenger) into the "inactive" area in the right sidebar.  To activate you do the reverse.  Just remember that when you deactivate a message type, if that message type has any settings, the settings will be lost.  However, any message templates that match the messenger and message type you deactivated will be preserved, they are just marked "inactive" in the database',
-    'event_espresso'
+	'There may be times where you just want to deactivate (or activate new) message types for a particular messenger.  The messages system makes it super easy to do so.  To deactivate, what you do is drag the message type box from the "active area" below the messenger description (of an active messenger) into the "inactive" area in the right sidebar.  To activate you do the reverse.  Just remember that when you deactivate a message type, if that message type has any settings, the settings will be lost.  However, any message templates that match the messenger and message type you deactivated will be preserved, they are just marked "inactive" in the database',
+	'event_espresso'
 ); ?></p>
\ No newline at end of file

admin_pages/messages/templates/ee_msg_messages_help_tab.template.php

Indentation +10 added lines, -10 removed lines

@@ -1,15 +1,15 @@
 <h2><?php esc_html_e('What is the Event Espresso Messages System?', 'event_espresso'); ?></h2>
 <p>
     <?php printf(
-        esc_html__(
-            'The Event Espresso Messages system is a powerful framework that Event Espresso uses to prepare %1$smessages%2$s for different types of use (message types) and delivered by different %1$smessengers%2$s.',
-            'event_espresso'
-        ),
-        '<strong>',
-        '</strong>'
-    ); ?></p>
+		esc_html__(
+			'The Event Espresso Messages system is a powerful framework that Event Espresso uses to prepare %1$smessages%2$s for different types of use (message types) and delivered by different %1$smessengers%2$s.',
+			'event_espresso'
+		),
+		'<strong>',
+		'</strong>'
+	); ?></p>
 <p>
     <?php esc_html_e(
-        'We\'ve intentionally created this framework so that we have as much flexibility as possible for future ideas that we think of (or customers think of) for the kinds of messages that get sent out related to your events.',
-        'event_espresso'
-    ); ?></p>
\ No newline at end of file
+		'We\'ve intentionally created this framework so that we have as much flexibility as possible for future ideas that we think of (or customers think of) for the kinds of messages that get sent out related to your events.',
+		'event_espresso'
+	); ?></p>
\ No newline at end of file

admin_pages/messages/templates/ee_msg_details_main_edit_meta_box.template.php

Indentation +18 added lines, -18 removed lines

@@ -4,21 +4,21 @@ 
     <input type="hidden" id="ee-msg-current-context" name="MTP_context" value="<?php echo $context; ?>"/>
     <!-- if this is not a global template then let's show the name and description fields -->
     <?php
-    if (! $MTP->is_global()) : ?>
+	if (! $MTP->is_global()) : ?>
         <div class="non-global-mtp-fields">
             <p>
                 <?php _e(
-                    'This is a custom template.  Custom Templates have an editable name and description to help you differentiate between templates.',
-                    'event_espresso'
-                ); ?>
+					'This is a custom template.  Custom Templates have an editable name and description to help you differentiate between templates.',
+					'event_espresso'
+				); ?>
             </p>
             <div id="titlediv">
                 <div id="titlewrap">
                     <label for="title" class="label-MTP_name" style="visibility:hidden">
                         <?php _e(
-                            'Message Template Name:',
-                            'event_espresso'
-                        ); ?></label>
+							'Message Template Name:',
+							'event_espresso'
+						); ?></label>
                     <input id="title" type="text" class="regular-text" name="ee_msg_non_global_fields[MTP_name]"
                            value="<?php echo $MTP->name(); ?>">
                 </div>
@@ -27,29 +27,29 @@ 
                 <label for="ee-msg-non-global-fields-MTP_description" class="label-MTP_description"
                        style="visibility:hidden;">
                     <?php _e(
-                        'Message Template Description:',
-                        'event_espresso'
-                    ); ?></label>
+						'Message Template Description:',
+						'event_espresso'
+					); ?></label>
                 <textarea id="ee-msg-non-global-fields-MTP_description" class="large-text"
                           name="ee_msg_non_global_fields[MTP_description]"><?php echo $MTP->description(); ?></textarea>
             </p>
         </div>
     <?php
-    else :
-    ?>
+	else :
+	?>
         <input type="hidden" name="ee_msg_non_global_fields[MTP_name]" value="<?php echo $MTP->name(); ?>">
         <input type="hidden" name="ee_msg_non_global_fields[MTP_description]"
                value="<?php echo $MTP->description(); ?>">
     <?php endif; ?>
     <!-- we need to loop through the template_fields so we know our structure -->
     <?php
-    if (isset($template_fields) && ! empty($template_fields) && ! is_wp_error($template_fields)) {
-        echo $template_fields;
-    } else {
-        ?>
+	if (isset($template_fields) && ! empty($template_fields) && ! is_wp_error($template_fields)) {
+		echo $template_fields;
+	} else {
+		?>
         <p><?php _e('Something has gone wrong, there are no template fields to output.', 'event_espresso'); ?></p>
         <?php
-    }
+	}
 
-    ?>
+	?>
 </div> <!-- end #admin-primary-mbox-dv -->

Spacing +2 added lines, -2 removed lines

@@ -1,10 +1,10 @@
 <div id="admin-primary-mbox-dv" class="admin-primary-mbox-dv">
 
-    <h3 class="admin-primary-mbox-h4"><?php echo isset($event_name) ? $event_name . ' Custom Template' : ''; ?></h3>
+    <h3 class="admin-primary-mbox-h4"><?php echo isset($event_name) ? $event_name.' Custom Template' : ''; ?></h3>
     <input type="hidden" id="ee-msg-current-context" name="MTP_context" value="<?php echo $context; ?>"/>
     <!-- if this is not a global template then let's show the name and description fields -->
     <?php
-    if (! $MTP->is_global()) : ?>
+    if ( ! $MTP->is_global()) : ?>
         <div class="non-global-mtp-fields">
             <p>
                 <?php _e(

Braces +5 added lines, -2 removed lines

@@ -35,9 +35,12 @@
             </p>
         </div>
     <?php
-    else :
+    else {
+    	:
     ?>
-        <input type="hidden" name="ee_msg_non_global_fields[MTP_name]" value="<?php echo $MTP->name(); ?>">
+        <input type="hidden" name="ee_msg_non_global_fields[MTP_name]" value="<?php echo $MTP->name();
+    }
+    ?>">
         <input type="hidden" name="ee_msg_non_global_fields[MTP_description]"
                value="<?php echo $MTP->description(); ?>">
     <?php endif; ?>

admin_pages/messages/templates/ee_msg_details_messenger_meta_box.template.php

Indentation +16 added lines, -16 removed lines

@@ -1,28 +1,28 @@
 <div class="<?php echo $messenger; ?>-content">
     <?php
-    if (empty($inactive_message_types) && empty($active_message_types)) :
-        echo '<p>'
-             . __(
-                 'This messenger is not currently used with any message types for templates but merely adds to the shortcodes available for templates on other messenger and message types.',
-                 'event_espresso'
-             ) . '</p>';
-    else : ?>
+	if (empty($inactive_message_types) && empty($active_message_types)) :
+		echo '<p>'
+			 . __(
+				 'This messenger is not currently used with any message types for templates but merely adds to the shortcodes available for templates on other messenger and message types.',
+				 'event_espresso'
+			 ) . '</p>';
+	else : ?>
         <p class="inactive-on-message <?php echo $hide_on_message; ?>">
             <?php _e(
-                'Below are message types that are currently inactive with this messenger.  Drag them over to the messenger box to activate them.',
-                'event_espresso'
-            ); ?>
+				'Below are message types that are currently inactive with this messenger.  Drag them over to the messenger box to activate them.',
+				'event_espresso'
+			); ?>
         <p>
         <p class="inactive-off-message <?php echo $hide_off_message; ?>">
             <?php _e(
-                'This messenger is currently inactive.  Once the messenger is activated any inactive message types associated with the messenger will be shown here.',
-                'event_espresso'
-            ); ?>
+				'This messenger is currently inactive.  Once the messenger is activated any inactive message types associated with the messenger will be shown here.',
+				'event_espresso'
+			); ?>
         </p>
         <div<?php
-        if ($active) :
-            ?> id="inactive-message-types"<?php
-        endif; ?>
+		if ($active) :
+			?> id="inactive-message-types"<?php
+		endif; ?>
             class="inactive-message-types mt-tab-container ui-widget-content-ui-state-default <?php echo $hide_on_message; ?>">
             <ul class="messenger-activation">
                 <?php echo $inactive_message_types; ?>

Spacing +1 added lines, -1 removed lines

@@ -5,7 +5,7 @@
              . __(
                  'This messenger is not currently used with any message types for templates but merely adds to the shortcodes available for templates on other messenger and message types.',
                  'event_espresso'
-             ) . '</p>';
+             ).'</p>';
     else : ?>
         <p class="inactive-on-message <?php echo $hide_on_message; ?>">
             <?php _e(

Braces +5 added lines, -2 removed lines

@@ -6,8 +6,11 @@
                  'This messenger is not currently used with any message types for templates but merely adds to the shortcodes available for templates on other messenger and message types.',
                  'event_espresso'
              ) . '</p>';
-    else : ?>
-        <p class="inactive-on-message <?php echo $hide_on_message; ?>">
+    else {
+    	: ?>
+        <p class="inactive-on-message <?php echo $hide_on_message;
+    }
+    ?>">
             <?php _e(
                 'Below are message types that are currently inactive with this messenger.  Drag them over to the messenger box to activate them.',
                 'event_espresso'

admin_pages/messages/templates/ee_msg_message_type_help_tab.template.php

Indentation +20 added lines, -20 removed lines

@@ -1,31 +1,31 @@
 <h2><?php esc_html_e('What are Message Types?', 'event_espresso'); ?></h2>
 <p>
     <?php printf(
-        esc_html__(
-            'Message Types are the %1$skinds%2$s of messages that get delivered.  Think of them as the "type" of package that is being delivered by the messenger.  For example, Event Espresso comes with two Message Types attached to the Email messenger:  Registration Confirmation (which is triggered by frontend event registrations), and Payment Confirmation (which is triggered by frontend payments).',
-            'event_espresso'
-        ),
-        '<em>',
-        '</em>'
-    ); ?></p>
+		esc_html__(
+			'Message Types are the %1$skinds%2$s of messages that get delivered.  Think of them as the "type" of package that is being delivered by the messenger.  For example, Event Espresso comes with two Message Types attached to the Email messenger:  Registration Confirmation (which is triggered by frontend event registrations), and Payment Confirmation (which is triggered by frontend payments).',
+			'event_espresso'
+		),
+		'<em>',
+		'</em>'
+	); ?></p>
 <p>
     <?php esc_html_e(
-        'Future iterations of Event Espresso 4.0 (premium versions), will include more and more different message types that can be attached to the various messengers that are available',
-        'event_espresso'
-    ); ?></p>
+		'Future iterations of Event Espresso 4.0 (premium versions), will include more and more different message types that can be attached to the various messengers that are available',
+		'event_espresso'
+	); ?></p>
 
 <h3><?php esc_html_e('Contexts', 'event_espresso'); ?></h3>
 <p>
     <?php printf(
-        esc_html__(
-            'Each message type (or %1$skind%1$s of message remember!) has different contexts for messages created for that message type. Contexts are dynamic but generally speaking they tend to represent recipients. So for example, Registration Confirmation message type has three types of recipients for every time a registration confirmation is triggered: Event Administrator, Primary Registrant, and Registrant (which may be multiple messages if there are more than one attendee per event). Whereas the Payment Message Type only has two recipients (Event Administrator, Primary Registrant [the one making the payment]).',
-            'event_espresso'
-        ),
-        '<em>',
-        '</em>'
-    ); ?></p>
+		esc_html__(
+			'Each message type (or %1$skind%1$s of message remember!) has different contexts for messages created for that message type. Contexts are dynamic but generally speaking they tend to represent recipients. So for example, Registration Confirmation message type has three types of recipients for every time a registration confirmation is triggered: Event Administrator, Primary Registrant, and Registrant (which may be multiple messages if there are more than one attendee per event). Whereas the Payment Message Type only has two recipients (Event Administrator, Primary Registrant [the one making the payment]).',
+			'event_espresso'
+		),
+		'<em>',
+		'</em>'
+	); ?></p>
 <p>
     <?php esc_html_e(
-        'You will most likely never see the word "context" in any of the Messages system labelling because they are dynamic per message type.  Usually, contexts will be labelled "Recipients" but there may be cases down the road where a message type might use contexts to represent something totally different',
-        'event_espresso'
-    ); ?></p>
\ No newline at end of file
+		'You will most likely never see the word "context" in any of the Messages system labelling because they are dynamic per message type.  Usually, contexts will be labelled "Recipients" but there may be cases down the road where a message type might use contexts to represent something totally different',
+		'event_espresso'
+	); ?></p>
\ No newline at end of file