[Victor]

Hi Luke!

I’m sorry for the delay in getting back to you. I’ve been away for a few days.

Here’s the working snippet that should hide the recurring instances in the community events list:

add_filter( 'tribe_ce_my_events_query', function( $ce_list_query_args ) {
    $ce_list_query_args['tribeHideRecurrence'] = true;
    return $ce_list_query_args;
} );

Please try it out and let me know if it works for you.

Best,
Victor

[Victor]

This reply is private.

[Victor]

Hi Mats!

I’m sorry for the delay in getting back to you. I’ve been away this last days and I couldn’t get my hands on this topic.

I would love to help you further with this but it might take me a few days to find the availability to make some tests with those template overrides and see what I can find.

I will keep you posted as soon as I have something for you to try.

I appreciate your patience while I work on this.

Best,
Victor

[Victor]

This reply is private.

[Victor]

Hi Abigail!

Thanks for following up with this.

We have already logged a report for this issue and it will be addressed in one of our next maintenance releases of our plugins. It should affect all plugins so don’t worry about the topic.

I will link this thread to the report so we can let you know when it’s fixed.

I apologise for the inconvenience and we appreciate your patience.

Best,
Victor

[Victor]

This reply is private.

[Victor]

Hi David!

I’m sorry for the delay in getting back to you. I’ve been out this last couple of days and could not follow up with this.

As a first glance, the problem is the fatal error that triggers because it exceeds the Maximum execution time of 30 seconds. It might be that using your theme might be taking more time to load that page. Please try raising this time limit and see if it prevents the fatal error.

In the meantime, I will reach out to the team and see if they can offer some insight on this matter, and also flag the PHP warning for the non-numerical value you are getting. We’ll let you know what we find.

Please let me know how that goes.

Thanks,
Victor

[Victor]

Hi Steve,

First, my apologies for the delay in getting back to you.

I have just checked the bug report and unfortunately we are not going to be able to tackle this one in our next maintenance release. It seems this issue is connected to another one and both need to be addressed at the same time.

I’m sorry the workaround did not work for you. This might be due to the fact that one of your tickets has unlimited capacity and as a consequence it makes all your other tickets unlimited. You could try setting a very high limited capacity for that ticket and see if it changes that behaviour (in addition to making sure that stock management is enabled at product level).

Using an older version of our plugins should be another workaround, as this issue is only present in Event Tickets 4.6 and up. If you decide to roll back to an older version, please make sure you try it out in a staging environment and make a full backup of your site, so in case anything breaks you can restore your site.

I’m really sorry this is being such a pain to your client. I can totally understand your frustration. Rest assured we take this issue very seriously (as well as all others) and we are actively working on a fix.

Let me know how it goes and if you have other questions in the meantime.

Best,
Victor

[Victor]

Hi Greg!

Glad to know it worked out for you! Thanks for following up to let me know about it.

I’ll close this thread now, but feel free to open a new topic if anything comes up and we’ll be happy to help.

Cheers,
Victor

[Victor]

Hi Roy!

Glad to know you could solve the issue. Thanks for following up to let us know about it.

I’ll close this now, but feel free to open a new topic if anything comes up and we’ll be happy to help.

Best,
Victor

[Victor]

Hi Zeljko!

I’m sorry for the delay in getting back to you.

I have just checked the report for the performance issue and it seems a filter is going to be added to prevent the large SQL query from being called that causes that specific performance issue in Events Calendar PRO 4.4.19.

I can’t commit to a date for when this will be available, but there is a chance that will be included in our next maintenance release. We will keep you posted about it.

Thanks for your patience.

Best,
Victor

[Victor]

Hi David,

My apologies for the delay in getting back to you.

Thanks for chiming in here and sharing that workaround.

Unfortunately, I cannot commit to a date for a fix yet, but rest assured we will fix this and will notify you in this thread once a fix is released.

For the time being, I will raise the priority of the ticket

We appreciate your patience while we work on this.

Best,
Victor

[Victor]

Hi Mark!

Thanks so much for taking your time to report this.

This is indeed a warning that pops up when using PHP version 7.2, which is the latest. We are aware of some adjustments that we need to make in the code to prevent these type of warnings.

It does not necessarily mean something is not working (if it does affect functionality please let us know) but is definitely something that we should address, so I have created a report for this issue and link it to this thread.

I have set this thread’s status to “Pending fix”, so we will notify you once a fix is released in one of our next maintenance releases of our plugins.

We will keep you posted about it.

Best,
Victor

[Victor]

Hi Kevin!

Thanks for taking your time to report this.

I have indeed been able to replicate the issue. It seems to be happening when child categories are present in the filters and it shows up many times because it triggers that part of the code for each child category.

I will log a bug report for this and link to this thread so we can let you know once fixed in one of our next maintenance releases.

For the moment, disabling the WP_DUBUG_DISPLAY will hide those notices as you might already know from the related thread.

I apologise for the inconvenience and we appreciate your patience while we work on this.

Best,
Victor

[Victor]

You’re welcome Kimberly! Thanks for following up with this and marking it as Resolved 🙂

I’ll close this now, but feel free to open a new topic if any other questions.

Cheers,
Victor

[Author]

Posts