Home › Forums › Calendar Products › Community Events › Limit Venues and Organizers
- This topic has 5 replies, 2 voices, and was last updated 11 years, 4 months ago by
Geoff.
-
AuthorPosts
-
December 2, 2014 at 1:46 pm #905545
avonnes
ParticipantIs there a way of limiting these two lists in the dropdown: “Use Saved Venue” and “Use Saved Organizer”? For unregistered users, the list soon will become too unwieldy. Also, how would I delete duplicate venues/organizers?
December 2, 2014 at 3:42 pm #905655Geoff
MemberHi there, Carolyn! Thanks for getting in touch. 🙂
Great question, but unfortuantely there’s no easy way to do this without triggering other issues from popping up. There is JavaScript in the plugin that controls Venue fields from hiding and showing those options and  would break if you were to remove the ‘Use New Venue’ or ‘Use New Organizer’ options.
If this is something you’d like to see in a future release, I would suggest submitting it as an idea on our UserVoice page. Our team periodically reviews the most popular ideas for possible inclusion in a future release of the plugin.
Sorry this probably isn’t the answer you were hoping for, but does it at least help answer your question? Please let me know. 🙂
Cheers!
GeoffDecember 2, 2014 at 7:09 pm #905825avonnes
ParticipantI’ve seen elsewhere in the forums about how someone could use CSS to hide a particular field. If so, this shouldn’t present any coding conflicts, right? What has been done previously when the list exceeds 100+ Venues? Also, can you point me to a link/post that deals with handling duplicates?
December 3, 2014 at 7:28 am #906242Geoff
MemberHello Carolyn! Thanks for following up 🙂
Absolutely, the CSS itself wouldn’t create a conflict with Javascript as far as I can tell. However, the options in the dropdown all share the same class, meaning hiding one of them would hide them all. I suppose one option might be to use pseudo classes to display the first element (e.g. :first-child) but then hide the rest.
The duplicate venues thing is interesting. Currently, if a visitor submits a venue with the exact same information as an existing venue, it will be accepted. That means the duplicated event would need to be removed manually on the back end. The largest number of venues I’ve seen in a working example is about 50, but the menu will certainly accommodate 100+ as well–the user can either scroll through it, or use the search bar at the top of the list.
Checking for duplicate event sounds like it would be a great feature. If you have a moment, it would be awesome if you shared it on our UserVoice page. We check there for new feature ideas to include in upcoming releases and I can see how that would be a useful one.
Cheers!
GeoffDecember 9, 2014 at 10:08 am #913161Geoff
MemberHey there, Carolyn! Just checking in to see if there’s been any further update or if you still need assistance on this one–let me know. 🙂
Cheers!
GeoffDecember 16, 2014 at 9:34 am #920014Geoff
MemberHi there, Carolyn! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to open a new thread. We’d be happy to help. 🙂
Cheers!
Geoff -
AuthorPosts
- The topic ‘Limit Venues and Organizers’ is closed to new replies.
