Importing payments into EME is done by using a CSV file. The csv delimiter and enclosure can be specified during import. If the delimiter value is empty, then “,” (comma) is taken as value. If the enclosure value is empty, then ‘”‘ (double quotes) is taken as value. The first line should indicate the names …
[eme_mymemberships] Will show all memberships for the logged in user, based on the layout given by the templates. Accepts the following arguments: template_id, template_id_header, template_id_footer (at least template_id is required, otherwise nothing will be rendered): use a predefined format template for the memberships list header, footer or list entry, See format templates . Because the …
[eme_mytasks] Will show all signed up tasks for the logged in user, based on the layout given by the templates or by the generic booking list format. Accepts the following arguments: scopelimit tasks to events with mentioned scope. Default value: “future”, other values: “past” or “all” template_id, template_id_header, template_id_footer (optional): use a predefined format template …
This shortcode is a shorter way to calling eme_add_multibooking_form with the option simple=1 by default. See https://www.e-dynamics.be/wordpress/eme_add_multibooking_form/ for all other options (except the simple=1 option)
EME can help you manage volunteers by defining tasks for an event. To activate tasks, go in the EME settings, tab “General” and activate the option “Use tasks”. After that, you can define tasks per event in a separate tab, like the RSVP definition. Once you have defined your tasks for an event, check the …
[eme_tasks_signups] Returns a list of signups for event tasks. Accepts the following arguments: event_id: the ID of the event you want to show the bookings for. If not present, all future events with tasks activated will be chosen. The events matching this shortcode also get influenced by the [eme_filterform] shortcode template_id, template_id_header, template_id_footer (optional). These …
[eme_tasks_signupform] Returns a form where people can signup for event tasks. Accepts the following arguments: event_id: the ID of the event you want to show the bookings for. If not present, all future events with tasks activated will be chosen. The events matching this shortcode also get influenced by the [eme_filterform] shortcode. If your event …
The task signup form consists of 2 parts: – a per-event entry for the tasks with a checkbox to indicate which tasks you want to use – a section with the form asking for lastname/firstname/email. For the per-event entries, the shortcode eme_tasks_signupform provides the option “template_id” (or a generic EME setting), which in fact is …
When defining a task, a huge amount of work can go into the definition/layout of the task signup form and the mails being send when someone signs up for a task, cancels a signup or the signup gets deleted. EME provides you with simple defaults, which you can either adapt globally or per event. These …
When showing the payment form, you can use certain placeholders to indicate info on a payment gateway (like the extra cost for that gateway). These placeholders can also be used in made bookings or members (so you can show info on the payment gateway used in mails sent after payment for example). #_EXTRACHARGE indicates the …