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 Simple event listing | Event Espresso - Staging Server
I assume you want this information to be in the event list?
If so, the the answer is yes and no. It can be done but requires some fiddling as Event Espresso is designed to display events rather than informational posts.
You would need to set the “Display registration form? ” option in the event editor to No. This would disable the registration form.
After that you would need to add some CSS that specifically targets that event to hide the payment and ticketing information.
Something like this might work, but no doubt you will need to tweak it a bit
/* replace 19 with the event ID number */
/* this will hide the meta data on the event list*/
#event_data-19 .event-meta {
display:none;
}
/*this will hide the attendance on the single reg page */
#espresso-event-id-19 p.section-title {
display:none;
}
I did have to setup a datetime and a ticket for the second event but besides that the test information looked okay.
The display registration form was temporarily removed from EE4. It will be reintroduced very soon.
For now, you can use CSS to target the ticket selector:
.event-tickets{display:none}
—
Lorenzo
Viewing 3 reply threads
The support post ‘Simple event listing’ 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.