Terrible piece of software

  • larsesdal

    (@larsesdal)


    2 months, 2 weeks ago

    I’m a software developer and can say looking under the hood—this is a terrible, fragile, bloated, poorly architected piece of software. Been losing my work (and money) due to tickets being randomly deleted, which in turn causes viewing prior orders of those ticket types to throw errors.

    So many of the default user interface decisions are terrible and this requires a ton of CSS and event template overriding to generate what I consider a reasonable user experience in buying tickets.

    The architectural decision to split “RSVPs” (for free events) and “Tickets” (for paid events)—basically entirely different object types—is nonsensical and maddening. There is poor support for multiple attendees on the same RSVP, a frustration totally unnecessary if they hadn’t made terrible architectural decision to treat these so separately.

    The Events Calendar may have been good a few years ago when few other options existed, but now they are just coasting on reputation and a large number of installs.

    Bottom line: USE AT YOUR OWN RISK. Cannot recommend.

Viewing 1 replies (of 1 total)
  • Plugin Support Abz

    (@abzlevelup)

    2 months, 1 week ago

    Thank you for taking the time to share your detailed feedback. I appreciate your perspective as a developer, and while it’s clear you’ve encountered some frustrating challenges, your input is valuable in helping us improve.

    Regarding the ticket deletion and associated errors, that’s definitely not typical behavior, and I’d like to dig deeper into this. If you haven’t already, I recommend opening a support ticket so we can investigate the issue further and identify a solution. Since this involves the premium version, we can’t address it here because of .org forum guidelines.

    You’re right, some aspects of the default user interface may require customization to align with certain design preferences or specific workflows. While our goal is to offer a flexible foundation that works for a broad range of users, we recognize that advanced users like yourself often need to go further with CSS and template overrides to achieve a tailored experience.

    As for your comments on the user interface and architecture, especially the separation of RSVPs and Tickets. I understand how this design choice might feel limiting depending on your specific use case. We’ve made this distinction to accommodate a range of event scenarios, though we’re always working to refine and expand functionality based on user needs.

    We’re constantly evolving and improving our products, and user feedback plays a significant role in shaping our roadmap. While I realize your experience hasn’t met expectations, I’d be happy to continue the conversation and assist you with any specific technical issues through our support platform.

    Please feel free to reach out directly via a support ticket.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this review.