[eme_mytasks]

[eme_mytaskss]
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:

  • scope
  • template_id, template_id_header, template_id_footer (optional): use a predefined format template for the bookings list header, footer or list entry
  • task_id: the task where you want to show things for
  • event_id: the event od where you want to show things for

Example:
[eme_mytasks template_id=3 template_id_header=7 template_id_footer=9 scope='past']
[eme_mtyasks template_id=3 ]

Tasks (volunteers)

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 other settings for tasks (globally and/or per event):

  • the mails that will get send if someone signs up for a task, when some cancels his/her signup, when a signup is deleted by an admin
  • the form format
  • the setting “Allow overlap” and “require WP membership”
  • if you want reminders to be sent out (reminders are sent out at midnight): choose when the reminders are to be sent (in days before the task starts)

Once your settings are ok, you need to show the signup form. For this you can use the shortcode eme_tasks_signupform on a wordpress page (or inside a single event format, see the shortcode doc). For showing who signed up, you can use the shortcode eme_tasks_signups on a wordpress page (or inside a single event format, see the shortcode doc).

[eme_tasks_signups]

[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 options define – per event – the header (“template_id_header” option, shown above the task signups for that event, the entry (“template_id” option, repeated for each signup for tasks for that event, ordered per task and the tasks ordered as per their definition in the event) and the footer (“template_id_footer” option, shown below the task signups for that event). Since this shortcode can contain tasks for multiple events, these options are used to define the layout of the tasks per event and get repeated for each event.
    If template_id is not provided, a default setting will be used that can be set in the EME settings for tasks.
  • ignore_filter: if set to 1, the shortcode will ignore the eme filter form if present on the page. Defaults to 0. Using this you can use several shortcodes on 1 page and only some are optionally influenced by the eme_filterform shortcode.

See the doc concerning task and task signup placeholders for the placeholders you can use in the templates for this shortcode.

Example (shows the task signups for all future events):
[eme_tasks_signups]
Or, when using it inside a single event format, show the task signups for that event when viewing the event details with a custom template:
[eme_tasks_signups event_id=#_EVENTID template_id=3]
Or, when showing it for event with ID 12 with all custom templates:
[eme_tasks_signups event_id=12 template_id=3 template_id_header=7 template_id_footer=9]

[eme_tasks_signupform]

[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
  • template_id, template_id_header, template_id_footer (all optional). These options define – per event – the header (“template_id_header” option, shown above the tasks for that event, the entry (“template_id” option, repeated for each task for that event) and the footer (“template_id_footer” option, shown below the tasks for that event). Since this shortcode can contain tasks for multiple events, these options are used to define the layout of the tasks per event and get repeated for each event.
    If template_id is not provided, the default setting will be used (from the EME generic settings for tasks).

Next to these, also the following arguments can be used, just like for events (see the eme_events shortcode doc for the info on these):
scope , order , category , showperiod , author , contact_person , location_id , show_ongoing , notcategory , show_recurrent_events_once , ignore_filter

See the doc concerning task signup form placeholders for the placeholders you can use in the templates for this shortcode.

While the above info generates the form to choose which tasks someone wants to signup for, the part of the form where the person enters his name/email (and the submit button) is a generic option in the EME settings.

Example (shows the task form where people can select tasks for all future events):
[eme_tasks_signupform]
Or, when using it inside a single event format and a custom template:
[eme_tasks_signupform event_id=#_EVENTID template_id=3]
Or, when showing it for event with ID 12 and all custom templates:
[eme_tasks_signupform event_id=12 template_id=3 template_id_header=7 template_id_footer=9]

Tasks and task signup placeholders

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 mails can contain placeholders to make your life easier.

Task placeholders

When you want to visualize task info (either in a task signup form, in the task signup mails sent to a person or the online info on task signups), you can use all event placeholders and the following:

  • #_TASKNAME displays the name of the task
  • #_TASKID displays the ID of the task, this can e.g. be used in the shortcode eme_taskssignups (taskid=#_TASKID option) per task and use an extra template option if you ever want to change the layout of signups per event
  • #_TASKDESCRIPTION displays the task description
  • #_TASKSTARTDATE or #_TASKBEGIN returns the task start datetime
  • #_TASKENDDATE or #_TASKEND returns the task end datetime
  • #_TASKSPACES returns the total number of spaces defined for this task
  • #_FREETASKSPACES returns the number of free spaces for this task
  • #_USEDTASKSPACES returns the number of used spaces for this task
  • #_TASKSIGNUPS returns a simple list of signups for this task. The layout can be changed in the EME settings. You can also use [ eme_taskssignups taskid=#_TASKID] per task and use an extra template option if you ever want to change the layout of signups per event.
  • #_USER_IS_REGISTERED returns 1 if the current logged in user is registerd for this task, 0 otherwise

Signup placeholders

For task signups, all the placeholders used for people and tasks (see above) can be used. Next to those, you can use the following 2 placeholders in a mail so people can cancel a task signup:

  • #_TASKSIGNUPCANCEL_URL returns a url to cancel the signup for this task. This can be used to create your own clickable links
  • #_TASKSIGNUPCANCEL_LINK returns a clickable link to cancel the signup for this task

Payment gateway placeholders

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 extra cost for the payment gateway being mentioned (in the payment forms) or the payment gateway used (after payment, for a member or booking). If possible, the price is localized according to your preferences (so including currency symbol).
  • #_EXTRACHARGE_NO_VAT the extra cost without VAT (the VAT percentage is taken from the relevant event or membership). If possible, the price is localized according to your preferences (so including currency symbol).
  • #_EXTRACHARGE_VAT_ONLY the total VAT on the extra charge (the VAT percentage is taken from the relevant event or membership). If possible, the price is localized according to your preferences (so including currency symbol).
  • #_PRICE_INCLUDING_CHARGES indicates the total cost (including extra charges for that payment gateway) for a booking or membership for the payment gateway being mentioned (in the payment forms) or the payment gateway used (after payment, for a member or booking). If possible, the price is localized according to your preferences (so including currency symbol).
  • #_PRICE_INCLUDING_CHARGES_NO_VAT the total price without VAT (the VAT percentage is taken from the relevant event or membership). If possible, the price is localized according to your preferences (so including currency symbol).
  • #_PRICE_INCLUDING_CHARGES_VAT-ONLY the total VAT (the VAT percentage is taken from the relevant event or membership). If possible, the price is localized according to your preferences (so including currency symbol).
  • #_CURRENCY the relevant currency used
  • #_CURRENCYSYMBOL the relevant currency symbol

[eme_person]

[eme_person]
Returns info of a person (or the person linked to the current logged in user if person_id is not provided). Accepts the following arguments:

  • person_id: the ID of the EME person you want to show the info of. If not provided, the person linked to the current logged in user is used (if existing)
  • template_id (required): The template used to show the info on this person. See https://www.e-dynamics.be/wordpress/category/documentation/7-placeholders/7-12-people/ for the placeholders that can be used here.

The parameter person_id can be overriden via a url param (using the person’s random id). This allows to create 1 page where you can show other people’s info based on their random id (so not easy to guess) from e.g. within an event. The url parameter name is “prid”. The placeholder to get the random id for a person (contact or author) for an event is documented in the event/people placeholders. Example: this_page/?prid=#_CONTACTRANDOMID.

Language support

EME by default supports multiple languages for the backend (typically called the “plugin” language, which follows the wordpress language). However, in the case some kind of language plugin is installed to help your site be multi-lingual, things become more difficult. Reason is that the RSVP form, mail templates, event titles, etc … all need to support your languages of choice.
EME tries to detect the used language by checking the url. It supports “https://my.site/?lang=en” format or “https://my.site/en/” format.
When wanting to support multiple languages, EME works very nicely together with qtranslate-xt. But if you’re using another plugin for languages, EME can still help you. You just need to use language tags to indicate the language for a specific part of text. An example for an event title:
[:en]title in english[:de]title in German[:nl]title in Dutch[:]
Or for content of an event (or mail), as an example with sections that are not translated (like a name):

[:en]Hi[:nl]Hallo[:] #_FIRSTNAME,
[:en]Thank you for reserving for[:nl]Bedankt voor uw reservatie voor[:] #_EVENTNAME

When the language is English, this then gets presented as:
Hi #_FIRSTNAME,
Thank you for reserving for #_EVENTNAME

And in Dutch:
Hallo #_FIRSTNAME,
Bedankt voor uw reservatie voor #_EVENTNAME

If a section of text is not enclosed between language tags, it is used in all languages. If no language is detected, or the language of choice is not present in the text, the first language found is used as a “default”.

EME supports both the language tags [:xx]…[:] and {:xx}….{:} (both of which are also used by qtranslate-xt).

EME also follows the language of choice when sending mails to people (as indicated in their EME profile, not WP).