By default, Event Espresso 4 uses the /events/ Custom Post Type (CPT) slug (permalink) to organize your events. The word “events” is a generic term for all types of happenings, classes, conferences, workshops, fundraisers, virtual events, etc. If your organization hosts one type of event, or uses a different word or translated word, it may add clarity to your events by renaming the events CPT slug to the single type of event that you host, e.g. “workshops” or “conferences”.

To Change the Custom Post Type (CPT) Slug

Login to your WordPress dashboard (WP-admin) and go to Events –> Templates. Then look for the Events List Pages section and then Event Slug. Change events to your new slug (e.g. workshops, courses, classes, etc) and save changes by clicking on the save button.

Then immediately go to Settings (your WordPress settings not Event Espresso settings) –> Permalinks to refresh your permalink on your WordPress site. This step is important.

More Information
For more information about re-declaring/changing a plugin’s Custom Post Type slug, please check this post on the WordPress Stack Exchange website: http://wordpress.stackexchange.com/questions/41988/redeclare-change-slug-of-a-plugins-custom-post-type

Want to change the custom post type slug for venues? See this tutorial

Want to change the custom post type slug for people (People add-on)? See this tutorial

In this tutorial we will explain how to add a message to registration checkout to let your registrants know that a PayPal account is optional. This will only work for PayPal premier and business account holders. Additionally, PayPal disables guest checkout for buyers in certain countries. If you are not sure if you have the correct account, then please get in touch with PayPal support.

Enable Guest Checkout through your PayPal Account

Login to your PayPal.com account. Then click on Profile. On the next page, locate the Selling online section and then Website preferences. Click on the Update link for Website preferences. Scroll down the page until you see the setting for PayPal Account Optional. Set it to On and then click on the Save button which appears at the end of the page.

Change the Current PayPal Messaging

The existing PayPal messaging can be changed using a gettext filter for WordPress. Below we have some sample code that will do that for you:

function ee_payment_options_paypal_optional( $translated, $original, $domain ) {
$strings = array(
 'After finalizing your registration, you will be transferred to the PayPal.com website where your payment will be securely processed.' => 'Upon clicking on the Finalize Registration button, you will be transferred to PayPal.com where your payment will be securely processed. A <strong>PayPal account is not required</strong> and you can pay with a credit or debit card.'
 );
if ( isset( $strings[$original] ) ) {
 $translations = &get_translations_for_domain( $domain );
 $translated = $translations->translate( $strings[$original] );
 }
return $translated;
}
add_filter( 'gettext', 'ee_payment_options_paypal_optional', 10, 3 );

The filter above works by looking for a match for the existing messaging for PayPal and then replacing it with something else. The sample code can be copied and pasted into a site specific plugin. Be sure to save your edits and then you can go to an event and begin a registration to see how it appears.

Here is what our sample code looks like on the registration checkout page:

You can take this tutorial a step further by changing the default PayPal logo to one that shows the PayPal logo and major credit cards. See this additional resource for more information:

https://gist.github.com/lorenzocaum/831c531ca80906af2353

By default the ticket selector will have different quantities of tickets available — usually 0 through 10. It may be useful to have the ticket selector set to a certain value for certain events. For example, if you are hosting a training course or an online meeting or webinar, then it would be helpful to have the ticket selector default to a value of 1. This will speed up the registration checkout process since the registrant would not need to adjust the ticket selector from 0 to 1.

In the first part of this tutorial, we’ll create a ticket that has a minimum and maximum quantity and in the second part we’ll setup a code snippet of jQuery to handle removing the 0 value. Once both of these are in place, then the ticket selector will default to a value of 1.

Create a Ticket with a Minimum and Maximum Quantity of 1

Login to your WordPress admin. Then find Event Espresso in your WordPress admin menu and click on Events. Now look for your event in the event overview page and click on it. This will take you to the Event Editor.

If this is a new event, then go ahead and setup your event by adding a title, description, venue, tickets, etc and then save your event as a draft. If this is an existing event, then scroll down to the Event Tickets & Datetimes area. Then click on the gear to access the advanced options for this ticket. Now set the Minimum Quantity to 1 and set the Maximum Quantity to 1:

Use jQuery to Remove the Value of 0

Next, we need to add some jQuery to remove the value of 0. Below we have some sample code that will do that for you:

function ee_default_ticket_selector_one() {
 $post = get_the_id();
 if( $post == 123 ) {
 ?>
 <script type="text/javascript">
 jQuery(document).ready(function () {
 jQuery("#ticket-selector-tbl-qty-slct-123-1 option[value='0']").remove();
});
 </script>
 <?php
 }
}
add_action( 'wp_footer', 'ee_default_ticket_selector_one' );

