[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 […]
[eme_tasks_signupform] Read More »
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
Task signup form placeholders Read More »
When defining a task, a huge amount of work goes 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
Tasks and task signup placeholders Read More »
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
Payment gateway placeholders Read More »
[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)
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
Using the EME backend, you can send emails to groups of people. However, there’s now also the option of doing this via your favorite mail client, via a commandline script that EME provides (called “cli_mail.php”). For this to work, you need to be able to pipe emails to scripts, and below I’ll explain how it
Send mail to group via script Read More »
[eme_bookings_report_link] If the user is logged in and has the permissions to list members, this shortcode generates a link to a CSV export for the members of the configured group or membership. It accepts the following parameters: event_id event id you want to show the bookings for (required). If this shortcode is used inside a
[eme_bookings_report_link] Read More »
[eme_members_report_link] If the user is logged in and has the permissions to list members, this shortcode generates a link to a CSV export for the members of the configured group or membership. It accepts the following parameters: membership_id membership id you want to show the members for. Either this or group_id is required. group_id id
[eme_members_report_link] Read More »
There are a number of generic placeholders, which can be used everywhere/always (even outside events/locations, if you’d use the eme_if shortcode standalone on a page). These are: #_IS_USER_IN_GROUP{xxx} returns ‘1’if the logged in WP user is in the EME group called ‘xxx’, ‘0’ otherwise. Multiple groups can be specified, separated by “,”. #_IS_USER_MEMBER_OF{xxx} returns ‘1’if
Generic placeholders Read More »