eventespresso / event-espresso-core

admin_pages/messages/templates/ee_msg_messenger_help_tab.template.php

Indentation +7 added lines, -7 removed lines

@@ -1,11 +1,11 @@
 <h2><?php esc_html_e('What are Messengers?', 'event_espresso'); ?></h2>
 <p>
     <?php printf(
-        esc_html__(
-            'Messengers are the vehicles that deliver messages to people.  By default, every Event Espresso install has the %sEmail%s messenger already active. The Email messenger is a vehicle for delivering messages.  Other possible vehicles might be any social media applications, 3rd Party API\'s etc.',
-            'event_espresso'
-        ),
-        '<strong>',
-        '</strong>'
-    ); ?>
+		esc_html__(
+			'Messengers are the vehicles that deliver messages to people.  By default, every Event Espresso install has the %sEmail%s messenger already active. The Email messenger is a vehicle for delivering messages.  Other possible vehicles might be any social media applications, 3rd Party API\'s etc.',
+			'event_espresso'
+		),
+		'<strong>',
+		'</strong>'
+	); ?>
 </p>
\ No newline at end of file

admin_pages/messages/templates/ee_msg_messages_settings_help_tab.template.php

Indentation +44 added lines, -44 removed lines

@@ -15,80 +15,80 @@
 <h3><?php esc_html_e('1. Defaults', 'event_espresso'); ?></h3>
 <p>
     <?php esc_html_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 esc_html_e('2. Activating or Deactivating Messengers', 'event_espresso'); ?></h3>
 <p>
     <?php esc_html_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 esc_html_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 esc_html($img1);
-    esc_html_e('The green colored gear indicates that this messenger is currently active.', 'event_espresso');
-    echo esc_html($img2);
-    esc_html_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'
-    ); ?>
+	esc_html_e('The green colored gear indicates that this messenger is currently active.', 'event_espresso');
+	echo esc_html($img2);
+	esc_html_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 esc_html_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 esc_html($img3);
-    printf(
-        esc_html__(
-            'On means of course that the messenger is active and %s means the messenger is inactive.',
-            'event_espresso'
-        ),
-        $img4
-    ); ?>
+	printf(
+		esc_html__(
+			'On means of course that the messenger is active and %s means the messenger is inactive.',
+			'event_espresso'
+		),
+		$img4
+	); ?>
 </p>
 <p>
     <?php esc_html_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 esc_html_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 esc_html_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(
-        esc_html__(
-            '%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>'
-    ); ?>
+		esc_html__(
+			'%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 esc_html_e('3. Activating or Deactivating Message Types', 'event_espresso'); ?></h3>
 <p>
     <?php esc_html_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_details_messenger_meta_box.template.php

Indentation +13 added lines, -13 removed lines

@@ -11,24 +11,24 @@
 <div class="<?php echo esc_attr($messenger); ?>-content">
 
     <?php if (empty($inactive_message_types) && empty($active_message_types)) :
-        echo '<p>'
-             . esc_html__(
-                 '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 : ?>
+		echo '<p>'
+			 . esc_html__(
+				 '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 esc_attr($hide_on_message); ?>">
             <?php esc_html_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 esc_attr($hide_off_message); ?>">
             <?php esc_html_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) : ?>

Braces +5 added lines, -2 removed lines

@@ -17,8 +17,11 @@
                  'event_espresso'
              )
              . '</p>';
-    else : ?>
-        <p class="inactive-on-message <?php echo esc_attr($hide_on_message); ?>">
+    else {
+    	: ?>
+        <p class="inactive-on-message <?php echo esc_attr($hide_on_message);
+    }
+    ?>">
             <?php esc_html_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,35 +1,35 @@
 <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>'
-    ); ?>
+		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'
-    ); ?>
+		'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>'
-    ); ?>
+		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'
-    ); ?>
+		'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>

admin_pages/messages/templates/ee_msg_messages_shortcodes_help_tab.template.php

Indentation +3 added lines, -3 removed lines

