[Reji]

Hi Rob.

Yes building out a feature like this is very important. Looks like there are multiple requests from some of your other customers for a feature like this (multiple venues/organizers against an event). I’m not sure how you prioritize what features would go in the next release, is there a way for us – the community – to know, so that we can progress our work accordingly?

[Reji]

John – yes, get_tribe_custom(‘Field label’) would definitely help.

[Reji]

Hi Rob. Thanks for checking. If a play name cannot be changed, how do we address that across multiple locations and times? Typically a custom recurring event would also need to be at different dates/times and at different locations. If I go with the proposed solution to break out a series, then I’ll have multiple events entered (duplicate copy, etc), with permalinks to each of those events supplemented by additional numbers example {event-name}-2, {event-name}-3. I could tag them on an event category, however I’m limited to providing a good main description of the event series and have duplicate event content all over the place.

[Reji]

Hi Rob. Hope you’ve got some approach around this.

[Reji]

Shane,

This could be more developer friendly if we could pass the field’s label as a sanitized id, instead of the cryptic _ecp_custom_1. Could that be lined up in a future release?

[Author]

Posts