In case you don’t trust WP cron to process the queue, you can use a REST API call to do this. As an example, you can call: curl –insecure –user “username:password” https://localhost/wordpress/wp-json/events-made-easy/v1/processqueue/60 don’t user –insecure for public sites, and change “https://localhost/wordpress” by your wordpress url change the “username” by your user and the “password” by […]
Shortcode Using the shortcode [eme_add_event_form] you can create a frontend submit form to add new events. The main settings and basic template can be set in the regular EME settings. This shortcode has 2 optional parameters: an optional id-parameter (pointing to the id of a template), so you can use different layouts if you want.
[eme_person_memberinfo] Will show all membership info for the currently treated person for the mentioned membership, based on the layout given by the template. Accepts the following arguments: person_id: the id of the person to be shown. Can be #_PERSONID if used inside another shortcode (that then first replaces #_PERSONID with the required value and then
[eme_person_memberinfo] Read More »
As you know, WordPress allows you to hook into existing hooks/actions to extend functionality. The disadvantage here is that you need to modify your theme’s functions.php for this (or create a child theme and modify it there). EME now allows you to create separate PHP files in wp-content/uploads/events-made-easy/includes . If those files start with “eme_”
Adding EME extensions Read More »
[eme_mymemberinfo] Will show all membership info for the logged in user for the mentioned membership, based on the layout given by the template. Accepts the following arguments: template_id: use a predefined format template for the membership info, See format templates . membership_id: the ID of the membership for which to show membership info for. The
[eme_mymemberinfo] Read More »
[eme_edit_member_form] After entering a member id, a person with the needed rights can edit that member in the frontend (not the personal info, nor start/end date of the event, but only member-entered info concerning the membership which are in fact just custom fields) Example [eme_edit_member_form]
[eme_edit_member_form] Read More »
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
CSV import payments Read More »
[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_mymemberships] Read More »
[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_add_simple_multibooking_form Read More »