Attendee Names & Emails for WooTickets

[Mike]

I hate to beat a dead horse, but in reference to this part of the Wootickets info page:<br><br>

“We’re also working on creating unique user specific tickets. Currently each order is associated with one name. We’re working on the ability to attach information about a specific attendee to each ticket.”<br><br>

Is there ANY progress on this? I really dont want to move to a competitor, but it has been almost a year since I jumped on the Wootickets bandwagon and reliance on JP’s 3rd party plugin for critical base level functionality is really restricting our ability to update your software. We want to stay with you guys, but how long is it going to be before this makes it into a release? <br><br>

I know you want to add in the ability to tie in all sorts of extra fields, but I would be happy with the base functionality of getting the name & email of the person who is ACTUALLY GOING TO THE EVENT. <br><br>

As a sample user case scenario, I ran the numbers for all of our ticket sales since we started using wootickets. 27% of sales were done FOR someone else. That is OVER a quarter of sales. That is NOT an insignificant number, and I am sure that if we compared statistics with other users of your software we would see similar percentages. It could be a wife using her husband’s credit card, a boss paying for his employees, a mom paying for kids, someone paying for a group of friends, whatever. The point is that this is basic functionality for ANY ticketing software, not a bonus feature.<br><br>

Please, please, PLEASE get this into your next release.

[Barry]

Hi Mike,

I do appreciate where you are coming from here and that it’s been a while without any movement on this one. This enhancement is still under investigation and part of the issue is engineering things in a way that will work without causing problems for other ticketing plugins that run on top of the same framework.

I’ve updated our issue tracker to note your continued interest here and would encourage you to continue to monitor our product stream to stay abreast of developments here.

[figcreative]

+1

[paulpetch]

I’m now with another developer trying to get this fixed. Implemented. Working. What ever you call it. First response from developer “why is a core feature not working?”

How can you sell a product that does not tell the buyer or admin the sale info? Wrong dates? No dates? WTF?

Contacting developers of the plugin has been pointless. No one even bothers to return emails.

This is not a REQUESTED FEATURE its a feature that should be there already.

I’ll not be recommending this plugin to anyone. What is more important in the development than actually making the event ticket purchase send the dates to the buyer and admin!!!

[paulpetch]

So Rob. This question is the same as mine and 1 year has passed for Mike. I’m confused to why i ask for this “feature” and its an issue yet others are also looking for this fix.

Anyway, where is the attendee list you talk of?

[Schalk Joubert]

I may as well add my cents, all of them.
I’ve also been arguing for this to be added, and a keen supported on the feature request.
https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/3738379-collect-all-attendee-information-for-multiple-tick
Unfortunately after a year, we decided go with another plugin.
After all this feature is officially on the roadmap since 31 August 2013.

[Barry]

We’re sorry to hear you had to go with another plugin, Schalk, but completely understand this plugin is not a perfect fit for everyone.

This is not a REQUESTED FEATURE its a feature that should be there already … Contacting developers of the plugin has been pointless. No one even bothers to return emails.

Paul: thanks for your feedback. I can certainly understand the desire for this functionality – but let me clarify a few things.

• The vision for WooCommerce Tickets (or WooTickets as it was originally) was always to create a straightforward, robust ticketing solution – not a comprehensive event management suite
• We do not actually state anywhere that this is one of its capabilities so, in concert with my first point, I’d suggest this does indeed qualify as a feature request rather than being something that “should be there already”
• As has been discussed, we definitely are considering adding functionality along these lines. Is it our very highest priority? No, it is not. Ensuring the underlying ticketing framework is solid is a higher priority and of course we would need to implement any developments in a manner that works well with all of the plugins that rest on the framework – so this isn’t something we’re going to rush into head-first
• Those who would like to see this functionality will naturally advocate for it’s inclusion – that’s natural and we encourage it – but we also have to balance this with the number of users we know to be happy with the plugin who have no such requirements (and consequently little incentive to comment upon the issue)
• Finally, if we haven’t been sufficiently responsive by email I’m sorry – but we do try to make it as clear as possible that the support forum is the correct venue for support issues (and similarly that our UserVoice page is the correct venue for making feature requests)

Anyway, where is the attendee list you talk of?

Please do check out our new user primer and the video in Section IV which illustrates this – if you need further guidance we’ll be happy to help, but please do create a new thread of your own if you haven’t already done so.

 

[Author]

Posts