Ticket Fees and slug flexability

[Chris]

It would be great if the person listing the event could choose if they absorb the fees or not for an event at a ‘per vendor’ level.

It would also be great to have a vendor slug for each community user, you could turn this on or off, guessing off by default for backward compatability.

eg:

Bob The Builder is selling tickets to his singing show:

http://communitytickets.com/bob-the-builder/
http://communitytickets.com/bob-the-builder/my-singing-show/
http://communitytickets.com/bob-the-builder/my-singing-tour/10-july-2012-10-00/

Would also be great if you could have some other permalink control also.

1) Instead of defaulting to a date, also allow a sequence number, or a template:

http://communitytickets.com/bob-the-builder/my-singing-tour/2/ (for second re-occurring item in that event series)

so in admin:

permalink : /%events-slug%/%community-slug%/%community-user%/%event-name%/%sequence%/

or for date

permalink textfield : /%events-slug%/%community-slug%/%community-user%/%event-name%/%sequence%/

and date time:

permalink text field : /%events-slug%/%community-slug%/%community-user%/%event-name%/%event-date%/%event-time%/

It would be great to have better control over the slug (or url) generally as we are looking at url-rewriting to remove the /event/community (as it’s way too long)…. events are events… no-one cares who entered them from the front end, so why have a different url for events entered by admin or community??

Just give us full control of /events slug upwards by putting that reference in a variable instead of hard coding.

[Geoff B.]

Good evening Chris and welcome back!

Thank you for reaching out to us and sharing your ideas with us.
I would love to help you with these suggestions.

It would be great if the person listing the event could choose if they absorb the fees or not for an event at a ‘per vendor’ level.

I can totally see how that would be a cool feature to have. In fact, I would recommend opening up a feature request for it (so that other people can vote for it). You can do that here: https://tribe.uservoice.com/forums/195723-feature-ideas

It would also be great to have a vendor slug for each community user, you could turn this on or off, guessing off by default for backward compatability.

Technically, the built-in feature is not that far from that. Each “vendor” (organizer) gets it’s own slug (yoursite.com/organizer/vendor-name/)

However, the second part of that feature request (reorganizing single event URLs based on organizer/vendor slugs) might prove to be slightly more complicated, since it would require the default single-event url to be either overridden or duplicated.

Same holds true for allowing a sequence or a template in the URL.

Once again, these are prime candidates for a feature request over our User Voice channel (as mentioned above).

Short term, your other options would be to either:

1. Try to tackle these customizations yourself. You might want to read our Themer’s guide to get a sense of how that works.
2. Hire one of our recommended customizers to do the customization for you.

It would be great to have better control over the slug (or url) generally as we are looking at url-rewriting to remove the /event/community (as it’s way too long)…. events are events… no-one cares who entered them from the front end, so why have a different url for events entered by admin or community?? Just give us full control of /events slug upwards by putting that reference in a variable instead of hard coding.

That is a very interesting point.

If I read you correctly (and based on the rest of these feature suggestions), your main goal is to have more options / control over the way all of our permalinks/slugs operate.

I can totally appreciate how the /event/community might not fit your specific needs (as a side note, as you probably know, you can change “community” for a word of your choosing).

However, I must point out that a lot of our Community event customers actually do care who entered events in the front-end.

I guess it boils down to each customer’s usage of our plugins being very specific to their situation.

As much as we try to make our plugin as flexible and user friendly as possible for everybody, sometimes we fall short to fulfilling some our great customers (such as yourself) needs.

This is why we also try to make our plugins as customizable as possible.

With that in mind, I want to reaffirm that your ideas are very interesting. Hopefully, by submitting them to our User Voice page, they will gain in popularity (I am pretty sure other customers share your views) and become full-fledged features.

In closing, the reason we use User Voice is because we actually get hundreds of new feature requests a year. Since we don’t have to the ressources to tackle each request, we have to go by the popularity of each of these. We realize this might not be the best approach to things, but so far it’s the best approach we have found.

Thank you for your engagement and understanding.

Best regards,

Geoff B.

[Chris]

Totally get you. Thanks for your feedback. Will put them up on uservoice shortly.

[Geoff B.]

Good evening Chris,

Thanks for writing back.

You are welcome back on our support forums any time 🙂

For now, I am going to close this thread.

Have a great week!

Geoff B.

[Author]

Posts