New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | A simple plugin that displays a form to allow people to enter events for the Events Made Easy plugin on a regular wordpress page. | You have to log in to add a translation. | Details |
Original untranslated
A simple plugin that displays a form to allow people to enter events for the Events Made Easy plugin on a regular wordpress page.
You have to log in to edit this translation. |
|||
| ↑ | Events Made Easy Frontend Submit | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Get The Events Made Easy plugin:↵ https://github.com/liedekef/events-made-easy/releases | You have to log in to add a translation. | Details | |
Original untranslated
Get The Events Made Easy plugin:↵
https://github.com/liedekef/events-made-easy/releases
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| A simple plugin that displays a form to allow people to enter events for the Events Made Easy plugin on a regular wordpress page.↵ Deprecation notice: this is the last release of the plugin, all functionality has been integrated in the main plugin.↵ This plugin will be discontinued. | You have to log in to add a translation. | Details | |
Original untranslated
A simple plugin that displays a form to allow people to enter events for the Events Made Easy plugin on a regular wordpress page.↵
Deprecation notice: this is the last release of the plugin, all functionality has been integrated in the main plugin.↵
This plugin will be discontinued.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Ensure the Events Made Easy plugin is installed and configured - https://github.com/liedekef/events-made-easy/releases | You have to log in to add a translation. | Details | |
Original untranslated
Ensure the Events Made Easy plugin is installed and configured - https://github.com/liedekef/events-made-easy/releases
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| If you want to use a default value for certain attributes or properties, you can use a third parameter for EMEFS::field, EMEFS::attribute and EMEFS::property.↵ E.g. EMEFS::property('event_single_event_format_tpl','hidden',"value=2");↵ This third parameter can also be used to add custom styles etc ...:↵ E.g. EMEFS::property('event_single_event_format_tpl','hidden',"value=2 class='my_class'"); | You have to log in to add a translation. | Details | |
Original untranslated
If you want to use a default value for certain attributes or properties, you can use a third parameter for EMEFS::field, EMEFS::attribute and EMEFS::property.↵
E.g. EMEFS::property('event_single_event_format_tpl','hidden',"value=2");↵
This third parameter can also be used to add custom styles etc ...:↵
E.g. EMEFS::property('event_single_event_format_tpl','hidden',"value=2 class='my_class'");
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Default values and extra classes | You have to log in to add a translation. | Details | |
Original untranslated
Default values and extra classes
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Which field types are supported? | You have to log in to add a translation. | Details | |
Original untranslated
Which field types are supported?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Action emefs_submit_event_action: this allows a custom action after event submit (like emailing the info to people).↵ (see the action eme_insert_event_action in the main EME plugin as an example).↵ Filter emefs_categories_filter: to filter the categories, see also eme_categories_filter↵ Filter emefs_event_insert_filter: executed just before insert of the new event in the database (so you can change certain properties by default). See also eme_insert_event_filter↵ Filter emefs_success_url: takes the current success page as parameter and needs to return a new url. This allows you to change the success page per submitted event | You have to log in to add a translation. | Details | |
Original untranslated
Action emefs_submit_event_action: this allows a custom action after event submit (like emailing the info to people).↵
(see the action eme_insert_event_action in the main EME plugin as an example).↵
Filter emefs_categories_filter: to filter the categories, see also eme_categories_filter↵
Filter emefs_event_insert_filter: executed just before insert of the new event in the database (so you can change certain properties by default). See also eme_insert_event_filter↵
Filter emefs_success_url: takes the current success page as parameter and needs to return a new url. This allows you to change the success page per submitted event
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| form.php which controls the html form. The default version can be found in the templates subdir.↵ If you want to change the layout (the default most probably won't suit you), copy this file in e.g. WP UPLOAD DIR/events-made-easy-frontend-submit/ and change the content there.↵ Don't change the default file in the templates subdir, it will get overwritten upon the next plugin update. | You have to log in to add a translation. | Details | |
Original untranslated
form.php which controls the html form. The default version can be found in the templates subdir.↵
If you want to change the layout (the default most probably won't suit you), copy this file in e.g. WP UPLOAD DIR/events-made-easy-frontend-submit/ and change the content there.↵
Don't change the default file in the templates subdir, it will get overwritten upon the next plugin update.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| For all possible fields, look at eme_events.php, function eme_new_event.↵ If you activated the option to use the captcha, you can (must) also use the field 'captcha'↵ If you activated the option to use Google reCAPTCHA, you can (must) also use the field 'recaptcha'↵ If you activated the option to use hCaptcha, you can (must) also use the field 'hcaptcha' | You have to log in to add a translation. | Details | |
Original untranslated
For all possible fields, look at eme_events.php, function eme_new_event.↵
If you activated the option to use the captcha, you can (must) also use the field 'captcha'↵
If you activated the option to use Google reCAPTCHA, you can (must) also use the field 'recaptcha'↵
If you activated the option to use hCaptcha, you can (must) also use the field 'hcaptcha'
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Filters and actions | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| If you have defined custom fields of type Events or Locations in EME, they are part of the event or location definition.↵ In that case, you can also ask in the frontend for that info, by using EMEFS::custom_field('xxx'). 'xxx' can be the id or the fieldname.↵ Example (under the assumption 'my_price' is a custom event or location field): ↵ Example (under the assumption '15' is a custom event or location field): ↵ Example (under the assumption '15' is a custom event or location field): | You have to log in to add a translation. | Details | |
Original untranslated
If you have defined custom fields of type Events or Locations in EME, they are part of the event or location definition.↵
In that case, you can also ask in the frontend for that info, by using EMEFS::custom_field('xxx'). 'xxx' can be the id or the fieldname.↵
Example (under the assumption 'my_price' is a custom event or location field): ↵
Example (under the assumption '15' is a custom event or location field): ↵
Example (under the assumption '15' is a custom event or location field):
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| How about custom event or location fields? | You have to log in to add a translation. | Details | |
Original untranslated
How about custom event or location fields?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| As shown in the templates examples, you call EMEFS::field('xxx') with 'xxx' being one of:↵ event_name↵ event_status↵ event_category_ids↵ event_start_date↵ event_start_time↵ event_end_date↵ event_end_time↵ event_notes↵ event_contactperson_email_body↵ event_respondent_email_body↵ event_url↵ event_rsvp↵ registration_requires_approval↵ registration_wp_users_only↵ event_image_url↵ event_seats↵ price↵ location_name↵ location_description↵ location_address1↵ location_address2↵ location_city↵ location_state↵ location_zip↵ location_country↵ location_latitude↵ location_longitude | You have to log in to add a translation. | Details | |
Original untranslated
As shown in the templates examples, you call EMEFS::field('xxx') with 'xxx' being one of:↵
event_name↵
event_status↵
event_category_ids↵
event_start_date↵
event_start_time↵
event_end_date↵
event_end_time↵
event_notes↵
event_contactperson_email_body↵
event_respondent_email_body↵
event_url↵
event_rsvp↵
registration_requires_approval↵
registration_wp_users_only↵
event_image_url↵
event_seats↵
price↵
location_name↵
location_description↵
location_address1↵
location_address2↵
location_city↵
location_state↵
location_zip↵
location_country↵
location_latitude↵
location_longitude
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.