Author name: admin

Legacy syntax and deprecated placeholders

Reason In the past, there was an inconsistent behaviour when placeholders needed options: #_ATT{…}{…} #_TOTALPRICE… #_SUBMIT[…] and others This resulted also in some unwanted behaviour where square brackets of wordpress shortcodes were matched as possible options for placeholders. This has now been made consistent and the syntax for #_ATT{…}{…} is being taken as a reference. […]

Legacy syntax and deprecated placeholders Read More »

[eme_attendees]

Returns a list of attendees for a single event. Accepts the following arguments: id: the ID of the event you want to show the attendees for. See also the examples below. Either this option or the scope option is required to be present (see below). When using ths shortcode inside a single event format, the

[eme_attendees] Read More »

[eme_bookings]

[eme_bookings] Returns the page describing the bookings for a single event. Accepts the following arguments: id: the ID of the event you want to show the bookings for. See also the examples below. Either this option or the scope option is required to be present (see below). When using ths shortcode inside a single event

[eme_bookings] Read More »

[eme_location]

[eme_location] Returns the page describing a single location. Accepts the following arguments: id: the ID of the location you want show. template_id (optional): use a predefined format template for the location, instead of the setting configured in ‘Default single location page format’. See http://www.e-dynamics.be/wordpress/?cat=51 ignore_url (optional): allows you to ignore the external url for this

[eme_location] Read More »

Format templates

Format templates are just the same as what you would enter in the header, footer, events list or location list format settings in the general EME settings. But sometimes you want to define a different format for event or location listings, depending on the page you are. In this case you can use the old

Format templates Read More »

Multiseat events

Multiseat events are just like multiprice events. But where you create price categories (or price levels) with multiprice events, here you can define (if wanted) the maximum available seats per price category. This means that if you define multiseats, the number of seat “categories” must correspond with the number of price categories (even if the

Multiseat events Read More »

Multiprice events

If you want an event to have multiple prices (e.g. different prices for students, children, …), it’s as easy as entering a price in the “Add New Event” window in the EME admin pages.The value entered should just specify all prices, seperated by “||”. An example (see also screenshot) for an event having 3 prices:

Multiprice events Read More »

Attendees list

This defines the layout of the attendees list when using the placeholder #_ATTENDEES or when defining templates for use in the shortcode [eme_attendees]. The standard placeholders for events and people AND the extra placeholders mentioned below can be used: #_ATTENDSEATS displays the total amount of seats booked by the attendee for the relevant event. #_ATTENDSEATS{xx}

Attendees list Read More »

Scroll to Top