@@ -1,5 +1,5 @@ |
||
1 | 1 | <li id="<?php echo $slug_id; ?>" class="ui-widget-content ui-corner-tr mt-tab <?php echo $class; ?>"> |
2 | - <div id="<?php echo $slug_id; ?>-handle" class="mt-handlediv no-drag" title="<?php esc_attr_e( 'Click to toggle', 'event_espresso' ); ?>"><br></div> |
|
2 | + <div id="<?php echo $slug_id; ?>-handle" class="mt-handlediv no-drag" title="<?php esc_attr_e('Click to toggle', 'event_espresso'); ?>"><br></div> |
|
3 | 3 | <h4 class="ui-widget-header"><?php echo $label; ?></h4> |
4 | 4 | <?php echo $content; ?> |
5 | 5 | <span class="mt_nonce hidden"><?php echo $mt_nonce; ?></span> |
@@ -1,4 +1,4 @@ |
||
1 | 1 | <h2><?php _e('What are Message Templates', 'event_espresso'); ?></h2> |
2 | 2 | <p><?php _e('Message Templates are the <em>format</em> 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'); ?></p> |
3 | 3 | <p><?php _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> |
4 | -<p><?php _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> |
|
5 | 4 | \ No newline at end of file |
5 | +<p><?php _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> |
|
6 | 6 | \ No newline at end of file |
@@ -8,10 +8,10 @@ |
||
8 | 8 | <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'); ?></p> |
9 | 9 | <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> |
10 | 10 | <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'); ?></p> |
11 | -<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> |
|
12 | -<p><?php _e( 'Incidentally, the on/off toggle is also what you use to activate or deactivate a messenger.', 'event_espresso' ); ?></p> |
|
13 | -<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'); ?></p> |
|
14 | -<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'); ?></p> |
|
15 | -<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>' ); ?></p> |
|
11 | +<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> |
|
12 | +<p><?php _e('Incidentally, the on/off toggle is also what you use to activate or deactivate a messenger.', 'event_espresso'); ?></p> |
|
13 | +<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'); ?></p> |
|
14 | +<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'); ?></p> |
|
15 | +<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>'); ?></p> |
|
16 | 16 | <h3><?php _e('3. Activating or Deactivating Message Types', 'event_espresso'); ?></h3> |
17 | 17 | <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'); ?></p> |
18 | 18 | \ No newline at end of file |
@@ -2,7 +2,7 @@ |
||
2 | 2 | <p><?php _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'); ?></p> |
3 | 3 | |
4 | 4 | <?php |
5 | -foreach ( $shortcodes as $name => $description ) : |
|
5 | +foreach ($shortcodes as $name => $description) : |
|
6 | 6 | ?> |
7 | 7 | <h3><?php echo $name; ?></h3> |
8 | 8 | <p><?php echo $description; ?></p> |
@@ -7,7 +7,7 @@ discard block |
||
7 | 7 | <p><?php echo $img2; ?></p> |
8 | 8 | <p><?php _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> |
9 | 9 | <p><?php _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> |
10 | -<p><?php printf( __('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>' ); ?> |
|
10 | +<p><?php printf(__('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>'); ?> |
|
11 | 11 | </p> |
12 | 12 | <h3><?php _e('3. Template Form Fields', 'event_espresso'); ?></h3> |
13 | 13 | <p><?php echo $img3; ?><?php _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> |
@@ -18,7 +18,7 @@ discard block |
||
18 | 18 | <?php echo $img4; ?><?php _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'); ?> |
19 | 19 | </p> |
20 | 20 | <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> |
21 | -<p><?php printf( __('%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>' ); ?> |
|
21 | +<p><?php printf(__('%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>'); ?> |
|
22 | 22 | </p> |
23 | 23 | <div style="clear:both"></div> |
24 | 24 | <h3><?php _e('5. Override All Custom', 'event_espresso'); ?></h3> |
@@ -1,2 +1,2 @@ |
||
1 | 1 | <h2><?php _e('What are Messengers?', 'event_espresso'); ?></h2> |
2 | -<p><?php printf( __('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> |
|
3 | 2 | \ No newline at end of file |
3 | +<p><?php printf(__('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> |
|
4 | 4 | \ No newline at end of file |
@@ -5,7 +5,7 @@ |
||
5 | 5 | <div class"mt-settings"> |
6 | 6 | <form method="POST" action="" class="mt-settings-form<?php echo $show_form; ?>"> |
7 | 7 | <?php echo $template_form_fields; ?> |
8 | - <?php foreach ( $hidden_fields as $name => $field ) { |
|
8 | + <?php foreach ($hidden_fields as $name => $field) { |
|
9 | 9 | echo $field['field']; |
10 | 10 | } ?> |
11 | 11 | <input type="submit" value="<?php _e('Submit', 'event_espresso'); ?>" class="button-secondary mt-settings-submit no-drag" /> |
@@ -1,5 +1,5 @@ discard block |
||
1 | 1 | <?php |
2 | -if (!defined('EVENT_ESPRESSO_VERSION') ) |
|
2 | +if ( ! defined('EVENT_ESPRESSO_VERSION')) |
|
3 | 3 | exit('NO direct script access allowed'); |
4 | 4 | |
5 | 5 | /** |
@@ -87,13 +87,13 @@ discard block |
||
87 | 87 | |
88 | 88 | |
89 | 89 | public function load_scripts_styles() { |
90 | - wp_register_style( 'ee-other-services-css', EE_OTHER_SERVICES_ASSETS_URL . 'other-services.css' , array('ee-admin-css') , EVENT_ESPRESSO_VERSION ); |
|
91 | - wp_enqueue_style( 'ee-other-services-css' ); |
|
90 | + wp_register_style('ee-other-services-css', EE_OTHER_SERVICES_ASSETS_URL.'other-services.css', array('ee-admin-css'), EVENT_ESPRESSO_VERSION); |
|
91 | + wp_enqueue_style('ee-other-services-css'); |
|
92 | 92 | } |
93 | 93 | |
94 | 94 | |
95 | 95 | protected function _other_services() { |
96 | - $this->_template_args['admin_page_content'] = EEH_Template::display_template( EE_OTHER_SERVICES_ADMIN_TEMPLATE_PATH . 'other_services_content.template.php', array(), true ); |
|
96 | + $this->_template_args['admin_page_content'] = EEH_Template::display_template(EE_OTHER_SERVICES_ADMIN_TEMPLATE_PATH.'other_services_content.template.php', array(), true); |
|
97 | 97 | $this->display_admin_page_with_no_sidebar(); |
98 | 98 | } |
99 | 99 |
@@ -6,8 +6,9 @@ |
||
6 | 6 | * @package Event Espresso |
7 | 7 | * @subpackage messages |
8 | 8 | */ |
9 | -if (!defined('EVENT_ESPRESSO_VERSION') ) |
|
9 | +if (!defined('EVENT_ESPRESSO_VERSION') ) { |
|
10 | 10 | exit('NO direct script access allowed'); |
11 | +} |
|
11 | 12 | |
12 | 13 | /** |
13 | 14 | * |
@@ -1,5 +1,5 @@ discard block |
||
1 | 1 | <?php |
2 | -if (!defined('EVENT_ESPRESSO_VERSION') ) |
|
2 | +if ( ! defined('EVENT_ESPRESSO_VERSION')) |
|
3 | 3 | exit('NO direct script access allowed'); |
4 | 4 | |
5 | 5 | /** |
@@ -32,11 +32,11 @@ discard block |
||
32 | 32 | |
33 | 33 | public function __construct() { |
34 | 34 | //define some help/support page related constants |
35 | - define( 'EE_OTHER_SERVICES_PG_SLUG', 'espresso_packages' ); |
|
36 | - define( 'EE_OTHER_SERVICES_ADMIN_URL', admin_url('admin.php?page=' . EE_OTHER_SERVICES_PG_SLUG )); |
|
37 | - define( 'EE_OTHER_SERVICES_ADMIN_TEMPLATE_PATH', EE_ADMIN_PAGES . 'other_services/templates/'); |
|
38 | - define( 'EE_OTHER_SERVICES_ADMIN', EE_ADMIN_PAGES . 'other_services/' ); |
|
39 | - define( 'EE_OTHER_SERVICES_ASSETS_URL', EE_ADMIN_PAGES_URL . 'other_services/assets/'); |
|
35 | + define('EE_OTHER_SERVICES_PG_SLUG', 'espresso_packages'); |
|
36 | + define('EE_OTHER_SERVICES_ADMIN_URL', admin_url('admin.php?page='.EE_OTHER_SERVICES_PG_SLUG)); |
|
37 | + define('EE_OTHER_SERVICES_ADMIN_TEMPLATE_PATH', EE_ADMIN_PAGES.'other_services/templates/'); |
|
38 | + define('EE_OTHER_SERVICES_ADMIN', EE_ADMIN_PAGES.'other_services/'); |
|
39 | + define('EE_OTHER_SERVICES_ASSETS_URL', EE_ADMIN_PAGES_URL.'other_services/assets/'); |
|
40 | 40 | |
41 | 41 | parent::__construct(); |
42 | 42 | } |
@@ -46,7 +46,7 @@ discard block |
||
46 | 46 | } |
47 | 47 | |
48 | 48 | protected function _set_menu_map() { |
49 | - $this->_menu_map = new EE_Admin_Page_Sub_Menu( array( |
|
49 | + $this->_menu_map = new EE_Admin_Page_Sub_Menu(array( |
|
50 | 50 | 'menu_group' => 'extras', |
51 | 51 | 'menu_order' => 30, |
52 | 52 | 'show_on_menu' => EE_Admin_Page_Menu_Map::BLOG_AND_NETWORK_ADMIN, |
@@ -6,8 +6,9 @@ |
||
6 | 6 | * @package Event Espresso |
7 | 7 | * @subpackage messages |
8 | 8 | */ |
9 | -if (!defined('EVENT_ESPRESSO_VERSION') ) |
|
9 | +if (!defined('EVENT_ESPRESSO_VERSION') ) { |
|
10 | 10 | exit('NO direct script access allowed'); |
11 | +} |
|
11 | 12 | |
12 | 13 | /** |
13 | 14 | * |