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
Conflicting Shortcode/Theme and adding custom field in EE4 | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Conflicting Shortcode/Theme and adding custom field in EE4

Conflicting Shortcode/Theme and adding custom field in EE4

Posted: February 18, 2014 at 3:58 am

Viewing 3 reply threads


Derrik van Bemmel

February 18, 2014 at 3:58 am

Yesterday we bought the new plugin. (ee4)

We have two problems with the plugin:

We can’t use the shortcode of esspresso in other pages of wordpress. (how can i do that)

How we can easily add standard fields to an event? Who can help me with this?

Greetz,

Vincent


Anonymous

February 18, 2014 at 5:48 am

Hi Derrik,

Which shortcode are you currently trying to use?

How we can easily add standard fields to an event? Who can help me with this?

I’m not sure what you mean here, can you explain a little more please?


Derrik van Bemmel

February 18, 2014 at 7:21 am

[EVENT_LIST] for a event list.

And

How can we add easily custom fields in the event template?


Josh

February 18, 2014 at 9:49 am

Hi Derrik,

It turns out that [EVENT_LIST] isn’t a valid Event Espresso 4 shortcode. Instead you can use [ESPRESSO_EVENTS] to list out events on a page.

I recommend using the Advanced Custom Fields plugin to add custom fields to your event editor. When you create the field group you’ll want to make sure you map a custom field to the Espresso Event custom post type. Then you can display the custom field values in your theme by following this guide:

http://www.advancedcustomfields.com/resources/getting-started/displaying-custom-field-values-in-your-theme/

It may not be necessary to add the custom field values directly to the theme. Event Espresso 4’s templates have several action hooks available in their templates to allow for adding additional content. For example, if you want to display the custom field values below the standard event information, you could use either of these action hooks:

AHEE_event_details_footer_top
AHEE_event_details_footer_bottom
Viewing 3 reply threads

The support post ‘Conflicting Shortcode/Theme and adding custom field in EE4’ 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.

The original Forum description...

Status: closed

Updated by Josh 11 years ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server