\n\n\n\n
Customizing required event fields<\/h2>\n\n\n\n
You can specify event fields for requirement by using this filter:<\/p>\n\n\n\n
- \n
- tribe_events_community_required_fields<\/kbd><\/li>\n<\/ul>\n\n\n\n
To make the Event URL field required for submission, for example, you could add the following snippet of code to your site:<\/p>\n\n\n
\nadd_filter( 'tribe_events_community_required_fields', 'my_community_required_fields', 10, 1 );\n\nfunction my_community_required_fields( $fields ) {\n\n if ( ! is_array( $fields ) ) {\n return $fields;\n }\n\n $fields[] = 'EventURL';\n\n return $fields;\n}\n<\/pre><\/div>\n\n\nThe
(required)<\/code> label should automatically be added after the field label, if the field is required.<\/p>\n\n\n\nYou can see a full list of the default fields<\/a> below. It’s worth mentioning that there are also two “shortcut” fields you can specify for the tribe_events_community_required_fields<\/kbd> filter:<\/p>\n\n\n\n
- \n
- venue<\/kbd><\/li>\n\n\n\n
- organizer<\/kbd><\/li>\n<\/ul>\n\n\n\n
\u261d\ufe0f These two shortcuts make the entire venue section or organizer section required, respectively. If either is added via the tribe_events_community_required_fields<\/kbd> filter, then the user has to pick an existing venue or organizer option or<\/strong> create a new one\u2014the venue or organizer can’t be left.<\/p>\n\n\n\n
\n\n\n\nCustomizing required venue fields<\/h2>\n\n\n\n
You can specify venue fields for requirement by using this filter:<\/p>\n\n\n\n
- \n
- tribe_events_community_required_venue_fields<\/kbd><\/li>\n<\/ul>\n\n\n\n
To make the venue URL and phone number required, for example, you could write the following snippet:<\/p>\n\n\n
\nadd_filter( 'tribe_events_community_required_venue_fields', 'my_venue_community_required_fields' );\n\nfunction my_venue_community_required_fields( $fields ) {\n \n if ( ! is_array( $fields ) ) {\n return $fields;\n }\n\n $fields[] = 'Phone';\n $fields[] = 'URL';\n\n return $fields;\n}\n<\/pre><\/div>\n\n\nIn order for the above snippet to work, it is necessary to also require the venue field itself. You can do that with the following snippet:<\/p>\n\n\n
\nadd_filter( 'tribe_events_community_required_fields', 'my_community_required_fields' );\n \nfunction my_community_required_fields( $fields ) {\n \n if ( ! is_array( $fields ) ) {\n return $fields;\n }\n \n $fields[] = 'venue';\n \n return $fields;\n}\n<\/pre><\/div>\n\n\nYou can see a full list of the default fields<\/a> below.<\/p>\n\n\n\n
\n\n\n\nCustomizing required organizer fields<\/h2>\n\n\n\n
You can specify organizer fields for requirement by using this filter:<\/p>\n\n\n\n
- \n
- tribe_events_community_required_organizer_fields<\/kbd><\/li>\n<\/ul>\n\n\n\n
To make the organizer email address required, for example, you could write the following snippet:<\/p>\n\n\n
\nadd_filter( 'tribe_events_community_required_organizer_fields', 'my_organizer_community_required_fields' );\n\nfunction my_organizer_community_required_fields( $fields ) {\n \n if ( ! is_array( $fields ) ) {\n return $fields;\n }\n\n $fields[] = 'Email';\n\n return $fields;\n} \n<\/pre><\/div>\n\n\nIn order for the above snippet to work, it is necessary to also require the organize field itself. You can do that with the following snippet:<\/p>\n\n\n
\nadd_filter( 'tribe_events_community_required_fields', 'my_community_required_fields' );\n \nfunction my_community_required_fields( $fields ) {\n \n if ( ! is_array( $fields ) ) {\n return $fields;\n }\n \n $fields[] = 'organizer';\n \n return $fields;\n}\n<\/pre><\/div>\n\n\nYou can see a full list of the default fields<\/a> below.<\/p>\n\n\n\n
\n\n\n\nCustomizing the “(required)” label<\/h2>\n\n\n\n
Customizing the label is also possible through a filter. See the below example, which changes the label to “must be filled”.<\/p>\n\n\n
\nadd_filter( 'tribe_community_required_field_marker', 'tec_ce_custom_required_label', 10, 2 );\n\nfunction tec_ce_custom_required_label ( $html, $field ) {\n\t$html = ' <span class="req">' . '(must be filled)' . '<\/span>';\n\n\treturn $html;\n}\n<\/pre><\/div>\n\n\nIt is possible to customize the label for certain fields only. For that you can use the
$field<\/code> parameter that is being passed.<\/p>\n\n\n\nCustomizing submission error messages<\/h2>\n\n\n\n
Following this guide<\/a>, you can add, remove, or modify Community Events submission form errors.<\/p>\n\n\n\n
\n\n\n\nCustomizing required additional fields<\/h2>\n\n\n\n
If you are using Events Calendar Pro<\/strong> along with The Events Calendar, then you can make use of the Additional Fields<\/a> feature to collect extra information for Events.<\/p>\n\n\n\n
You can make any additional field a required field by using the following example snippet.
Note: you will need to get the names (e.g._ecp_custom_2<\/code>) of the fields after setting them up and change them in the code.<\/p>\n\n\n\nadd_filter( 'tribe_events_community_required_fields', 'my_community_required_fields' );\n\nfunction my_community_required_fields( $fields ) {\n if ( ! is_array( $fields ) ) {\n return $fields;\n }\n $fields[] = '_ecp_custom_2'; \/\/ this is the field name for the input you want to require\n $fields[] = '_ecp_custom_3'; \/\/ this is another input you wish to require\n return $fields;\n}\n<\/pre><\/div>\n\n\nThe “required” label will not show up automatically for Additional Fields. You can fix that with the following sample snippet:<\/p>\n\n\n
\nadd_filter( 'tribe_community_events_field_label_text', 'tec_additional_fields_required_labels', 10, 2 );\n\nfunction tec_additional_fields_required_labels( $text, $field ) {\n \/\/ Bail, if it's not the Additional Field.\n\tif ( ! strstr( $field, '_ecp_custom_2' ) ) {\n\t\treturn $text;\n\t}\n\n \/\/ Add the "required" label.\n\treturn $text . ' <span class="req">(required)<\/span>';\n}\n<\/pre><\/div>\n\n\nThe last step is to add the snippet that includes the custom field in the list of allowed fields.<\/p>\n\n\n
\nadd_filter( 'tec_events_community_allowed_fields', 'my_community_allowed_fields' );\n \nfunction my_community_allowed_fields( $fields ) {\n if ( ! is_array( $fields ) ) {\n return $fields;\n }\n $fields[] = '_ecp_custom_2';\n return $fields;\n}\n<\/pre><\/div>\n\n\n<\/p>\n\n\n\n
\u261d\ufe0f Note: Make sure to change _ecp_custom_2 <\/strong>to a field that you are using on your submission form. You can find it by inspecting your site in the browser console and searching for _ecp_custom_<\/strong>.<\/p>\n\n\n\n
<\/p>\n\n\n\n
![\"\"](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2019\/10\/ECP-custom-1-1024x193.png\")
<\/figure>\n\n\n\n
\n\n\n\nDefault field names (case sensitive)<\/h2>\n\n\n\n
These are all of the default<\/strong> Community Events submission form fields, which can be used in the filters discussed above. Please note that these field names are case-sensitive<\/strong>.<\/p>\n\n\n\n
Default Event Fields<\/h4>\n\n\n\n
- \n
- post_content<\/kbd><\/li>\n\n\n\n
- event_image<\/kbd><\/li>\n\n\n\n
- EventStartDate<\/kbd><\/li>\n\n\n\n
- EventStartHour<\/kbd><\/li>\n\n\n\n
- EventStartMinute<\/kbd><\/li>\n\n\n\n
- EventStartMeridian<\/kbd><\/li>\n\n\n\n
- EventEndDate<\/kbd><\/li>\n\n\n\n
- EventEndMinute<\/kbd><\/li>\n\n\n\n
- EventEndHour<\/kbd><\/li>\n\n\n\n
- EventEndMeridian<\/kbd><\/li>\n\n\n\n
- is_recurring<\/kbd><\/li>\n\n\n\n
- EventCurrencySymbol<\/kbd><\/li>\n\n\n\n
- tax_input.tribe_events_cat<\/kbd> (for event categories)<\/em><\/li>\n\n\n\n
- venue<\/kbd><\/li>\n\n\n\n
- organizer<\/kbd><\/li>\n\n\n\n
- EventShowMapLink<\/kbd><\/li>\n\n\n\n
- EventURL<\/kbd><\/li>\n<\/ul>\n\n\n\n
? Quick Tip:<\/strong> If you are using Events Calendar Pro custom fields on the form, then you can even specify these fields as required. Just view the HTML source and find the correct
<input><\/code> tag, and look for the “name” attribute (screenshot<\/a>) to specify in your array of required fields.<\/p>\n\n\n\nDefault Venue Fields<\/h3>\n\n\n\n
- \n
- Venue<\/kbd> (the Venue Name)<\/em><\/li>\n\n\n\n
- Address<\/kbd><\/li>\n\n\n\n
- City<\/kbd><\/li>\n\n\n\n
- Province<\/kbd><\/li>\n\n\n\n
- State<\/kbd><\/li>\n\n\n\n
- Zip<\/kbd><\/li>\n\n\n\n
- Phone<\/kbd><\/li>\n\n\n\n
- URL<\/kbd><\/li>\n<\/ul>\n\n\n\n
Default Organizer Fields<\/h3>\n\n\n\n
- Address<\/kbd><\/li>\n\n\n\n
- event_image<\/kbd><\/li>\n\n\n\n
- post_content<\/kbd><\/li>\n\n\n\n
- tribe_events_community_required_organizer_fields<\/kbd><\/li>\n<\/ul>\n\n\n\n
- organizer<\/kbd><\/li>\n<\/ul>\n\n\n\n
- venue<\/kbd><\/li>\n\n\n\n