Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • 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

    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.

    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)

    Hi,
    You haven’t fixed the issues based on my check.

    The date picker for attendee additional fields is still blocked on present/future dates. And the event Registration deadline is not fixed. You simply removed the field on the front-end.

    How are the registration deadlines made visible to the customers? Where are they defined on the event?

    In v3 it was clearly defined on Event level and displayed on the event front-end page.

    Now in the latest v 4.0.11, you don’t have the Registration deadline field on the event level. You have it on Ticket level, but the dates are not displayed anywhere. They where briefly displayed in v4.0.10.

    Honestly each update is a complete disaster and makes this plugin compeltely unusable.

    Phone number standard field in the attendee registration form has a placeholder text including a +. You can’t use a + in the field as it only accepts numbers. The field now also doesn’t accept a 0 as first number and simply removes it. Which is basically completely wrong as all phone numbers start with a 0.

    I’m really getting annoyed and desperate by the poor level of understanding an quality displayed by Theme Winter.

    Thread Starter gregvdo

    (@gregvdo)

    Hi @faheem96dev

    I’m not convinced the vision is followed by the whole staff based on the previous answers I got and shared in my previous comment.

    And both things you mention in your reply repeated here below and completely wrong and absolutely not what I mentioned in my email.

    Regarding the registration deadline field, we will remove it in the next update. Additionally, we want to assure you that event creation on past dates is possible with our plugin. We will provide you with the beta fix for the issue you have reported.

    The Event registration deadline field IS ALREADY MISSING. But on the front-end the date entered previously is still displayed and connot be updated anymore.
    So you need to ADD IT AGAIN in the event basic field section of the events.

    And the past dates I mentioned are NOT for the event date. They are for the additional attendee fields with a date type where you can only select present or future dates. We used this field because we need to ask for the attendee Birthday during registration.

    Again, this was working fine in V3. And the registration deadline field was even there until v4.0.8.

    Thread Starter gregvdo

    (@gregvdo)

    Hi,

    I’ve installed the latest version and it solves only a very limited amount of issues I’ve communicated.

    See email sent on october 9th with subject “Re: 3 annoying issues with Eventin Pro” which is onlgoing support case opened more than 5 months ago.

    Answer to an email from someone from your suppor team provided customer oriented answers such as:
    “more than 10 thousand users didn’t claim that except you. What would you say about that?”
    “When a new update comes up, lots of things change as per the UI design, if you do not like it then you can customize it with CSS”
    And the best one here:
    “Have you ever tried it once? I don’t think so.”

    Kind reminder that I’ve purchased 2 lifetime licenses of Eventin pro and it has been a real headache with V4 and even keeping the site-wide styling and colors is requiring to have developer skills and not using the defined colors of the theme which are overwritten by Eventin css, nor even applying the Primary and Secondary colors set in the Eventin settings.

    In this reply, I’ve also (once more) submitted new bugs introduced since v4.08, such as Registration deadline field who has disappeared in the event edition page and still displays a value on the front-end, the date format type for additional fields only accepts present and future dates which makes it unusable for Birthday capture

    Hope I can get the required assistance to have a fully working product in the coming week.

    I’ve fixed the styling issues myself using custom CSS.

    I’m once more getting delayed and my customers are waiting for events to be put online due to this as I cannot upgrade to v4 in the current state.

    • This reply was modified 1 month, 1 week ago by gregvdo.
    Thread Starter gregvdo

    (@gregvdo)

    Again almost one week later. 3 days without answer on my email requesting status and ETA for fixes and (hopefully) stable version 4.0.11

    I missed already 4 deadlines for my customer and had to launch an event last monday!

    Which is still not possible with all the issues reported and I’m once more waiting blindly with no information whatsoever and only excuses followed by silence for days.

    Thread Starter gregvdo

    (@gregvdo)

    Hi @azamansagor,

    The significant updates you are mentioning are an issue since the (early) launch of an unfinished and unstable v4. After already 10 updates, you’ve been making breaking changes multiple times, adding regressions and breaking functionality that was working fine in previous versions, creating critical errors on 3 different updates including 4.0.10 which is still breaking the Customize part of wordpress and throws a critical error (working fine in 4.0.8).
    You made fundamental feature and setting changes in multiple patch versions which should ONLY be used to release bug fixes, security patches and minor improvements at most.

    Impacting free and paid users for 4 months with a direct impact on financial aspects as this plugin is meant to SELL Event tickets and is currently resulting in LOSS of customers.

    I hope you start applying the right quality insurance, regression testing, governance and overall lifecyle management. This amateur way of working needs to stop now.

    Why add new features and not fix known bugs for 10 updates in a row?!

    I’ve provided access to a staging website and hope to get things sorted today. With yet another hope for a stable version as from 4.0.11 and ON.

    • This reply was modified 1 month, 3 weeks ago by gregvdo.
    Thread Starter gregvdo

    (@gregvdo)

    I don’t have a ticket number. Never received one for all the different requests submitted to support by chat or email to [email protected]
    Latest email was sent: Date:27 sept. 2024 14:17
    Subject: Re: 3 annoying issues with Eventin Pro
    Thanks for making the necesary fixes by tomorrow end of day.

    Thread Starter gregvdo

    (@gregvdo)

    Hi @azamansagor,

    Please have a look at the emails I’ve sent to support today as a paid customer with 2 Lifetime licenses.
    There are MANY findings there that need immediate fixed to be released now.
    I’ve been dragging this unstable plugin for way too long (more than 4 months) and have spent multiple DAYS of work debugging and providing feedback.
    So far v4 is a big deception. Only delivering a bad user/customer experience and Eventin is the only plugin really blocking for any updates. Really high maintenance…

    But it’s an essential part of one of my customer’s online businesses. So I hope you understand the priority to have something working and stable today!

    Hi @azamansagor,

    Thanks. To be honest, I’m not taking any apologies anymore. Please do have a look at the emails I’ve sent today to the support team (and the months of history).
    The list of bugs is only getting longer.
    And I’ve been delaying the 4.x upgrade on a key customer webshop for more than 4 months due to lack of quality and stability.
    I hoped to get it stable with release 4.0.10 and pushed for it extensively. But still not there yet and even worse, this version introduced new regressions once again.
    I need to have a stable working version by tomorrow end of day as I’ve been delaying as much as possible but this is now directly impacting the online business of one of my (and your) customers who has a Lifetime license of Eventin Pro.

    Since 4.0.10 branding and colours is again default and broken on multiple items. Previously applied cutom CSS not being applied.
    Default primary and secondary colors applied in settings not taken into consideration on buttons etc. Just applying the default plugin colors out of the box.

    Branding and styling is just a complete mess on this plugin and very unstable. Regressions or breaking changes after every update.

    Still not fixed in 4.0.10 and pro 4.0.9 with dates set in the future for Event and tickets.
    Please fix this now.

    • This reply was modified 1 month, 3 weeks ago by gregvdo.
Viewing 13 replies - 1 through 13 (of 13 total)