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.<\/p>\n
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.<\/p>\n
eg:<\/p>\n
Bob The Builder is selling tickets to his singing show:<\/p>\n
http:\/\/communitytickets.com\/bob-the-builder\/
\nhttp:\/\/communitytickets.com\/bob-the-builder\/my-singing-show\/
\nhttp:\/\/communitytickets.com\/bob-the-builder\/my-singing-tour\/10-july-2012-10-00\/<\/p>\n
Would also be great if you could have some other permalink control also.<\/p>\n
1) Instead of defaulting to a date, also allow a sequence number, or a template:<\/p>\n
http:\/\/communitytickets.com\/bob-the-builder\/my-singing-tour\/2\/ (for second re-occurring item in that event series)<\/p>\n
so in admin:<\/p>\n
permalink : \/%events-slug%\/%community-slug%\/%community-user%\/%event-name%\/%sequence%\/<\/p>\n
or for date<\/p>\n
permalink textfield : \/%events-slug%\/%community-slug%\/%community-user%\/%event-name%\/%sequence%\/<\/p>\n
and date time:<\/p>\n
permalink text field : \/%events-slug%\/%community-slug%\/%community-user%\/%event-name%\/%event-date%\/%event-time%\/<\/p>\n
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??<\/p>\n
Just give us full control of \/events slug upwards by putting that reference in a variable instead of hard coding.<\/p>\n","protected":false},"template":"","class_list":["post-1138456","topic","type-topic","status-closed","hentry"],"yoast_head":"\n