Unstable and new bugs after each update

  • I purchased 2 Lifetime licenses of Event Pro when it was v3.x. The latest v3 plugin worked fine and was stable. There were 2 unresolved bugs impacting the redirection and side cart with WooCommerce and Elementor Pro. These were never resolved in v3.x

    V4.x was realease 2 weeks after beta testing and was simply NOT production ready at all.

    The whole data migration was broken. Live events not working anymore etc. Completely unusable and impacting Webshops and online buisinesses.

    Since v4.0, I’ve been in almost weekly contact with support to get things sorted.

    There were so many regressions that I’ve spent easilly 2 full days debugging and testing + tweaking for them.
    2 security/patch updates that resulted on a critical issue 4.0.5 and 4.0.9 of the free version.

    Styling is after almost 4 months still not applying the primary and secondary colors defined in the plug-in settings. The 3 available single page event templates are simply not using these and have a lot of plugin-in specific default colors you need to override in CSS. I mean, for buttons and so on, you should at least inherit from the theme used by the website…

    v4.0.7 came out with a breaking change not documented in the release notes. Date format with / was not supported anymore while it worked fine in all previous versions. Again, impacting the whole site.

    Since version 4.0.10 free made available in the past hours, the styling of the single page for free and pro was again changed. Previously applied CSS styling up to 4.0.8 is simply not taken into consideration anymore. Ugly + – buttons for quantity, attendee registration form also impacted with border styling and color changes.

    And in the release notes, you can only read a few fixes.
    Well next to the fixes you have a lot of impact on branding/styling which is bad for reputation.

    And it introduced new bugs!
    Existing published events with 2 ticket variations available for purchase had simply no ticket purchasing options displayed anymore. Needed to delete and create them again.
    How can this be release as this would have broken the whole registration count per ticket if I did the update on the live website!!!

    The registration limit date is nowhere to be found in the admin part of the event. But it is displaying a date coming out of nowhere which is even in the past but the tickets are still available for purchase.

    I feel I’ve been a beta/quality insurance tester since june 24 for this plugin.

    The promise is appealing and the marketing and affiliates have high praises. Looks like they never had to work with the plugin on a real website because honestly, it’s the only plugin I’ve ever used (and paid for twice) that is blocking me for making security updates on a customer website.
    Let alone demanding a lot of effort to maintain a working website with the expecting look and feel update after update.

    And it’s not like I’m using it for a complex use case. Simple offline events with 2 ticket variations on 1 website. No schedules, agenda, seat map, speakers, etc
    And RSVP only on the second website.

    Headhache for both thanks to Eventin.

    Support is polite and apologising everytime. They better start fixing and stabilizing things instead of apologising foor the poor quality of their development and quality insurance work.

Viewing 4 replies - 16 through 19 (of 19 total)
  • Thread Starter gregvdo

    (@gregvdo)

    Hi @azamansagor

    I just replied to your last email after testing stable release 4.0.12 and 4.0.11 pro.

    This has resolved a good list of the issues. Thanks!

    I do still have multiple things reported in my reply that are still not working as expected.

    Attendee additional field placeholder texts not being displayed, some CSS classes that again changed name since v4.0.11 which impacted my custom classes on some parts.

    And there are still a few things unclear. Such as Event registration deadline field that was deleted from the Event Basic Information and is not something that can be displayed anymore. While this is a crucial aspect to encourage people to register and buy tickets on time.

    Also the ticket availability date is not displayed on the front-end anymore, so that cannot be used either.

    I also have an open question (and issue) as we do propose 2 ticket variations. But the attendees should only be able to purchase 1 out of the 2 proposed variations per attendee. As we do have an extended attendee registratio form which needs to be unique per attendee. So no option for someone to purchase 2 times the same variation (solved with max quantity) or 1 per ticket variation (not solved)

    Is there a way to achieve this?

    Thread Starter gregvdo

    (@gregvdo)

    Latest updates in this wonderful universe of Eventin.

    v4.x is currently NOT optimised for SEO. Doesn’t use the SEO titles and descriptions nor the seo images. Same goes for Social meta which is not used as it should and makes the sharing of Event archive and Event single pages on social a TOTAL mess and look very unprofessional.
    While sharing events on social is like the basic way of getting the word out…

    And once more a FIX/Patch version is again and again and again BRINGING NEW stuff instead of just fixing bugs. The whole point of FIX/Patch versions is to FIX bugs or apply security patches.

    Between v4.0.12 and v4.0.13 the Event Archive page is NOT using the Elementor Archive page applied to it.

    And this is the published change log of v4.0.13
    = 4.0.13 ( October 28, 2024 )=
    Fix : Attendee and ticket name updated on order email
    Fix : Clone event doesn’t reset sold tickets
    Fix : Events details template load on oxygen builder
    Fix : Event checkout page load issue on oxygen builder
    Fix : Event price and currency formating was incorrect
    Fix : Woocommerce payment redirect to success component while payment failed

    So again, impact on an existing functionality that has been working fine (for once something) since v3x and one fix version further with v4x and boom borken.

    Imagine people applying auto updates for fix version which are often seen as crucial or security related…

    They would have a broken website every months with this plugin. And you had the audacity to ask me to update my review… I mean, there is no 0 in the ratings unfortunately so I can’t really update it to be honest.

    Can you fix this TODAY please. And I won’t repeat it any longuer after this final call. Get more focus on the overall release process and quality insurance on your plugin. This is by far the worst experience I’ve had in over 15 years working with WordPress.

    Plugin Support Md Mahbub Morshed Chowdhury

    (@faheem96dev)

    Hi @gregvdo,

    Hi,

    We can understand your frustration. 

    As you know, development is a gradual process, and addressing complex bugs and compatibility issues takes time. You know our development process that we always fix the bugs and try to produce a bug free user experience.

    Also, no one wants to be a buggy product to be released. You know that how much big that plugin is. Even no one is using the full plugin because it has lots of feature. And we are trying to fix them one by one and trying to do it ASAP. I know you are frustrated and its should be. But we are trying to fix all the issues ASAP for our customers.

    And we can no implement a module overnight because we have to do R & D first. Lets say you have told us the archive page is not overridable with Elementor PRO. So we have to do R &D first on it and then we can implement that feature. We try to happy all of our clients.

    Please rest assured that our team is actively focused on improving SEO compatibility and ensuring everything works smoothly for you as soon as possible.

    Best Regards

    Thread Starter gregvdo

    (@gregvdo)

    Hi Mahbub,

    I’ve sent a reply by email with a file listing the remaining big issues.

    I fully understand the complexity of your work as I’ve been working in custom software development for the past 16 years on small to very big enterprise projects.

    My main concern here is that things are working in v4.0.xx and then not anymore in v4.0.xx+1

    Like the Event Archive Page using Elementor Pro template. This has been working fine since v3 and on all v4.x version up to 4.0.12. V4.0.13 and 14 broke this to comply with Oxygen and Divi, but seems it wasn’t validated for Elementor before release.

    I appreciate your efforts and support and hope we’ll soon get to a stable v4.x working with Elementor Pro

Viewing 4 replies - 16 through 19 (of 19 total)
  • You must be logged in to reply to this review.