Posted: January 3, 2019 at 3:55 am
I’m am using event espresso for approximately 6 months and I can tell I expected a lot more of it. Event Espresso was recommended to me by someone, because I had no idea of which plugin to use with my WordPress site, but now I think (or really hope) there would be other, better, less rigid plugins for ticket selling.
I am working for a rather small organisation, but although we are small, we have a lot of events (100-150 a year) and we have around 1.000 attendees to buy tickets every year.
What I really don’t like about event espresso:
I am really hoping something can be done about all this, because I am seriously thinking about switching to another plugin as soon as I can find one.
Or maybe Event Espresso is not the right plugin for an organisation like mine with that large amount of events and attendees.
I’m sorry you expected more, can you provide some example(s) of what ‘more’ would be in this context?
You mentioned EE is rigid, but again, can you clarify? At the time of writing the codebase for Event Espresso core has over 1600 Filter Hooks and a little under 900 Action Hooks with various ‘template’ files in use within EE that can also be overridden should you wish, meaning you can customize a huge amount of EE’s code to suit various different use cases.
We have this on our roadmap for the attendee mover add-on here:
However, we have to prioritize our development time and we do so by working on the features with the most requests (plus our own vision for the plugin). The above feature has very few requests (less than 5) meaning it so far hasn’t been considered for development.
This is something we are aware of and have been discussing possible ways in which we can handle this within the plugin, eventually, we’d like to have a method to archive the data but it’s not available currently.
The registration CSV includes the Transaction Status, Total, Amount Due, Amount Paid, Payment Date(s), Payment Method(s) and Gateway Transaction ID(s)
I’m not sure how that is useless?
However, the CSV is completely customizable so you can add any transaction related data you need to. May I ask, what data would you link to include?
You could even filter the CSV to only contain very specific fields (meaning it would no longer even suit being used as a registration CSV) within a custom function, enable the function and export the data, then disable the function to continue to use the CSV as ‘normal’ if needed.
Can you provide some examples, please?
For #1 and #2, those are feature requests and are unlikely to be added to the plugin ‘soon’ at this time, simply because we are working on other areas of the plugin currently.
If points #3 and #4 are your dealbreakers its possible we can help add more details to some sections that may help. The CSV is filtered so you can add additional details to it, some additional details can be added to the tables used within Event Espresso which may help with 4. However, it’s important to set expectations correctly here in that we can’t simply re-write the plugin/interface to exactly how you want because you don’t like the current interface, we can help point you in the right direction to something that may help reduce the issues you have now though.
I can’t answer that, only you (or the organization) can.
I can tell you that we work with users with high numbers of events and attendees with EE4 and it seems to fit well, but it’s all personal opinion and what one person likes, another does not.
Thank you for your reply.
I added some more information underneath…
I am struggling with payments that are paid back. I do not find this very clear. I would want to have a list of all the single amounts of many that are paid to me, for which event and how they are paid, and the same list for all the paybacks.
We would like to have more filters. For example, we have an event that is recurring on several dates, but not regularly (like every month). For example the same event on the 1st of July, the 18th of August and the 3rd of October. I would like to filter my attendees.
We don’t have a transaction/payment report that lists all payments/refunds in that way. The registration csv report could be edited to breakdown the payments further within the that if it will help?
So is each recurrence a new event or do you have them set up as multiple datetimes within a single event?