It checks to see if you are on a specific single event page. Then it removes the option value of 0.

The sample code above can be copied and pasted into a site specific plugin.

Then change the number 123 (used twice in the sample code above) to the post id of your actual event. The post id appears to the left of the event name when viewing the events overview screen. It also appears at the end of the URL when viewing an event in the event editor. Be sure to save changes after updating the sample code. Then view your event page on the front end and the quantity selector should now default to 1.

Here is what the ticket selector for our example event looks like:

Additional Examples

If you would like to remove the 0 value for an event with a post id of 123 and an additional event with a post id of 456, then you could use the sample code below.

function ee_default_ticket_selector_one_multiple_events() {
 $post = get_the_id();
 ?>
 <script type="text/javascript">
 jQuery(document).ready(function () {
 jQuery("#ticket-selector-tbl-qty-slct-123-1 option[value='0']").remove();
 jQuery("#ticket-selector-tbl-qty-slct-456-1 option[value='0']").remove();
});
 </script>
 <?php
 }
add_action( 'wp_footer', 'ee_default_ticket_selector_one_multiple_events' );

If you would like to remove the 0 value for all events, then you could use the sample code below.

function ee_default_ticket_selector_one_all_events() {
 ?>
 <script type="text/javascript">
 jQuery(document).ready(function () {
 jQuery("option[value='0']").remove();
});
 </script>
 <?php
 }
add_action( 'wp_footer', 'ee_default_ticket_selector_one_all_events' );

Be advised that it will remove the value of 0 from all select menus on your site since the conditional check for a specific single event page and CSS id targetting is no longer in place.

In this guide, we’ll show you how to style the buttons that are used on the front end for Event Espresso. Below we have examples of the buttons that you’ll see during registration checkout. The buttons below are from the Twenty Twelve theme which includes basic styling for buttons.

	This button is used after entering registrant details and will take you to the payment options page
	This button is used to finish up a registration and will take you to the thank you page
	This button is used to process a payment if the initial payment attempt fails
	This button is used to update the registration details for an existing registration

Some themes include existing styling for buttons while others do not. If your theme does not have existing styles for buttons, then your buttons may appear as a default grey.

These buttons can be styled to any color by using CSS and these styles can be added to your child theme’s stylesheet or through a plugin like My Custom CSS or Reaktiv CSS Builder.

Proceed to Payment Options button style

A tool like Firebug or Chrome Developer Tools can be used to inspect the buttons to see the CSS classes and ids that are in use. Here is an example from Chrome Developer Tools for the Proceed to Payment Options button:

The screenshot shows that there is a CSS id of spco-go-to-step-payment_options-btn and a CSS class of spco-next-step-btn. We can then use this information to change the style for our button. The following code will change the color for the Proceed to Payment Options button from grey to blue:

#spco-go-to-step-payment_options-btn {
   border-top: 1px solid #96d1f8;
   background: #65a9d7;
   padding: 5px 10px;
   -webkit-border-radius: 5px;
   -moz-border-radius: 5px;
   border-radius: 5px;
   -webkit-box-shadow: rgba(0,0,0,1) 0 1px 0;
   -moz-box-shadow: rgba(0,0,0,1) 0 1px 0;
   box-shadow: rgba(0,0,0,1) 0 1px 0;
   text-shadow: rgba(0,0,0,.4) 0 1px 0;
   color: white;
   font-size: 14px;
   text-decoration: none;
   vertical-align: middle;
   }
#spco-go-to-step-payment_options-btn:hover {
   border-top-color: #28597a;
   background: #28597a;
   color: #ccc;
   }
#spco-go-to-step-payment_options-btn:active {
   border-top-color: #1b435e;
   background: #1b435e;
   }

To apply these new styles, just copy and paste them into your child theme’s stylesheet or into a plugin like My Custom CSS or Reaktiv CSS Builder.

Finalize Registration button style & Process Payment button style & Update Registration Details button style

The Finalize Registration button, Process Payment button, and Update Registration Details button have a CSS id of spco-go-to-step-finalize_registration-btn and a CSS class of spco-next-step-btn. The following code will change the color for the Finalize Registration button, Process Payment button, and Update Registration Details button from grey to blue:

