Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Possible to clone Event Post content | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Possible to clone Event Post content

Possible to clone Event Post content

Posted: August 7, 2013 at 8:00 am

Viewing 4 reply threads


Hugo Azzolini

August 7, 2013 at 8:00 am

Hi.

I am trying to set up EE for a Philharmonic Orchestra. Most of their events occur more than once. And their target demographic is the 55+ crowd, so ticket purchasing needs to be as simple as possible. As such, I am using the [ESPRESSO_CART_LINK] shortcode instead of the standard registration form so the user can add as many tickets to their cart as possible before filling out any forms.

I am using the Espresso Event custom post type to display the events on my ‘Events’ page: http://dppad.com/demo/orlandophil/?page_id=24

The issue that I am facing is two-fold:
1. I have a substantial amount of meta-data (being handled by the brilliant Advanced Custom Fields plugin) that is necessary for all of the needed info to be added to each post. Is it possible to clone the content for each subsequent recurring post?

If this is not, is there a simple method of displaying a single post that includes a list of all dates, times, and the [ESPRESSO_CART_LINK] for each subsequent recurring event in the series?

2. They offer a variety of subscription options, where the user would purchase a single a single ‘package’ that purchases tickets for multiple events. Is there a user-friendly way to link these events with the individual events, so that attendee counts are updated when the subscription package is purchased?

Thanks.


Sidney Harrell

  • Support Staff

August 7, 2013 at 1:45 pm

1. If, when you are creating the recurring events, you choose “Create a post”, then it will create a new post for each of the events in the recurrence series. It will use the templates/event_post.php file as a template, so you may be able to customize that file to use the meta-data from your Advanced Custom Fields plugin.
2. You can use a cart link shortcode to add multiple events with one click:

[ESPRESSO_CART_LINK event_id="15-16-17" direct_to_cart=1 moving_to_cart="Redirecting to cart..."]

would add events with ids 15, 16 and 17 to the cart.


Hugo Azzolini

August 8, 2013 at 6:35 am

Thanks for the quick reply!

Point 2 will work perfectly for ‘subscription’ packages, but since those packages are being sold at a discount, then we will have to create alternate (discounted) versions of each event and only offer access to them through the subscription packages.

Still wrestling with point 1. I’ll share if I find a workaround.


Sidney Harrell

  • Support Staff

August 8, 2013 at 1:28 pm

You could use the volume discounts add-on to discount the cart when over a certain number of tickets are sold at once.


Hugo Azzolini

August 8, 2013 at 1:32 pm

For this specific use case, I don’t think that will work: we are offering a concert series subscription package consisting of several events. We aren’t offering discounts when the user purchases a block of several tickets for a single event, but when they purchase 1 ticket to each event in the series.

Viewing 4 reply threads

The support post ‘Possible to clone Event Post content’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server