The placeholder #_BOOKINGS gets replaced with a list of bookings for an event and the layout of that list is configured in the settings “Bookings list header”, “Bookings list” and “Bookings list footer”. These 3 settings and the shortcode [eme_bookings] can then use specific placeholders to show the info you want the way you want […]
The registration form is called inside a single event by using the placeholder #_ADDBOOKINGFORM (or alike) or independently on a page via the shortcode [eme_add_booking_form] or the shortcode eme_add_multibooking_form. The registration form can be completely customized. You can define any number of fields in the “Events => Form fields” page, then go to the “Events
Registration form formatting Read More »
[eme_countdown] Returns the number of days until the next event or the event specified. Accepts the following optional argument: id: the ID of the event for which you want the countdown to happen. If not specified: count down until the first future event. Example: [eme_countdown id=25] Word of warning: this actually only shows the full-day
[eme_locations] Inserts a list of locations. Accepts the following arguments: eventful: if set to true, only locations with events planned will be shown. Default: false. scope: see the explanation for [eme_events]. You need to set eventful to true for this to have any effect. Default: all. category: see the explanation for [eme_events]. If eventful=true as
EME provides a number of hooks and filters so you can customize a number of things to your liking. For a howto in general about hooks and filters, see here for actions and here for filters. Below is a list of all possible hooks and filters (with a number of examples) that you can use
EME provides the use of conditional tags and for-loops. Conditional tags Sometimes you want info only to be shown dependent on some conditions. In almost all formatting settings, you can use a special shortcode called [eme_if] that allows these kind of decisions: You can use all placeholders in the if-part, just by prepending them with
Conditional tags and for-loops Read More »
Locations format works in the same way as events, but the parameters are different. #_LOCATIONDBFIELD{xx} displays the database value of the location property called ‘xx’ (with ‘xx’ being ‘location_name’, ‘location_id’, etc … see eme_locations.php, function eme_new_location) This can replace a number of more specific placeholders below (and future placeholders can be avoided like this too)
Location formatting Read More »
Hint: for time-based or location placeholders related to the event, scroll to the bottom of this page. The syntax of events format is quite simple. Basically, just write your html code in the usual way. Then you can add a number of placeholders corresponding to the data of the event. Some of them are: #_EVENTDBFIELD{xx}
This defines the layout of the event list or calendar filtering form when using the shortcode [eme_filterform]. The following placeholders can be used: #_FILTER_CATS shows a dropdown selection of categories #_EVENTFUL_FILTER_CATS shows a dropdown selection of eventful categories #_FILTER_CATS{xx} or #_EVENTFUL_FILTER_CATS{xx} shows a dropdown selection of (eventul) categories with between braces the text you want
Filter form formatting Read More »
If you enable RSVP email notifications, the contact person and respondent will be notified of the booking. The templates can be customised using the standard placeholders for events, locations, payment gateways and people AND the extra placeholders mentioned below. The extra placeholders: #_BOOKINGDBFIELD{xx} displays the database value of the booking property called ‘xx’ (with ‘xx’
RSVP mail and booking info Read More »