users creating event tags – no option for this when creating new event

hi,

you can modify template file at wp-content/plugins/events-manager/templates/forms/event-editor.php then add this snippet

<?php
$terms = get_terms(EM_TAXONOMY_TAG);
?>
<div class="event-tags">
<select name="newtag[]" multiple size="10">
	<?php foreach ($terms as $em_tag){ ?>
	<option value="<?php echo $em_tag->term_id; ?>"><?php echo $em_tag->name; ?></option>
	<?php } ?>
</select>
</div>

then hook into hook into the em_event_save filter – https://wp-events-plugin.com/tutorials/saving-custom-event-information/

Hi,

The code snippet you supplied just gives a list of previously created event tags. Ok, this I can probably change to just an input text field so that the user can insert any event tag text to the event.

But I got stuck when you say hook into the “em_event_save” filter, where do I do this? in events-manager.php? Also event tags comprise of several db tables “wp_terms”, “wp_terms_taxonomy” and “wwp_term_relationships”, and inserting tags related info into these table together, is a bit more complicated than the styles example in the online tutorial.
Amittedly I’m new to wordpress, and for the benefit of others that will surely in future encounter this issue can you please give a bit clearer instructions on how to allow users create their own event tags. I will surely be grateful man

… also isn’t the em_event_save filter only used for custom fields for events. however events tags are infact seperate database entities and exist seperate from events. Since they are more than just events meta information, they are taxonomy terms for events. I’ve checked out the source files, and theres seperate classes to deal with event taxonomy: em-tag.php and em-tag-taxonomy.php, but these only deal with retrieving taxonomy data, and not saving them

the reason this isn’t possible atm is because a seperate script needs to be written to save them. At the moment, WP handles the saving of the tags admin-side.

Something we’ll add eventually, but it’s in a line with other feature requests.