@@ -6,18 +6,18 @@ discard block |
||
6 | 6 | <form id="ee-msg-add-message-template-frm" action="<?php echo $edit_message_template_form_url; ?>" method="post"> |
7 | 7 | <input type="hidden" id="evt_id" name="EVT_ID" value="<?php echo ($EVT_ID) ? $EVT_ID : ''; ?>"/> |
8 | 8 | <?php |
9 | - if (isset($hidden_fields)) { |
|
10 | - echo $hidden_fields; |
|
11 | - } ?> |
|
9 | + if (isset($hidden_fields)) { |
|
10 | + echo $hidden_fields; |
|
11 | + } ?> |
|
12 | 12 | <!--active_messengers --> |
13 | 13 | <label for="MTP_messenger"><?php _e('Select Messenger', 'event_espresso'); ?></label> |
14 | 14 | <select name="MTP_messenger" id="MTP-messenger"> |
15 | 15 | <?php |
16 | - foreach ($active_messengers as $messenger => $values) : ?> |
|
16 | + foreach ($active_messengers as $messenger => $values) : ?> |
|
17 | 17 | <option value="<?php echo $messenger; ?>"> |
18 | 18 | <?php echo ucwords( |
19 | - str_replace('_', ' ', $messenger) |
|
20 | - ); ?></option> |
|
19 | + str_replace('_', ' ', $messenger) |
|
20 | + ); ?></option> |
|
21 | 21 | <?php endforeach; ?> |
22 | 22 | </select> |
23 | 23 | |
@@ -26,8 +26,8 @@ discard block |
||
26 | 26 | <?php foreach ($active_message_types as $message_type => $values) : ?> |
27 | 27 | <option value="<?php echo $message_type; ?>"> |
28 | 28 | <?php echo ucwords( |
29 | - str_replace('_', ' ', $message_type) |
|
30 | - ); ?></option> |
|
29 | + str_replace('_', ' ', $message_type) |
|
30 | + ); ?></option> |
|
31 | 31 | <?php endforeach; ?> |
32 | 32 | </select> |
33 | 33 |
@@ -1,6 +1,6 @@ discard block |
||
1 | 1 | <div id="admin-primary-mbox-dv" class="admin-primary-mbox-dv"> |
2 | 2 | |
3 | - <h4 class="admin-primary-mbox-h4"><?php echo ($event_name) ? $event_name . ' Custom Template' : ''; ?></h4> |
|
3 | + <h4 class="admin-primary-mbox-h4"><?php echo ($event_name) ? $event_name.' Custom Template' : ''; ?></h4> |
|
4 | 4 | <p><?php echo $action_message; ?></p> |
5 | 5 | |
6 | 6 | <form id="ee-msg-add-message-template-frm" action="<?php echo $edit_message_template_form_url; ?>" method="post"> |
@@ -32,7 +32,7 @@ discard block |
||
32 | 32 | </select> |
33 | 33 | |
34 | 34 | <!-- events if we don't have an EVENT_ID --> |
35 | - <?php if (! empty($active_events)) : ?> |
|
35 | + <?php if ( ! empty($active_events)) : ?> |
|
36 | 36 | <label for="EVT_ID_select"><?php _e('Select Event', 'event_espresso'); ?></label> |
37 | 37 | <select name="EVT_ID" id="EVT_ID_select"> |
38 | 38 | <?php foreach ($active_events as $event) : ?> |
@@ -12,7 +12,7 @@ |
||
12 | 12 | <span class="ee-messages-shortcodes-chooser js-open-list-trigger dashicons dashicons-menu"> |
13 | 13 | <ul id="ee_shortcode_chooser_<?php echo $fieldname; ?>" class="ee_shortcode_chooser_container hidden"> |
14 | 14 | <?php |
15 | - foreach ($shortcodes as $shortcode => $label) : ?> |
|
15 | + foreach ($shortcodes as $shortcode => $label) : ?> |
|
16 | 16 | <li> |
17 | 17 | <span class="js-shortcode-selection" data-value="<?php echo esc_attr($shortcode); ?>" |
18 | 18 | data-linked-input-id="<?php echo esc_attr($linked_input_id); ?>"><?php echo $shortcode; ?></span> |
@@ -10,7 +10,7 @@ |
||
10 | 10 | * @type string $linked_input_id The name of the input that the shortcode gets inserted to. |
11 | 11 | */ |
12 | 12 | |
13 | -if (! empty($shortcodes)) : ?> |
|
13 | +if ( ! empty($shortcodes)) : ?> |
|
14 | 14 | <span class="ee-messages-shortcodes-chooser js-open-list-trigger dashicons dashicons-menu"> |
15 | 15 | <ul id="ee_shortcode_chooser_<?php echo $fieldname; ?>" class="ee_shortcode_chooser_container hidden"> |
16 | 16 | <?php |
@@ -3,16 +3,16 @@ discard block |
||
3 | 3 | <div id="espresso-ajax-loading" class="ajax-loader-grey"> |
4 | 4 | <span class="ee-spinner ee-spin"></span><span class="hidden"> |
5 | 5 | <?php |
6 | - _e( |
|
7 | - 'loading...', |
|
8 | - 'event_espresso' |
|
9 | - ); ?></span> |
|
6 | + _e( |
|
7 | + 'loading...', |
|
8 | + 'event_espresso' |
|
9 | + ); ?></span> |
|
10 | 10 | </div> |
11 | 11 | <span id="on-off-nonce-<?php echo $messenger; ?>" class="hidden"><?php echo $nonce; ?></span> |
12 | 12 | <div class="switch"> |
13 | 13 | <?php |
14 | - $checked = $on_off_status ? ' checked="checked"' : ''; |
|
15 | - ?> |
|
14 | + $checked = $on_off_status ? ' checked="checked"' : ''; |
|
15 | + ?> |
|
16 | 16 | <input id="ee-on-off-toggle-<?php echo $messenger; ?>" type="checkbox" |
17 | 17 | class="ee-on-off-toggle ee-toggle-round-flat"<?php echo $checked; ?> |
18 | 18 | value="<?php echo $on_off_action; ?>"> |
@@ -27,9 +27,9 @@ discard block |
||
27 | 27 | <form method="POST" action="" class="mt-settings-form"> |
28 | 28 | <?php echo $template_form_fields; ?> |
29 | 29 | <?php |
30 | - foreach ($hidden_fields as $name => $field) { |
|
31 | - echo $field['field']; |
|
32 | - } ?> |
|
30 | + foreach ($hidden_fields as $name => $field) { |
|
31 | + echo $field['field']; |
|
32 | + } ?> |
|
33 | 33 | <input type="submit" value="<?php _e('Submit', 'event_espresso'); ?>" class="button-secondary no-drag"/> |
34 | 34 | </form> |
35 | 35 | </div> |
@@ -7,9 +7,9 @@ |
||
7 | 7 | <form method="POST" action="" class="mt-settings-form<?php echo $show_form; ?>"> |
8 | 8 | <?php echo $template_form_fields; ?> |
9 | 9 | <?php |
10 | - foreach ($hidden_fields as $name => $field) { |
|
11 | - echo $field['field']; |
|
12 | - } ?> |
|
10 | + foreach ($hidden_fields as $name => $field) { |
|
11 | + echo $field['field']; |
|
12 | + } ?> |
|
13 | 13 | <input type="submit" value="<?php _e('Submit', 'event_espresso'); ?>" |
14 | 14 | class="button-secondary mt-settings-submit no-drag"/> |
15 | 15 | </form> |
@@ -1,20 +1,20 @@ |
||
1 | 1 | <h2><?php esc_html_e('What are Message Templates', 'event_espresso'); ?></h2> |
2 | 2 | <p> |
3 | 3 | <?php printf( |
4 | - esc_html__( |
|
5 | - '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.', |
|
6 | - 'event_espresso' |
|
7 | - ), |
|
8 | - '<em>', |
|
9 | - '</em>' |
|
10 | - ); ?></p> |
|
4 | + esc_html__( |
|
5 | + '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.', |
|
6 | + 'event_espresso' |
|
7 | + ), |
|
8 | + '<em>', |
|
9 | + '</em>' |
|
10 | + ); ?></p> |
|
11 | 11 | <p> |
12 | 12 | <?php esc_html_e( |
13 | - '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.', |
|
14 | - 'event_espresso' |
|
15 | - ); ?></p> |
|
13 | + '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.', |
|
14 | + 'event_espresso' |
|
15 | + ); ?></p> |
|
16 | 16 | <p> |
17 | 17 | <?php esc_html_e( |
18 | - '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").', |
|
19 | - 'event_espresso' |
|
20 | - ); ?></p> |
|
21 | 18 | \ No newline at end of file |
19 | + '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").', |
|
20 | + 'event_espresso' |
|
21 | + ); ?></p> |
|
22 | 22 | \ No newline at end of file |
@@ -3,56 +3,56 @@ |
||
3 | 3 | |
4 | 4 | <h3><?php _e('1. Defaults', 'event_espresso'); ?></h3> |
5 | 5 | <p><?php _e( |
6 | - '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', |
|
7 | - 'event_espresso' |
|
6 | + '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', |
|
7 | + 'event_espresso' |
|
8 | 8 | ); ?></p> |
9 | 9 | <h3><?php _e('2. Activating or Deactivating Messengers', 'event_espresso'); ?></h3> |
10 | 10 | <p><?php _e( |
11 | - '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.', |
|
12 | - 'event_espresso' |
|
11 | + '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.', |
|
12 | + 'event_espresso' |
|
13 | 13 | ); ?></p> |
14 | 14 | <p><?php _e( |
15 | - 'There are two ways to determine whether a messenger is active or not. The first way is via the messenger tab itself.', |
|
16 | - 'event_espresso' |
|
15 | + 'There are two ways to determine whether a messenger is active or not. The first way is via the messenger tab itself.', |
|
16 | + 'event_espresso' |
|
17 | 17 | ); ?></p> |
18 | 18 | <p><?php echo $img1; |
19 | - _e('The green colored gear indicates that this messenger is currently active.', 'event_espresso'); |
|
20 | - echo $img2; |
|
21 | - _e( |
|
22 | - '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.', |
|
23 | - 'event_espresso' |
|
24 | - ); ?></p> |
|
19 | + _e('The green colored gear indicates that this messenger is currently active.', 'event_espresso'); |
|
20 | + echo $img2; |
|
21 | + _e( |
|
22 | + '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.', |
|
23 | + 'event_espresso' |
|
24 | + ); ?></p> |
|
25 | 25 | <p><?php _e( |
26 | - '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:', |
|
27 | - 'event_espresso' |
|
26 | + '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:', |
|
27 | + 'event_espresso' |
|
28 | 28 | ); ?></p> |
29 | 29 | <p><?php echo $img3; |
30 | - printf( |
|
31 | - __('On means of course that the messenger is active and %s means the messenger is inactive.', 'event_espresso'), |
|
32 | - $img4 |
|
33 | - ); ?></p> |
|
30 | + printf( |
|
31 | + __('On means of course that the messenger is active and %s means the messenger is inactive.', 'event_espresso'), |
|
32 | + $img4 |
|
33 | + ); ?></p> |
|
34 | 34 | <p><?php _e( |
35 | - 'Incidentally, the on/off toggle is also what you use to activate or deactivate a messenger.', |
|
36 | - 'event_espresso' |
|
35 | + 'Incidentally, the on/off toggle is also what you use to activate or deactivate a messenger.', |
|
36 | + 'event_espresso' |
|
37 | 37 | ); ?></p> |
38 | 38 | <p><?php _e( |
39 | - '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.', |
|
40 | - 'event_espresso' |
|
39 | + '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.', |
|
40 | + 'event_espresso' |
|
41 | 41 | ); ?></p> |
42 | 42 | <p><?php _e( |
43 | - '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.', |
|
44 | - 'event_espresso' |
|
43 | + '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.', |
|
44 | + 'event_espresso' |
|
45 | 45 | ); ?></p> |
46 | 46 | <p><?php printf( |
47 | - __( |
|
48 | - '%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.', |
|
49 | - 'event_espresso' |
|
50 | - ), |
|
51 | - '<strong>', |
|
52 | - '</strong>' |
|
47 | + __( |
|
48 | + '%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.', |
|
49 | + 'event_espresso' |
|
50 | + ), |
|
51 | + '<strong>', |
|
52 | + '</strong>' |
|
53 | 53 | ); ?></p> |
54 | 54 | <h3><?php _e('3. Activating or Deactivating Message Types', 'event_espresso'); ?></h3> |
55 | 55 | <p><?php _e( |
56 | - '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', |
|
57 | - 'event_espresso' |
|
56 | + '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', |
|
57 | + 'event_espresso' |
|
58 | 58 | ); ?></p> |
59 | 59 | \ No newline at end of file |
@@ -1,15 +1,15 @@ |
||
1 | 1 | <h2><?php esc_html_e('What is the Event Espresso Messages System?', 'event_espresso'); ?></h2> |
2 | 2 | <p> |
3 | 3 | <?php printf( |
4 | - esc_html__( |
|
5 | - '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.', |
|
6 | - 'event_espresso' |
|
7 | - ), |
|
8 | - '<strong>', |
|
9 | - '</strong>' |
|
10 | - ); ?></p> |
|
4 | + esc_html__( |
|
5 | + '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.', |
|
6 | + 'event_espresso' |
|
7 | + ), |
|
8 | + '<strong>', |
|
9 | + '</strong>' |
|
10 | + ); ?></p> |
|
11 | 11 | <p> |
12 | 12 | <?php esc_html_e( |
13 | - '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.', |
|
14 | - 'event_espresso' |
|
15 | - ); ?></p> |
|
16 | 13 | \ No newline at end of file |
14 | + '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.', |
|
15 | + 'event_espresso' |
|
16 | + ); ?></p> |
|
17 | 17 | \ No newline at end of file |
@@ -1,10 +1,10 @@ |
||
1 | 1 | <div id="admin-primary-mbox-dv" class="admin-primary-mbox-dv"> |
2 | 2 | |
3 | - <h3 class="admin-primary-mbox-h4"><?php echo isset($event_name) ? $event_name . ' Custom Template' : ''; ?></h3> |
|
3 | + <h3 class="admin-primary-mbox-h4"><?php echo isset($event_name) ? $event_name.' Custom Template' : ''; ?></h3> |
|
4 | 4 | <input type="hidden" id="ee-msg-current-context" name="MTP_context" value="<?php echo $context; ?>"/> |
5 | 5 | <!-- if this is not a global template then let's show the name and description fields --> |
6 | 6 | <?php |
7 | - if (! $MTP->is_global()) : ?> |
|
7 | + if ( ! $MTP->is_global()) : ?> |
|
8 | 8 | <div class="non-global-mtp-fields"> |
9 | 9 | <p> |
10 | 10 | <?php _e( |
@@ -4,21 +4,21 @@ discard block |
||
4 | 4 | <input type="hidden" id="ee-msg-current-context" name="MTP_context" value="<?php echo $context; ?>"/> |
5 | 5 | <!-- if this is not a global template then let's show the name and description fields --> |
6 | 6 | <?php |
7 | - if (! $MTP->is_global()) : ?> |
|
7 | + if (! $MTP->is_global()) : ?> |
|
8 | 8 | <div class="non-global-mtp-fields"> |
9 | 9 | <p> |
10 | 10 | <?php _e( |
11 | - 'This is a custom template. Custom Templates have an editable name and description to help you differentiate between templates.', |
|
12 | - 'event_espresso' |
|
13 | - ); ?> |
|
11 | + 'This is a custom template. Custom Templates have an editable name and description to help you differentiate between templates.', |
|
12 | + 'event_espresso' |
|
13 | + ); ?> |
|
14 | 14 | </p> |
15 | 15 | <div id="titlediv"> |
16 | 16 | <div id="titlewrap"> |
17 | 17 | <label for="title" class="label-MTP_name" style="visibility:hidden"> |
18 | 18 | <?php _e( |
19 | - 'Message Template Name:', |
|
20 | - 'event_espresso' |
|
21 | - ); ?></label> |
|
19 | + 'Message Template Name:', |
|
20 | + 'event_espresso' |
|
21 | + ); ?></label> |
|
22 | 22 | <input id="title" type="text" class="regular-text" name="ee_msg_non_global_fields[MTP_name]" |
23 | 23 | value="<?php echo $MTP->name(); ?>"> |
24 | 24 | </div> |
@@ -27,29 +27,29 @@ discard block |
||
27 | 27 | <label for="ee-msg-non-global-fields-MTP_description" class="label-MTP_description" |
28 | 28 | style="visibility:hidden;"> |
29 | 29 | <?php _e( |
30 | - 'Message Template Description:', |
|
31 | - 'event_espresso' |
|
32 | - ); ?></label> |
|
30 | + 'Message Template Description:', |
|
31 | + 'event_espresso' |
|
32 | + ); ?></label> |
|
33 | 33 | <textarea id="ee-msg-non-global-fields-MTP_description" class="large-text" |
34 | 34 | name="ee_msg_non_global_fields[MTP_description]"><?php echo $MTP->description(); ?></textarea> |
35 | 35 | </p> |
36 | 36 | </div> |
37 | 37 | <?php |
38 | - else : |
|
39 | - ?> |
|
38 | + else : |
|
39 | + ?> |
|
40 | 40 | <input type="hidden" name="ee_msg_non_global_fields[MTP_name]" value="<?php echo $MTP->name(); ?>"> |
41 | 41 | <input type="hidden" name="ee_msg_non_global_fields[MTP_description]" |
42 | 42 | value="<?php echo $MTP->description(); ?>"> |
43 | 43 | <?php endif; ?> |
44 | 44 | <!-- we need to loop through the template_fields so we know our structure --> |
45 | 45 | <?php |
46 | - if (isset($template_fields) && ! empty($template_fields) && ! is_wp_error($template_fields)) { |
|
47 | - echo $template_fields; |
|
48 | - } else { |
|
49 | - ?> |
|
46 | + if (isset($template_fields) && ! empty($template_fields) && ! is_wp_error($template_fields)) { |
|
47 | + echo $template_fields; |
|
48 | + } else { |
|
49 | + ?> |
|
50 | 50 | <p><?php _e('Something has gone wrong, there are no template fields to output.', 'event_espresso'); ?></p> |
51 | 51 | <?php |
52 | - } |
|
52 | + } |
|
53 | 53 | |
54 | - ?> |
|
54 | + ?> |
|
55 | 55 | </div> <!-- end #admin-primary-mbox-dv --> |
@@ -35,9 +35,12 @@ |
||
35 | 35 | </p> |
36 | 36 | </div> |
37 | 37 | <?php |
38 | - else : |
|
38 | + else { |
|
39 | + : |
|
39 | 40 | ?> |
40 | - <input type="hidden" name="ee_msg_non_global_fields[MTP_name]" value="<?php echo $MTP->name(); ?>"> |
|
41 | + <input type="hidden" name="ee_msg_non_global_fields[MTP_name]" value="<?php echo $MTP->name(); |
|
42 | + } |
|
43 | + ?>"> |
|
41 | 44 | <input type="hidden" name="ee_msg_non_global_fields[MTP_description]" |
42 | 45 | value="<?php echo $MTP->description(); ?>"> |
43 | 46 | <?php endif; ?> |
@@ -1,28 +1,28 @@ |
||
1 | 1 | <div class="<?php echo $messenger; ?>-content"> |
2 | 2 | <?php |
3 | - if (empty($inactive_message_types) && empty($active_message_types)) : |
|
4 | - echo '<p>' |
|
5 | - . __( |
|
6 | - '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.', |
|
7 | - 'event_espresso' |
|
8 | - ) . '</p>'; |
|
9 | - else : ?> |
|
3 | + if (empty($inactive_message_types) && empty($active_message_types)) : |
|
4 | + echo '<p>' |
|
5 | + . __( |
|
6 | + '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.', |
|
7 | + 'event_espresso' |
|
8 | + ) . '</p>'; |
|
9 | + else : ?> |
|
10 | 10 | <p class="inactive-on-message <?php echo $hide_on_message; ?>"> |
11 | 11 | <?php _e( |
12 | - 'Below are message types that are currently inactive with this messenger. Drag them over to the messenger box to activate them.', |
|
13 | - 'event_espresso' |
|
14 | - ); ?> |
|
12 | + 'Below are message types that are currently inactive with this messenger. Drag them over to the messenger box to activate them.', |
|
13 | + 'event_espresso' |
|
14 | + ); ?> |
|
15 | 15 | <p> |
16 | 16 | <p class="inactive-off-message <?php echo $hide_off_message; ?>"> |
17 | 17 | <?php _e( |
18 | - 'This messenger is currently inactive. Once the messenger is activated any inactive message types associated with the messenger will be shown here.', |
|
19 | - 'event_espresso' |
|
20 | - ); ?> |
|
18 | + 'This messenger is currently inactive. Once the messenger is activated any inactive message types associated with the messenger will be shown here.', |
|
19 | + 'event_espresso' |
|
20 | + ); ?> |
|
21 | 21 | </p> |
22 | 22 | <div<?php |
23 | - if ($active) : |
|
24 | - ?> id="inactive-message-types"<?php |
|
25 | - endif; ?> |
|
23 | + if ($active) : |
|
24 | + ?> id="inactive-message-types"<?php |
|
25 | + endif; ?> |
|
26 | 26 | class="inactive-message-types mt-tab-container ui-widget-content-ui-state-default <?php echo $hide_on_message; ?>"> |
27 | 27 | <ul class="messenger-activation"> |
28 | 28 | <?php echo $inactive_message_types; ?> |
@@ -5,7 +5,7 @@ |
||
5 | 5 | . __( |
6 | 6 | '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.', |
7 | 7 | 'event_espresso' |
8 | - ) . '</p>'; |
|
8 | + ).'</p>'; |
|
9 | 9 | else : ?> |
10 | 10 | <p class="inactive-on-message <?php echo $hide_on_message; ?>"> |
11 | 11 | <?php _e( |
@@ -6,8 +6,11 @@ |
||
6 | 6 | '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.', |
7 | 7 | 'event_espresso' |
8 | 8 | ) . '</p>'; |
9 | - else : ?> |
|
10 | - <p class="inactive-on-message <?php echo $hide_on_message; ?>"> |
|
9 | + else { |
|
10 | + : ?> |
|
11 | + <p class="inactive-on-message <?php echo $hide_on_message; |
|
12 | + } |
|
13 | + ?>"> |
|
11 | 14 | <?php _e( |
12 | 15 | 'Below are message types that are currently inactive with this messenger. Drag them over to the messenger box to activate them.', |
13 | 16 | 'event_espresso' |