#spco-go-to-step-finalize_registration-btn {
   border-top: 1px solid #96d1f8;
   background: #65a9d7;
   padding: 5px 10px;
   -webkit-border-radius: 5px;
   -moz-border-radius: 5px;
   border-radius: 5px;
   -webkit-box-shadow: rgba(0,0,0,1) 0 1px 0;
   -moz-box-shadow: rgba(0,0,0,1) 0 1px 0;
   box-shadow: rgba(0,0,0,1) 0 1px 0;
   text-shadow: rgba(0,0,0,.4) 0 1px 0;
   color: white;
   font-size: 14px;
   text-decoration: none;
   vertical-align: middle;
   }
#spco-go-to-step-finalize_registration-btn:hover {
   border-top-color: #28597a;
   background: #28597a;
   color: #ccc;
   }
#spco-go-to-step-finalize_registration-btn:active {
   border-top-color: #1b435e;
   background: #1b435e;
   }

To apply these new styles, just copy and paste them into your child theme’s stylesheet or into a plugin like My Custom CSS or Reaktiv CSS Builder.

View Details and Register Now button style

The following buttons are not using during registration checkout but CSS examples are included below.

	This button is used on the event list page
	This button is used on the single event pages

The View Details buttons and Register Now buttons will have different CSS ids for each event. For example, if our event had a post id of 123, then the CSS id would be ticket-selector-submit-123-btn.

The following code will change the color for the View Details button and Register Now button for a specific event with a post id of 123 from grey to blue:

#ticket-selector-submit-123-btn {
   border-top: 1px solid #96d1f8;
   background: #65a9d7;
   padding: 5px 10px;
   -webkit-border-radius: 5px;
   -moz-border-radius: 5px;
   border-radius: 5px;
   -webkit-box-shadow: rgba(0,0,0,1) 0 1px 0;
   -moz-box-shadow: rgba(0,0,0,1) 0 1px 0;
   box-shadow: rgba(0,0,0,1) 0 1px 0;
   text-shadow: rgba(0,0,0,.4) 0 1px 0;
   color: white;
   font-size: 14px;
   text-decoration: none;
   vertical-align: middle;
   }
#ticket-selector-submit-123-btn:hover {
   border-top-color: #28597a;
   background: #28597a;
   color: #ccc;
   }
#ticket-selector-submit-123-btn:active {
   border-top-color: #1b435e;
   background: #1b435e;
   }

The CSS class of ticket-selector-submit-btn applies to all View Details and Register Now buttons. The following code will change the color for all View Details buttons and Register Now buttons from grey to blue:

.ticket-selector-submit-btn {
   border-top: 1px solid #96d1f8;
   background: #65a9d7;
   padding: 5px 10px;
   -webkit-border-radius: 5px;
   -moz-border-radius: 5px;
   border-radius: 5px;
   -webkit-box-shadow: rgba(0,0,0,1) 0 1px 0;
   -moz-box-shadow: rgba(0,0,0,1) 0 1px 0;
   box-shadow: rgba(0,0,0,1) 0 1px 0;
   text-shadow: rgba(0,0,0,.4) 0 1px 0;
   color: white;
   font-size: 14px;
   text-decoration: none;
   vertical-align: middle;
   }
.ticket-selector-submit-btn:hover {
   border-top-color: #28597a;
   background: #28597a;
   color: #ccc;
   }
.ticket-selector-submit-btn:active {
   border-top-color: #1b435e;
   background: #1b435e;
   }

To apply these new styles, just copy and paste them into your child theme’s stylesheet or into a plugin like My Custom CSS or Reaktiv CSS Builder.

There are several resources available for creating CSS buttons:

CSS tricks button maker

CSS portal button generator

CSS drive button generator

In this article, we’ll show you how to customize the text that is used for these buttons. Below we have examples of the buttons that you’ll see during registration checkout:

	This button is used after entering registrant details and will take you to the payment options page
	This button is used to finish up a registration and will take you to the thank you page
	This button is used to update the registration details for an existing registration

These changes will be applied using WordPress filters. Its best to add the sample code snippets below to a site specific plugin. You can view our guide on creating a site specific plugin for WordPress.

Some Example code

Here’s some example code that’s intended to be instructional. If you’re familiar with the WordPress Plugin API you’ll note the use of the add_filters() function:

Specific, one-off examples

How to change the Proceed to Payment Options button text

The following code will change the only the text for the Proceed to Payment Options button:

function ee_proceed_to_button( $submit_button_text, EE_Checkout $checkout ) {
 if ( ! $checkout instanceof EE_Checkout || ! $checkout->current_step instanceof EE_SPCO_Reg_Step || ! $checkout->next_step instanceof EE_SPCO_Reg_Step ) {
  return $submit_button_text;
 } 
 if ( $checkout->next_step->slug() == 'payment_options' ) {
  $submit_button_text = 'Go to Payment Processing';
 }
 return $submit_button_text;
}

