Child Themes Now Available for Event Espresso 4

Ever find yourself wishing that WordPress themes would look better, out of the box, with Event Espresso 4? Well, I have some good news! We now have a small selection of child themes available for Event Espresso 4.

We have been using a selection of about 20, optimized WordPress child themes on our hosted platform, Event Smart, for the past two years. I’ve always thought it would be a great idea to release these themes to Event Espresso users, so I’ve started a new, bare-bones, little theme shop called, Espresso Themes, where I am hosting a limited selection of WordPress child themes, specially brewed, just for Event Espresso 4.

Child Themes Optimized for Event Espresso 4

Many WordPress themes tend to display the published date on each post, which usually conflicts with the event dates, which is confusing to your customers.

The following screenshot is an example of the default Baskerville WordPress theme. If you look at the post meta section at the bottom, you can see the author information, then on the right side, the post date and post category.

Default WordPress Post Output - Baskerville Theme

Default WordPress Post Output – Baskerville Theme

 

However, if you are running Event Espresso, the event date that shows on the single event page, or the event list doesn’t correspond to the post date. In the example below, the post date that shows in the post meta output of the theme, which is confusing to event goers that are trying to learn about the event.

On Event Smart, we have engineered around twenty child themes to show the event dates, instead of the post dates in those places.

In the example below, the post date section has been removed on the single event post.

Optimized WordPress Event Output - Baskerville Child Theme

Optimized WordPress Event Output – Baskerville Child Theme

 

As you can see, the child themes have been optimized for Event Espresso 4 to display event dates and times, instead of post dates, which are common in many default WordPress themes. In this case, I removed the meta box entirely, as I thought it made the event page cleaner and focused on purchasing tickets.

Four child themes launched in October

In October, I started the website and made four new child themes available. Now, I have plans to launch around 20 more in the coming weeks, in between other tasks. The primary functions to launch a new child theme are relatively tedious but straightforward.

What about support and one-click updates?

Support and one-click updates for the child themes are primarily handled via Github and a private theme update service, called Kernl.

What about premium themes?

I’ve decided to create a section dedicated to premium themes that work well with Event Espresso. From there you will find a selection of third-party event themes and standard themes that work well with Event Espresso.

Why create a new theme shop?

One reason is that we don’t have a system to deploy automated theme updates as we do for the plugin. Instead of adding themes for sale on our Event Espresso website and tying up valuable resources on that site. I created a very simple (bare-bones), standalone theme shop to promote the child themes and provide one-click theme updates. Since these are free child themes, I decided to set up a simple shopping cart system, using Easy Digital Downloads, which only took a matter of minutes to set up. I wrote about the process, on my blog, entitled: Bare-bones Guide to Launching a WordPress Theme Shop from Scratch

Comments, feedback, questions?

I hope you find this information useful and are inspired to develop child themes for Event Espresso. If you do, I hope that you find these child themes to be an excellent starting point and a useful guide in your endeavors.

I love hearing your ideas and thoughts regarding our services, so please feel free to send us an email or submit your own child theme to our directory.

If you have any questions, please let me know in the comments below.

 

Related Articles

Share a Reply or Comment

Your email address will not be published. Required fields are marked *

Need help with Event Espresso? Create a support post in our support forums

Do NOT follow this link or you will be banned from the site!
[gravityform id=116 title=false description=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_116' ><form method='post' enctype='multipart/form-data' id='gform_116' action='/2017/11/child-themes-now-available-for-event-espresso-4/'> <div class='gform_body'><ul id='gform_fields_116' class='gform_fields top_label form_sublabel_below description_below'><li id='field_116_5' class='gfield gfield_contains_required field_sublabel_hidden_label field_description_below gfield_visibility_visible' ><label class='gfield_label gfield_label_before_complex' >What is your first name?<span class='gfield_required'>*</span></label><div class='ginput_complex ginput_container no_prefix has_first_name no_middle_name no_last_name no_suffix gf_name_has_1 ginput_container_name' id='input_116_5'> <span id='input_116_5_3_container' class='name_first' > <input type='text' name='input_5.3' id='input_116_5_3' value='' aria-label='First name' aria-required="true" aria-invalid="false" placeholder='First name'/> <label for='input_116_5_3' class='hidden_sub_label screen-reader-text'>First name</label> </span> </div></li><li id='field_116_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_1' >What is your email address so we can follow up with you?<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_116_1' type='text' value='' class='medium' placeholder='hello@example.com' aria-required="true" aria-invalid="false" /></div></li><li id='field_116_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_2' >Tell us about your concerns below<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_textarea'><textarea name='input_2' id='input_116_2' class='textarea medium' placeholder='What kind of events are you planning?' aria-required="true" aria-invalid="false" rows='10' cols='50'></textarea></div></li><li id='field_116_6' class='gfield field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement</label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_116_6'><li class='gchoice_116_6_1'> <input name='input_6.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_116_6_1' /> <label for='choice_116_6_1' id='label_116_6_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_116_3' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_3' id='input_116_3' type='hidden' class='gform_hidden' aria-invalid="false" value='' /></li><li id='field_116_4' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_4' id='input_116_4' type='hidden' class='gform_hidden' aria-invalid="false" value='https://eventespresso.com/2017/11/child-themes-now-available-for-event-espresso-4/' /></li><li id='field_116_7' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_7' >Name</label><div class='ginput_container'><input name='input_7' id='input_116_7' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description__7'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_116' class='gform_button button' value='Send my message' onclick='if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} jQuery("#gform_116").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_116' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='116' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_116' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_116' id='gform_target_page_number_116' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_116' id='gform_source_page_number_116' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 116) {if(typeof Placeholders != 'undefined'){ Placeholders.enable(); }} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [116, 1]) } ); </script>