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
Using [SINGLEEVENT] shortcode in custom post type file | Event Espresso - Staging Server

Support

Home › Forums › Custom Files › Using [SINGLEEVENT] shortcode in custom post type file

Using [SINGLEEVENT] shortcode in custom post type file

Posted: July 16, 2012 at 11:13 am

Viewing 1 reply thread


Brad Ball

July 16, 2012 at 11:13 am

I am using do_shortcode(‘[SINGLEEVENT single_event_id=”my_identifier”]’); in my custom post type template. It is displaying correctly but I would like to know if there are any parameters I am able to pass to it? Like how you can pass parameters to the Venue short code to allow different items to show or not. My goal is to just display the Registration Form and nothing else. I am using the “Single Event” short code because the REG_EVENT_FORM short code always displays at the top of the page and I cannot control it.


Seth Shoultes

  • Support Staff

    •

July 16, 2012 at 11:31 am

I see what is happening with the output of the ESPRESSO_REG_FORM shortcode. We are not using output buffering in the espresso_reg_form_sc function. If you are experienced with PHP, you should be able to add that to the espresso_reg_form_sc function in the event-espresso/includes/shortcodes.php file.

I am going to add it right now, so the next update should include this change.
Viewing 1 reply thread

The support post ‘Using [SINGLEEVENT] shortcode in custom post type file’ 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.

Status: closed

Updated by Seth Shoultes 12 years, 6 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server