gregvdo

@azamansagor hi again,

Look, this is completely impacting my customer’s business and financial revenue now!

I tried publishing an event on the live website using v 4.0.12 and Pro 4.0.11.

There is NO WAY to make a purchase for an event.

After clicking on the purchase button on the desired ticket variation, the user gets redirected to a checkout page that stays COMPLETELY empty.

In the previous versions there was the Attendee registration form with all the standard and custom fields defined. And then after completion the user was redirected to the shopping cart.

The attendee registration form step is simply broken.

And I can’t update the plugin to 4.0.19 and pro 4.0.15 due to the other bugs reported!!!

The major one remaining on the staging website is the Event Archive page that doesn’t use the custom page designed and assigned in Elementor Pro Theme Builder. This was working fine up to v4.10. There was a workaround by modifying a PHP line in the Event Single post page but this one is not working anymore in v4.0.19…

There is a newsletter planned to be sent this Tuesday 07/01 at 10am CET to announce the event and get some sales.

FIX THIS TODAY on the final version of your plugin and make a proper WELL tested release including ALL the remaining bug fixes!

And I’m still waiting for a financial compensation proposal here. I think I’ve been more than patient enough after 6 months of constant support contact.

• This reply was modified 1 year, 4 months ago by gregvdo.

@webdev3244 unfortunately the issue is not resolved after now more than 6 months.

Each update brings new features and fixes but most of the time also regressions breaking stuff that worked previously.

With Elementor Pro, the standard side cart is simply broken when Eventin Pro is enabled as a plugin. I have a workaround in place since v3.x for that and need to redirect to the cart page. Less engaging to buy multiple products at the same time.

Eventin redirection after adding to the cart is also again applied to the whole WooCommerce list of products while I only have 1 Eventin related product. This setting is simply overriding the whole webshop behaviour. Fixed previously and came back again.

The Event Archive page which was built with a custom Elementor Pro Archive page on the website was working fine since v3.x until v4.12. Then there were changes introduced to support Divi and Oxygen builder which broke the Elementor compatibility for that part. I need to change the PHP code of the plug-in manually after each update if I want this to work with Elementor. Been reported for more than 2 months…

These are (hopefully) the last 3 big issues I have. The others have been fixed over the months. Can’t really switch easily to another solution that fits the needs without impacting my customer. But if these last 3 points don’t get solved before end of 2024, I’ll definitely ask for a financial compensation.

I’ve been playing beta tester and QA for Theme Winter for way too long and it has cost me multiple days of work!

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.

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.

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 year, 7 months ago by 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 year, 8 months ago by 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!