Event Tickets Plus 4.0.1.5 changes styles of headers, buttons, form

[Rob]

I noticed that the styles of the ticket purchase form changes somewhat jarringly when upgrading to Event Tickets Plus 4.0.1.5. If you compare the following two URLs:

1. https://www.westernlegendsroundup.com/events/tenderfoot-day-wagon-train-ride/
2. http://mt-western-legends-roundup.pantheonsite.io/events/tenderfoot-day-wagon-train-ride/

You’ll see that #1, the non-upgraded live site has the correct style while #2, the upgraded non-live site has the incorrect style. I have only been using the default styling provided by the plugin, and have not modified it for this piece. Looking in the view source for each site, specifically for the Add to Cart button, I see that the live non-upgraded site has:

<button type="submit" name="wootickets_process" value="1" class="button alt">Add to cart</button>

and is governed by the CSS file /wp-content/plugins/event-tickets-plus/src/resources/css/wootickets.min.css?ver=4.4.9

while the non-live, upgraded site has:

<button type="submit" name="wootickets_process" value="1" class="tribe-button">
							Add to cart						</button>

(spaces preserved) and is now governed by a different CSS file /wp-content/plugins/the-events-calendar/src/resources/css/tribe-events-full.min.css?ver=4.5.6

Similar things are happening to the H2 and the horizontal rule, plus subtle changes with the ticket name and amount text.

Why did you change the CSS classes from button alt to this completely new class tribe-button? Why the change of CSS file? And, even so, if I’m not running custom styling, why would the change matter? Wouldn’t your new stylesheet code pick that up?

[Andras]

Hello Rob,

Thanks for reaching out to us with your questions. Let me try to answer them for you.

In our recent release we have introduced the “Buy now” buttons which are visible on the list based views (List, Day and Map views). For these we have introduced the tribe-button class and have applied it to the buttons on the single event page as well to streamline the look of the buttons across all pages.

With this new feature some formatting has been adjusted as well, that is why you might see some changes.

However, I believe the missing line is a bug. I have filed a bugticket for that so our developers can take a look at it and fix it.

As a workaround, until the fix arrives, you can paste this css snippet into your theme’s style.css file:

.tribe-events-tickets td.woocommerce {
border-bottom: 1px solid #dfdfdf;
}

If you would like to style the button on the single event page, then you can do it with this css snippet:

.tribe-events-tickets .woocommerce.add-to-cart .tribe-button {
/* styles you want */
}

Hope this helps.

Cheers,
Andras

[Victor]

Hello Rob!

Just wanted to share with you that a new maintenance release (for the Week of 18 September 2017) is out, including a fix for this issue 🙂

Find out more about this release → https://theeventscalendar.com/maintenance-release-week-18-september-2017/

Please update the plugins and let us know if the fix works for your site.

Best,
Victor

[Victor]

Hello Rob!

Just wanted to share with you that a new maintenance release (for the Week of 18 September 2017) is out, including a fix for this issue 🙂

Find out more about this release → https://theeventscalendar.com/maintenance-release-week-18-september-2017/

Please update the plugins and let us know if the fix works for your site.

Best,
Victor

[Rob]

Thanks. too little too late in the case of this particular client. They are going to start all over with how they do event ticketing and calendaring because of this and other major shortcomings of this plugin. Their sales and ticket fulfillment process was a total nightmare with this plugin. One thing they really needed was a sensible Will Call option. And the emailed tickets printed on two pages each…not good when people were buying 8 tickets for a group of attendees and showing up with reams of paper tickets. Nobody could figure out how to do the QR code scanning despite my having given them careful directions to follow…it’s just not intuitive or integrated enough. Lots of other problems as well, but I’m already off-topic here.

[Andras]

Hey Rob,

Thanks for getting back to us and especially thank you for your feedback.

We are sorry to hear the plugins didn’t make it for the client. There are cases where our plugins might not be the perfect solution out of the box.

As for the issues, we are aware of some of them and our team will get around to fixing them.

I am going to close this ticket, but if you need anything else related to this topic or another please create a new ticket and we’ll be happy to help.

Good luck with your project!

Cheers,
Andras

PS: We’d be grateful if you would give us feedback on your satisfaction with support. Just click on one of the classy looking emojis below. 🙂 If you can spare a few words, that’s even better. Thank you!

 

[Author]

Posts