@@ -9,9 +9,9 @@
     </p>
     <p>
         <?php esc_html_e(
-            'The following list of shortcodes can be used for this Messenger and Message Type. You can use the descriptions to learn what the shortcode will be parsed to when the final message is generated.',
-            'event_espresso'
-        ); ?>
+			'The following list of shortcodes can be used for this Messenger and Message Type. You can use the descriptions to learn what the shortcode will be parsed to when the final message is generated.',
+			'event_espresso'
+		); ?>
     </p>
 
 <?php

admin_pages/messages/templates/ee_msg_details_messenger_mt_meta_box.template.php

Braces +5 added lines, -2 removed lines

@@ -17,8 +17,11 @@
                  'event_espresso'
              )
              . '</p>';
-    else : ?>
-        <p class="active-on-message <?php echo esc_attr($hide_on_message); ?>">
+    else {
+    	: ?>
+        <p class="active-on-message <?php echo esc_attr($hide_on_message);
+    }
+    ?>">
             <?php printf(
                 esc_html__(
                     'Below are message types that are currently %sactive%s with this messenger. Drag them over to the "Inactive Message Types" box to deactivate them.',

Indentation +15 added lines, -15 removed lines

@@ -15,23 +15,23 @@
 <div class="<?php echo esc_attr($messenger); ?>-content">
     <?php echo wp_kses($content, AllowedTags::getWithFormTags()); ?>
     <?php if (empty($inactive_message_types) && empty($active_message_types)) :
-        echo '<p>'
-             . esc_html__(
-                 '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 : ?>
+		echo '<p>'
+			 . esc_html__(
+				 '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="active-on-message <?php echo esc_attr($hide_on_message); ?>">
             <?php printf(
-                esc_html__(
-                    'Below are message types that are currently %sactive%s with this messenger. Drag them over to the "Inactive Message Types" box to deactivate them.',
-                    'event_espresso'
-                ),
-                '<strong>',
-                '</strong>'
-            );
-            ?>
+				esc_html__(
+					'Below are message types that are currently %sactive%s with this messenger. Drag them over to the "Inactive Message Types" box to deactivate them.',
+					'event_espresso'
+				),
+				'<strong>',
+				'</strong>'
+			);
+			?>
         <p>
         <div<?php if ($active) : ?>
             id="active-message-types"

admin_pages/messages/templates/ee_msg_message_templates_help_tab.template.php

Indentation +13 added lines, -13 removed lines

@@ -1,23 +1,23 @@
 <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>'
-    ); ?>
+		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'
-    ); ?>
+		'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'
-    ); ?>
+		'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_details_main_edit_meta_box.template.php

Spacing +1 added lines, -1 removed lines

@@ -15,7 +15,7 @@
     <input type="hidden" id="ee-msg-current-context" name="MTP_context" value="<?php echo esc_attr($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 esc_html_e(

Braces +5 added lines, -2 removed lines

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

Indentation +15 added lines, -15 removed lines

@@ -19,13 +19,13 @@ 
     <input type="hidden" id="ee-msg-current-context" name="MTP_context" value="<?php echo esc_attr($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 esc_html_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">
@@ -56,8 +56,8 @@ 
             </p>
         </div>
         <?php
-    else :
-        ?>
+	else :
+		?>
         <input type="hidden" name="ee_msg_non_global_fields[MTP_name]" value="<?php echo esc_attr($MTP->name()); ?>">
         <input type="hidden"
                name="ee_msg_non_global_fields[MTP_description]"
@@ -66,18 +66,18 @@ 
     <?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 wp_kses($template_fields, AllowedTags::getWithFullTags());
-    } else {
-        ?>
+	if (isset($template_fields) && ! empty($template_fields) && ! is_wp_error($template_fields)) {
+		echo wp_kses($template_fields, AllowedTags::getWithFullTags());
+	} else {
+		?>
         <p>
             <?php esc_html_e(
-                'Something has gone wrong, there are no template fields to output.',
-                'event_espresso'
-            ); ?>
+				'Something has gone wrong, there are no template fields to output.',
+				'event_espresso'
+			); ?>
         </p>
         <?php
-    }
+	}
 
-    ?>
+	?>
 </div> <!-- end #admin-primary-mbox-dv -->

admin_pages/messages/templates/ee_msg_preview_help_tab.template.php