add_filter ( 'FHEE__EE_SPCO_Reg_Step__set_submit_button_text___submit_button_text', 'ee_proceed_to_button', 10, 2 );

To apply this function, you copy and paste the code into your site specific plugin. You can change “Go to Payment Processing” to something else and save your changes.

How to change the Finalize Registration button text

The following code will change only the text for the Finalize Registration button:

function ee_finalize_registration_button( $submit_button_text, EE_Checkout $checkout ) {
 if ( ! $checkout instanceof EE_Checkout || ! $checkout->current_step instanceof EE_SPCO_Reg_Step || ! $checkout->next_step instanceof EE_SPCO_Reg_Step ) {
  return $submit_button_text;
 }
 if ( $checkout->next_step->slug() == 'finalize_registration' ) {
  $submit_button_text = 'Complete My Registration';
 }
 return $submit_button_text;
}

add_filter ( 'FHEE__EE_SPCO_Reg_Step__set_submit_button_text___submit_button_text', 'ee_finalize_registration_button', 10, 2 );

The function for ee_finalize_registration_button will only change “Finalize Registration” to “Complete My Registration”.

To apply this function, you copy and paste it into your site specific plugin. Then change “Complete My Registration” to something else and save changes.

How to change the Update Attendee Information button text

The following code will change the text only for the Update Attendee Information button:

function ee_update_registration_details_button( $submit_button_text, EE_Checkout $checkout ) {
 if ( ! $checkout instanceof EE_Checkout || ! $checkout->current_step instanceof EE_SPCO_Reg_Step || ! $checkout->next_step instanceof EE_SPCO_Reg_Step ) {
  return $submit_button_text;
 } 
 if ( $checkout->current_step->slug() == 'attendee_information' && $checkout->revisit ) {
  $submit_button_text = 'Yes I Want To Change My Registration Details';
 }
 return $submit_button_text; 
}

add_filter ( 'FHEE__EE_SPCO_Reg_Step__set_submit_button_text___submit_button_text', 'ee_update_registration_details_button', 11, 2 );

The function for ee_update_registration_details_button will change only “Update Attendee Informations” to “Yes I Want To Change My Registration Details.”

To apply this function, you copy and paste it into your site specific plugin. Then change “Yes I Want To Change My Registration Details” to something else and save changes.

How to change the View Details and Register Now button text

The following buttons are not using during registration checkout but code snippets are included below should you need them.

	This button is used on the event list page
	This button is used on the single event pages

The following code will change the text for the View Details button:

function ee_view_details_button() {
 return 'Learn More About This Event';
}

add_filter ('FHEE__EE_Ticket_Selector__display_view_details_btn__btn_text', 'ee_view_details_button');

The above code will change “View Details” to “Learn More About This Event.”

To apply this function, you copy and paste it into your site specific plugin. Then change “Learn More About This Event” to something else and save changes.

The following code will change the text for the Register Now button:

function ee_register_now_button() {
 return 'Buy';
}

add_filter ('FHEE__EE_Ticket_Selector__display_ticket_selector_submit__btn_text', 'ee_register_now_button');

The above code will change “Register Now” to “Buy”.

To apply this function, you copy and paste it into your site specific plugin. Then change “Buy” to something else and save changes.

In this post we’ll learn how to show tickets that have a cost of zero as free and remove the dollar amount showing from the pricing option (ticket) selector. Lets begin by taking a look at a screenshot below of the default configuration of the price of a free (0.00) ticket:

We can see in the screenshot that the default configuration for a free ticket has a pricing of zero (shown as 0.00). Now, to show the price as “free” instead of “0.00.” you can will change this default configuration on your own site with a filter.

function convert_zero_to_free( $amount, $return_raw ) {

    if ( ! $return_raw || ! is_admin() ) {

     $amount = $amount == 0 ?  __( 'free', 'event_espresso' ) : $amount; 

    }
    return $amount;
}
add_filter( 'FHEE__EEH_Template__format_currency__amount', 'convert_zero_to_free', 10, 2 );

There are a couple ways to add the filter above to your site. The first is to add the code to your theme’s functions.php file. However, this edit may be lost if you update your theme and it removes and replaces the functions.php file. We strongly recommend a safer method of applying this filter to your site to protect it from being overwritten by theme updates by creating a custom/site-specific plugin.

Once this filter is in place, go to any events on your site that has a 0.00 priced ticket and you’ll see that the pricing has been transformed from 0.00 to free: