|
Springanew
|
June 11, 2017 at 11:16 am
I’m running a monthly market where vendors can buy one, two or three months at a time. If they buy a “June only” ticket, when the June market ends they need to roll off the Attendee list (displayed by shortcode) so people know that business slot is open. Suggestions? http://rimrockmarketdays.com/events/market-on-the-meadow/
|
|
Springanew
|
June 11, 2017 at 11:51 am
OK I used [ESPRESSO_EVENT_ATTENDEES datetime_id=datetime_id_for_event] (fyi it was hard to find the datetime ID) which I’ll have to update each month and is doable but would like to see it as a feature to display only current ticket holders in the future – thanks!
|
|
Josh
|
June 12, 2017 at 7:29 pm
Hi there,
You might consider making a specific event for each monthly market. If you use the Multi Event Registration add-on the vendors will still be able to buy more than one month. This way you can automate your published list of vendors by simply including the
[ESPRESSO_EVENT_ATTENDEES] shortcode on the monthly event’s page.
|
|
Springanew
|
June 12, 2017 at 11:16 pm
Hi Josh, good idea but vendors need to buy three consecutive months at a time to get the discount, not just three events otherwise they might buy June August and December and that defeats the purpose of having the exclusive “avon, LuLaRoe” etc. space. The limit of having only one Direct Sales representative throws a whole different kink into events but it’s the rage right now. That plus our events are not big enough to spare the extra for the add ons- thankfully right now the basic program is working although I have to put the event on password protect for a few days to allow current gold vendors to renew. Yes, markets are a different beast.
|
|
Josh
|
June 13, 2017 at 7:40 am
You might consider checking with one of the developers listed here for a quote to build out a dynamic version of the [ESPRESSO_EVENT_ATTENDEES] shortcode to your specifications. The idea would be to add some additional checks for the current datetime to help automate things for you. This will add some additional processing and overhead to the shortcode, and that’s something we generally avoid adding to a distributed product.
|
|
Tony
|
June 13, 2017 at 9:49 am
Also, can I ask where are you pulling the datetime ID from? You mentioned its difficult to find but its included within the datetime editor – http://take.ms/8NHQp
If you have any feedback on how we can make that easier to find I can pass that onto the developers.
|
|
Springanew
|
June 13, 2017 at 10:04 am
Hi Tony, one suggestion is to beta test features with event coordinators working on their events with an event hangover lol. You mentioned one block – editor. I was looking for information, NOT to edit the event, so when I saw the box for input I immediately backed out of the window. Secondly working with Facebook, Twitter and WordPress we are wired to look at the top, and the Datetime ID is at the Bottom – AND third, it is in light font – meaning it’s not important so don’t really pay attention to it. Once you know it’s there you see it, but it took me three maybe four views before my eyes got all the way to the bottom.
Also to Josh – I checked the developer section and at those prices it will be a good decade before I can hire them 🙂 If I was a developer I’d take a look at the “Market” industry as it is a niche market. Actually it’s more like running a shopping center where stores rent a space and each month renew or not. You don’t see two Sears, or two Macys at a mall so there needs to be some way to limit “Brand Names/Direct Sales-Franchises” to only one, and they get to renew before their space/brand goes public. FYI though most markets are run as fundraisers and they are not going to be able to afford expensive programs unless well established. 🙂 Thanks everyone!
|
|
Tony
|
June 13, 2017 at 11:08 am
Thank you for the feedback, I’ll pass this along to the developers.
However, I do know that most of the points you’ve raised concerning the datetime ID are intentional.
You mentioned one block – editor. I was looking for information, NOT to edit the event, so when I saw the box for input I immediately backed out of the window.
We can’t have a ‘DateTime’ section outside of the event editor as the datetimes can’t exist without the event, so I don’t think it would make sense to have them separated out into their own section, right now all of the datetime info is in that one specific location.
I understand your point on seeing inputs and closing the section out, however going back to the above the only place we can show all of the information for a datetime is within the event.
Secondly working with Facebook, Twitter and WordPress we are wired to look at the top, and the DateTime ID is at the Bottom – AND third, it is in light font – meaning it’s not important so don’t really pay attention to it.
That’s intentional as day to day you simply don’t need the datetime ID, in your specific use case you need it, but for the majority of users, it’s not important and so is there as additional info, not the primary info of the datetime.
Once you know it’s there you see it, but it took me three maybe four views before my eyes got all the way to the bottom.
Maybe we can add some additional documentation noting where to find the IDs (the tickets also have the ID in the same location of their settings).
I’m not trying to argue against the points you’ve made above, simply explaining the reasons so far.
—
FYI though most markets are run as fundraisers and they are not going to be able to afford expensive programs unless well established.
This is likely why there currently isn’t a product that is designed specifically for that market. Creating those kinds of systems take a lot of man-hours, not only to create but to update, maintain and support.
EE, for example, has a huge amount of developer hours put in to make the product what it is today. Then take into consideration the support hours and it quickly mounts up. If the majority of users for a specific market are unable to pay for the hours put into developing a product, what is the incentive for developers to, well develop/support?
|