Indentation +18 added lines, -18 removed lines

@@ -1,44 +1,44 @@
 <h2><?php esc_html_e('What the preview page shows', 'event_espresso'); ?></h2>
 <p>
     <?php esc_html_e(
-        'This page is accessed by clicking the preview button while editing a message template.  This feature has been created as a way of previewing what the final generated messages will look like when received.  Here\'s how the preview is prepared:',
-        'event_espresso'
-    ); ?>
+		'This page is accessed by clicking the preview button while editing a message template.  This feature has been created as a way of previewing what the final generated messages will look like when received.  Here\'s how the preview is prepared:',
+		'event_espresso'
+	); ?>
 </p>
 
 <h3>
     <?php esc_html_e(
-        '1. The system retrieves the appropriate template based on the given messenger, message type, and context',
-        'event_espresso'
-    ); ?>
+		'1. The system retrieves the appropriate template based on the given messenger, message type, and context',
+		'event_espresso'
+	); ?>
 </h3>
 <p>
     <?php esc_html_e(
-        'When you click the preview button, the messages system remembers what template is being "previewed" based on the messenger, message_type, context and event (if this is a custom event template).',
-        'event_espresso'
-    ); ?>
+		'When you click the preview button, the messages system remembers what template is being "previewed" based on the messenger, message_type, context and event (if this is a custom event template).',
+		'event_espresso'
+	); ?>
 </p>
 
 <h3><?php esc_html_e('2. Setup data.', 'event_espresso'); ?></h3>
 <p>
     <?php esc_html_e(
-        'Before any shortcodes in the template can be parsed, the previewer needs to know what data to use for the shortcodes.  Some of the data is dummy data that the previewer generates, but wherever possible the previewer will use ACTUAL data from your database.  For example, all the organization shortcodes will use actual data you\'ve setup for your organization.  For global template previews, the previewer will obtain the first active event from your database and use data from it.  If you are previewing a custom event template then THAT event will be used for the preview.  The only data that is dummy data is typically data that would be entered by a person registering for an event',
-        'event_espresso'
-    ); ?>
+		'Before any shortcodes in the template can be parsed, the previewer needs to know what data to use for the shortcodes.  Some of the data is dummy data that the previewer generates, but wherever possible the previewer will use ACTUAL data from your database.  For example, all the organization shortcodes will use actual data you\'ve setup for your organization.  For global template previews, the previewer will obtain the first active event from your database and use data from it.  If you are previewing a custom event template then THAT event will be used for the preview.  The only data that is dummy data is typically data that would be entered by a person registering for an event',
+		'event_espresso'
+	); ?>
 </p>
 
 <h3><?php esc_html_e('3. Parse shortcodes', 'event_espresso'); ?></h3>
 <p>
     <?php esc_html_e(
-        'The previewer then goes through all the shortcodes in the template being previewed and replaces them using the prepared data. This is a good way of making sure that the shortcodes are working as you expect, and also clearly seeing what is being displayed for that shortcode when someone receives that message.',
-        'event_espresso'
-    ); ?>
+		'The previewer then goes through all the shortcodes in the template being previewed and replaces them using the prepared data. This is a good way of making sure that the shortcodes are working as you expect, and also clearly seeing what is being displayed for that shortcode when someone receives that message.',
+		'event_espresso'
+	); ?>
 </p>
 
 <h3><?php esc_html_e('4. Display the preview!', 'event_espresso'); ?></h3>
 <p>
     <?php esc_html_e(
-        'An important thing to remember about the previewer is that for the most part, the previewer uses the same underlying system that will be used for actual outgoing messages, so you can be certain that what you see in the preview is what users will see when they receive the message.  It is yet another tool provided to make it easier for you to customize the look of your outgoing messages.',
-        'event_espresso'
-    ); ?>
+		'An important thing to remember about the previewer is that for the most part, the previewer uses the same underlying system that will be used for actual outgoing messages, so you can be certain that what you see in the preview is what users will see when they receive the message.  It is yet another tool provided to make it easier for you to customize the look of your outgoing messages.',
+		'event_espresso'
+	); ?>
 </p>
\ No newline at end of file