[Barry]

OK, I’m sorry to hear that but it may be the most pragmatic way forward. One other note, if you do want to revisit this, is that references to TribeEventsQuery would need to be changed to:

Tribe__Events__Query

(Otherwise, following recent changes, WordPress will not be able to successfully “unhook” those items.)

Could I get a download of the Events Calendar 3.9.2? or whatever the latest version was before the current version?

You should be able to download all previous versions (that your licenses entitled you to) over here – and we’re generally happy to offer up access to other previous versions where needed – just let us know, here or in a new topic, if we can help on that count.

Thanks again 🙂

[Barry]

Hey again Tony,

We’re looking at this in a little more depth and wondered if you’d be comfortable sending us a database dump?

Lots of database tools such as phpMyAdmin will help you to do this (and alternatively something like the Duplicator plugin would give us a database dump as part of a bigger package – and is quite easy to use).

If you are open to doing this, would you be able to upload the resulting file to a suitable location (whether your WP site, Dropbox or some similar service) and share a download link by private reply?

Thanks!

[Barry]

Hey Tony,

When I review your system information (that you shared when you opened this post) I see no reference to our new month view caching setting.

Can you visit Events → Settings → Display and check to see if Enable the Month View Cache has been checked and check it if it has not already been enabled (then save the changes)? That may not solve this immediately if the cache cannot be generated owing to the timeouts, but it could be worth a shot.

[Barry]

Hi Joe,

Sorry that didn’t work.

If the same code works on other sites, perhaps something else local to the problematic site is getting in the way?

What differences can you identify (different plugins/themes/customizations) and can you try temporarily switching to a setup you know works with this slider (perhaps that would be our plugins, the slider plugin and an unmodified default theme such as Twenty Fifteen) – confirm if it works then and then build back up to your full stack of plugins – testing at each stage to see if the problem has been reintroduced?

[Barry]

It’s possible the theme is the cause for sure, especially if they ship complete with customizations targeting The Events Calendar and Events Calendar PRO, which is quite possible here.

If you suspect that might be the case (and if, for instance, the problem disappears when you switch to a default, unmodified theme like Twenty Fifteen that strongly suggests it is the theme) then it probably is worth both connecting with the theme authors and waiting for an update on that count.

[Barry]

My pleasure 🙂

I’ll go ahead and close out this topic since we can’t go into too much more detail on a customization task like this one, but we’re here to help if any other issues crop up – just post a new topic and one of the team will be only too happy to assist.

Thanks again!

[Barry]

Hi M,

What I see (as a logged out user) is the login screen. If you want to open submissions up to everyone, you can – please just visit Events → Settings → Community and check the “Allow anonymous submissions” box (remember to save your changes!).

You can learn more about this and other Community Events settings by reading this post (linked to from the New User Primer).

I hope that helps 🙂

[Barry]

That is odd.

It does look to me as if your theme ships with a set of custom templates (contained in a tribe-events directory of its own) – could it be one of these has fallen out of date, or a change made their broke this functionality?

Can you try temporarily removing those (or rename that subdirectory to something like __unused_tribe-events) then test to see if the issue is resolved. This would give us a better handle on the source of the problem.

[Barry]

Hi Ray,

Our apologies first of all for the disruption.

Question 1) Why does a unstable version is automatically updated?

We always go to great pains to test new versions before releasing them and this was no exception – it’s definitely possible some things slipped through the net and of course that was not our intention – but we certainly wouldn’t want to trigger unnecessary problems.

That said, let’s take a look at this problem in more detail as it may not be a fault within our plugins.

Now there is a fatal error.

I don’t really have enough information to help you diagnose this just yet. Where is the problem happening (on which page) – is it the result of some custom code, do you know? Our full troubleshooting steps could help you to determine this.

tribe_is_week() has not been removed and is still available for use, so I’m particularly interested to learn about why this is happening (perhaps it is being called too early in the request, for example).

Could you also share your system information – in a private reply – to help build our picture of the issue? Thanks!

[Barry]

Hi Joe,

I’m sorry you’ve had a rough ride after updating.

One thing that jumps out is the use of old class names, like TribeEvents – this should be updated to:

Tribe__Events__Main

We were conscious of backwards compatibility when making this change and actually you should still be able to use the old class names. If you happen to have the display of errors turned on it is certainly possible the resulting warnings could get in the way of the slider’s operation, but generally you should not display errors on a live website.

At any rate, can you try making that change? (As a sidenote, please share code via Pastebin, Gist or some similar service and paste the link in here rather than sharing it directly in forum topics 🙂 )

[Barry]

Hi brendakato,

Would you be able to share, by private reply if you prefer, a copy of your System Information? This can be found at the bottom of the Events → Help screen – more information on finding it is provided here.

[Barry]

So before we go any further, would you be able to upgrade to our current release (3.10) for both The Events Calendar and Events Calendar PRO?

[Barry]

I think that’s fine, it gives me a good sense of the scale (and type) of events you are dealing with. Bear with me a little longer, I’m going to compare notes with some fellow team members and we’ll figure out a further course of action from there.

[Barry]

Ah, I see.

So if the product is actually a ticket then by default WooCommerce Tickets will try to “redirect” it to the related single event page.

In this case, my guess is that single event no longer exists. It also looks like you were trying to use ticketing with a recurring event, which isn’t fully supported – that coupled with the fact the event seems to no longer exist is probably at the root of this.

(Plus, since the event no longer exists customers should not be able to locate that product, assuming the visibility setting has not explicitly been changed.)

Does that match up with what you see in the site itself?

[Barry]

…As a quick update, we did receive your second email (with no subject) so hold tight and one of the team will get back to you as soon as they can (at this point in the day, that’s likely to be tomorrow) 🙂

[Author]

Posts