[Hans]

I found the string in event tickets, so this issue is solved. It just didn’t come up because I had to sync the translation file first.
Cheeers, Hans

[Hans]

Hi Victor,

thanks for looking into it. I cant find the non-breaking space you’re talking about, but know the price in buy-tickets is different from the rest because it has WooCommerce classes and an extra span around the currency sign. I quess Event Ticket Plus uses WooCommerce to build that price while the others are build by TEC itself. If I want it to change, I can use some css to do it. Different theme’s had allready given the same result, otherwise I wouldn’t have mentioned it at all. At this moment I’m using Studiopress Digital Pro child-theme for the Genesis framework.

I’m good for now, thanks.

Have a nice day!

Hans

[Hans]

Hi Victor,

it’s probably nothing to fix, just a small difference in presentation that I noticed. I use Event Tickets Plus combined with WooCommerce and the event price in the ticket has a span around the currency sign and some css, resulting in more whitespace between the sign and the value. The other prices don’t have that span. The extra whitespace does make it seem a bit more relaxed and gives some extra control for who wants it.

You can see it here, if you like, but your test-system will show it too in an event with woocommmerce tickets. I haven’t made changes to the event css.

Cheers,

Hans

[Hans]

Hey Victor,

Thanks for the follow-up. I’ve removed the workaround and the signs are still on the left side, so this issue is indeed fixed.

I do notice a difference now in the that in the ticket area there is a space between the sign and the value and not everywhere else, but that is not that important. The ticket area also shows decimals and the others not, so it seems to be separate from each other.

Thanks again and keep on doing the good work.

Cheers,

Hans

[Hans]

Hi Victor,

Thank you for the workaround. It did the job.

Cheers, Hans

ps. My log shows a recurring PHP warning about line 326 of wp-content/plugins/the-events-calendar/common/src/Tribe/Meta/Chunker.php (“strpos() expects parameter 1 to be string, array given”). Is that of interest to you too? It doesn’t seem to break anything.

[Hans]

Hi Andras,

Thanks for shadow-testing this issue. I have tried to recreate it again myself, but under php v7.1.6 it seems to work here too now. So I quess it’s just solved, although I don’t know how. Consider this solved.

Thanks,
Hans

[Hans]

There is also another small problem that was introduced by one of the last updates that seems to be solved by the downgrade to php 7.0:

When I added a ticket without entering the number of available tickets, untill I updated a few days ago (both the Tribe plugins and WooCommerce itself), the tickets could be bought in my event. But then it started to mark them as sold out and I had to enter the number of available tickets to make it sell again. I know it is not woocommerce itself causing it, because I wen going back to the previous versions of TEC TEC Pro, ET and ET+ made it work again.

After I went back to php 7.0 the tickets stay available for sale without entering the # of available tickets again. Although the ticket now can be bought still, on the admin-side a difference to previous versions of the plugins remain, since after # sold it still says (0 remaining) as if there still is a limited amount available. It is workable for me, but there might be something for you to solve perhaps?

I noticed this problem after upgrading to versions:
TEC v4.5.6
TEC Pro v4.4.12
Event Ticket v4.5.0.2
Event Tickets Plus v4.5.0.1

Hope it helps. In php7 it seems to work fine, so at my install it’s nothing to solve.

Kind regards,

Hans

[Hans]

Great. I’ll wait for the fix.

Cheers, Hans

[Hans]

Hi Andras,

Thanks for the workaround.

In case of a past event there is less confusion, although with a call2action a visitor may jump directly to the buy-tickets div and not see the message above the event description. So it’s more a general observation that the event tickets plus plugin doesn’t really provide clear information when tickets are not shown based on a start or end date of the ticket sales. Omiting the ticket part of the event alltogether may be functionally right, but is not that visitor friendly and confusing when call 2 actions are used, like you concurred. So there is a need for some customization. The snippet helps, but perhaps the issue itself is something to consider as a future feature.

Thanks, Hans

[Hans]

Hi Andras,

To answer your questions:
1. the plugin that reports the deprecated call is: “Log Deprecated Notices” by Andrew Nacin (https://nl.wordpress.org/plugins/log-deprecated-notices/)

2. I still get the message when all other plugins are deactivated and using theme twelve sixteen. Without too extended testing, it seems at least to be generated whenever the events archive is shown, not when showing the event single and not when I am already in the archive and go to previous events. So the events archive seems to be the source, and it seems to be part of your plugin rather than anything else.

Hope it helps.

kind regards,

Hans

[Author]

Posts