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 »
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 »
Next to the form to cancel all bookings for a person for one event, you can also cancel one payment. This is done by using e.g. #_CANCEL_URL in e.g. the RSVP mail when a booking is made. When a user clicks on the resulting link, he/she is sent towards a “cancel one payment” form. This
Cancel one payment form Read More »
When defining a membership, a huge amount of work will go into the definition of the mails being send when someone becomes a member, pays, expires, etc … These mails can contain placeholders to make your life easier and be able to reuse these for other membership definitions. For members, all the placeholders used for
Member placeholders Read More »
The membership form is called independently on a page via the shortcode [eme_add_member_form]. There is no default form, you need to define one by creating a template with any of the following placeholders. Warning: if the shortcodes #_LASTNAME, #_FIRSTNAME, #_EMAIL or #_SUBMIT are not present, the form is not valid and will not be shown.
Membership form formatting Read More »
People placeholders are placeholders you can use in emails to all EME people, rsvp info, attendee info etc (all things related to people). Below are all the possible placeholders, but to avoid clashing with placeholders from events, bookings, … you can (should) use “#_PERSON” in front of all related placeholders (so #_EMAIL can be #_PERSONEMAIL
People placeholders Read More »
This defines the layout of the list of categories shown when defining templates for use in the shortcode [eme_categories]. The placeholders mentioned below can be used: #_CATEGORYFIELD{xx} (with ‘xx’ being one of ‘category_id’, ‘category_name’, ‘description’ or ‘slug’) displays respectively the id, name, description or slug of the category. #_CATEGORYURLa link to the category, which will
This defines the layout of the calendar when using the shortcode [eme_calendar]. The standard placeholders for events AND the extra placeholders (in this case only conditional tags) mentioned below can be used: #_IS_START_DAY returns 1 if the calendar day corresponds to the start day of an event #_IS_END_DAY returns 1 if the calendar day corresponds
Calendar placeholders Read More »