Plugin Author
Franky
(@liedekef)
weird, it seems my reply didn’t make it in but the status got set to resolved …
Anyway: the placeholders (not shortcodes) you need to use are event placeholders (not frontend form placeholders). See https://www.e-dynamics.be/wordpress/eme-docs/event-formatting/
I do not fully understand, how the content of the frontend submit fields lands in the emails:
This one works for example:
#_FIELD{event_name} in the form has to be addressed with _EVENTNAME in the email template.
I also found all the others, but one I cannot find :
<div class=”input”>#_FIELD{event_contactperson_email_body}{textarea}</div>
Plugin Author
Franky
(@liedekef)
Well, I never imagined people using frontend submit combined with mails, so in fact not every event/location property was accessible using placeholders (an old oversight apparently). This fixes that:
https://github.com/liedekef/events-made-easy/commit/e997b26d7ca57ea9f448d0a1f921df95945d5ae0
Using that changeset, you can use #_PROP{xxx} to access custom event/location properties (identical to #_ATT). For a list of all event/location properties, see the function “eme_init_event_props” in eme_events.php or the function “eme_init_location_props” in eme_locations.php (almost at the top).
Concerning event_contactperson_email_body : that happens to be *not* a property (I was correcting code while writing this post), but can be accessed using #_EVENTDBFIELD{xx} , which in fact allows to access the value of any event column in the DB (I did that so as not to create a placeholder for every field …)
Isn’t “Frontend Submit” combined with email a useful combination (one that probably everyone who uses the plugin takes advantage of)?
Why else would you fill out the “Notification Email for Frontend Event Submission” field?
Also, I’m a little confused about the terms:
When are they attributes (#_ATT), when properties (#_PROP{xxx}) and when are they placeholders?
Or are they all the same?
“Shortcodes” is something else, I already understand that.
-
This reply was modified 3 days, 2 hours ago by
webmark487.
Plugin Author
Franky
(@liedekef)
The email-section was written later on, that’s why 😉
Concerning terminology: placeholders is the generic English term to replace something (a placeholder) by something else (value of some sort). In EME the placeholders start with “#_” (most of the time) to be able to correctly find/replace them. The #_ATT placeholders are for event attributes (see the Attributes-section when defining an event). The #_PROP placeholders are for events properties which don’t have own database columns (to avoid needing to create specific placeholders for each, which would cause the code to explode even more). And then there are the old regular placeholders for convenience.
