No caching, tested in Firefox, Chrome, Edge and mobile variations, all produce the same result.  I checked a couple of websites that use EVO Tickets (appears to be latest version) and they too create a similar over-sized ‘added to cart box’; compared to the tighter/cleaner version in earlier EVO tickets.

Any way to trace back to the change?

The site I confirmed with is:
http://www.beefmince.co.uk/tickets

You can see the now larger ‘added to cart’ box, compared to the method that was used in the earlier EVO Tickets.  (I also confirmed with another site as well, if you would like me to post that link, I will as well)

Thanks!

Yes, if that’s the style you prefer, but here’s the thing, the prior version(s) of EVO Tickets appear to uses a smaller box that activated below the ‘add quantity area’ and now the new version(s) replace that entire area? In many cases our customers decide at the last minute to additional quantities and it causes confusion (yes, I know); not to mention, it’s visually less appealing, from a clean, tight status box to a very large overwriting surface area.

We just want to go back to the prior method, but utilize the latest version of EVO Tickets, how can get there?

(Attached is our preferred display method).

Thanks!

An example is if a customer adds a ‘Group A’, then realizes they need a ‘Group C’, they can stay in one location and add many variations/quantities as needed. It appears this may be more of an issue when using variable pricing, alas, all of our event tickets use variations.

In that, we need the ability for a customer to add additional ticket variations/quantities and not have to move away from their current location, especially in mobile usage.  That’s why the box added below was so ideal for us, a customer could add as many as needed, lastly, this was great for group purchases, which we get regularly.

Thoughts?

We’d prefer the older style actually. Is this something we can get as a paid mod., if it’s affordable? As for others requesting the older style, they may not even realize the impact of the change, that or they simply don’t use variations, it’s hard to say.

Curiously, why was it changed in the first place?  I just don’t see the advantage?

Thanks!

Just a quick follow-up on a potential paid modification.  That said, what was the last version of EVO Tickets that utilized the method that we prefer and will it work the current version of EventON (and related products), our goal is just to get to WooCommerce 3.x and if we have to utilize an older version of EVO Tickets, that’s fine, we’re already doing that now.

Your help and thoughts are truly welcomed.

Thanks!