- This topic has 10 replies, 3 voices, and was last updated 10 years, 9 months ago by .
Viewing 11 posts - 1 through 11 (of 11 total)
Viewing 11 posts - 1 through 11 (of 11 total)
- The forum ‘How do I …’ is closed to new topics and replies.
Events Made Easy › Forums › How do I … › Frontend Category Restriction?
Tagged: frontend
Hello, is it possible to restrict the categories that users of the front-end form are allowed to select, and if so, can you please describe the process by which to create this restriction? Thank you!
What front-end form? The search form or the create-new-event form?
The create-new-event form that users submit from the front-end. I am wondering what the best way would be to restrict the categories they are able to choose as they are creating their event, before they submit it to us for review.
That’s not possible. That plugin (which is not my code btw) has (for now) no filtering also, so …
I’ll try to take a look at it this evening.
It would certainly be much appreciated 🙂 We use categories quite a bit, but not all of them are for the front-end users to choose from. I’ve been trying to come up with a solution, but so far no luck… I’ll keep testing too.
I created a filter emefs_categories_filter for the frontend, so you can filter out unwanted cats:
This sounds like it could be very useful for back-end also to restrict categories by user level. Would this be possible using the new filter?
Not really, since it’s a filter only for emefs. But I can add a similar filter if you want, although I don’t really see a big use for it 🙂
It’s similar to a previous feature request I made for a 2nd category/taxonomy.
In my instance, I assign a particular category as ‘recommended’ which should only be used by Editors.
I have many other custom roles that can publish events and it’s only good faith that stops them ‘recommending’ their own events.
This might be too specific to my own needs though so it’s up to you.
Thanks
Well, adding a filter is not that big a deal 🙂
I’ll move this to bugs, so I don’t forget about it (I forgot to do it yesterday evening, before the release).
Implemented here: