FATAL error -STILL- exists in 6.1.1

@Gustavo Bordoni staging environnent is ready. Just let me know how toa safely send credentials to your teams. I try create a support ticket but “thanks for contacting us! We will get in touch with you shortly. Just a reminder, we only offer premium support for current, active licenses.” ?? no hopes that i will be read

• This reply was modified 1 year, 5 months ago by daivernon.

I totally concur with @tvalleau. This is ridiculous on Events Calendar development team’s part: Why “brag” about a new rollout with Version 6.1.1., if it still contains errors that already were reported in at least two previous releases in the same week?

I have asked my website team to consider cancelling our PRO subscription and completely removing The Events Calendar from the website.

Totally crazy that these guys seem not to be testing thoroughly enough before new updates.

Help!
Version 6.1.1

(/the-events-calendar/the-events-calendar.php): failed to open stream: No such file or directory in /home/customer/www/susangiannantonio.com/public_html/wp-includes/functions.php on line 6651

Warning: file_get_contents(/events-calendar-pro/events-calendar-pro.php): failed to open stream: No such file or directory in /home/customer/www/susangiannantonio.com/public_html/wp-includes/functions.php on line 6651

Warning: file_get_contents(/the-events-calendar/the-events-calendar.php): failed to open stream: No such file or directory in /home/customer/www/susangiannantonio.com/public_html/wp-includes/functions.php on line 6651

Warning: file_get_contents(/events-calendar-pro/events-calendar-pro.php): failed to open stream: No such file or directory in /home/customer/www/susangiannantonio.com/public_html/wp-includes/functions.php on line 6651

Warning: Cannot modify header information – headers already sent by (output started at /home/customer/www/susangiannantonio.com/public_html/wp-includes/functions.php:6651) in /home/customer/www/susangiannantonio.com/public_html/wp-admin/admin-header.php on line 9

• This reply was modified 1 year, 5 months ago by susangiannantonio.

I’m also seeing this error after upgrading within the last day or so. Here’s the information you requested:
full error: [17-Jun-2023 23:20:12 UTC] PHP Warning file_get_contents(/the-events-calendar/the-events-calendar.php): failed to open stream: No such file or directory in [REDACTED]/wp-includes/functions.php on line 6651
WordPress 6.2.2
Multisite YES
PHP 7.4.33
Divi 4.2.1
The Events Calendar 6.1.1

I’ll also add that I’m another one who is looking for a different events plugin due to these error messages that have been ongoing now for a while.

@charmedchicken and @susangiannantonio we have a release ready to launch early next week, we are hoping for something early on Monday EST. But we need to make sure we test this properly before launching.

@webifiedone as I replied to you on the other thread, it’s near impossible to catch all the edge cases when it comes to third party modifications, we are trying to make sure customers are not facing this problem anymore. It would be amazing if you could provide us with some more information about your problem so we can engage in a productive conversation to fix your problem.

@daivernon If you mention me by name that it’s something that I need, one of our support crew will get it to me ASAP.

i open a ticket with title “To Gustavo Bordoni(@bordini)”

@bordoni: you say “But there are other possible ways of enabling the legacy views, another one might be a filter that could be added in a snippet, your functions.php and many other places.

add_filter( ‘tribe_tickets_new_views_is_enabled’, ‘__return_false’ );

The snippet above triggers the problem, so depending on how you activated it removing that would solve the problem”

I don’t understand what you are saying here. I don’t need to add a snippet to trigger the problem, I need the opposite: a snippet to stop the problem from occurring.

However, if as you said, it’s really a problem with your new JIT code, then a snippet is not likely to resolve it; that would just be a bandaid for one particular trigger.

As noted above, in order to prevent the White Screen of Death, and the site being TOTALLY unavailable, we have reverted to using the previous versions of all four plugins.

This error is apparently also causing all of my attendees lists to be blank, which we discovered when trying to begin our event yesterday. It shows that I have X tickets sold, but instead of attendees, I’m getting:

Warning: array_key_exists(): The first argument should be either a string or an integer in [redacted]/public_html/wp-content/plugins/event-tickets/src/Tribe/Status/Manager.php on line 417

Needless to say, my big events this weekend have been nightmarish, to the tune of an estimated $6,000 loss in revenue and irreparable embarassment and damage to my store’s reputation.

PHP: 7.4.33
WordPress: 6.2.2
Theme: Outreach Pro 3.1.2
Parent Theme: Genesis 3.4.0

So now that I check things across multiple client websites that I develop, It looks like EVERY site I have developed that uses this calendar and tickets add-on all have problems! I’ll wait till mid-week to see what your idea of a “fix” looks like. Because trying to tell people they caused issues using a added line of code to the functions.php file is wrong. Your entire platform has caused more harm since your big 6x “upgrade”. Anyway, what this means is depending on this coming week… you stand to loose 20+ paying clients. Will next week mark time to look for another alternative for events and tickets? or will you not release yet another sloppy update!

@bordoni Rob Ly from ticket support will give you credentials for staging environnement.

UPDATE : Avada has released a new version of his theme + plugins, but conflict still exist.

• This reply was modified 1 year, 5 months ago by daivernon. Reason: Avada release an update

@daivernon for sure, I dont think their release had anything to do with this.

We are planning to ship something today that should fix that problem.

We are finishing up a couple of rounds of tests to ensure the problem was fixed at least on the scenarios we confirmed.

@inspirationacademy if you are a paying customer, you really should reach out to us on the our support, there we will be able to possibly provide you with solution a little earlier.

Just to clarify in no way shape or form I said that the problem was caused by the customers actions, what I was suggesting is that there is an edge case we didn’t test that we are addressing on a release later today.

From the other topic I saw your comment the bug you are facing will be fixed.

Best regards,

We just released a new version of Event Tickets and Event Tickets Plus that should have the problem resolved.

If someone can confirm it would be amazing.

@gustavo. Fail. Exactly the same error with ET 5.6.0.1 as with ET 5.6.0.

I updated the ET and ETP. Still got WSOD with

"There has been a critical error on this website. Please check your site admin email inbox for instructions.

Learn more about troubleshooting WordPress."

Email says:

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.2.2
Active theme: Avada (version 7.9.1)
Current plugin: Event Tickets (version 5.6.0.1)
PHP version 8.0.2

Error Details

An error of type E_ERROR was caused in line 84 of the file /home/cpaorg/photography.org/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/ClassBuilder.php. Error message: Uncaught TEC\Common\lucatume\DI52\NotFoundException: nothing is bound to the 'tickets.cache-central' id and it's not an existing or instantiable class. in /home/cpaorg/photography.org/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/ClassBuilder.php:84
Stack trace:

0 /home/cpaorg/photography.org/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/Resolver.php(233): TEC\Common\lucatume\DI52\Builders\ClassBuilder->__construct('tickets.cache-c…', Object(TEC\Common\lucatume\DI52\Builders\Resolver), 'tickets.cache-c…')

1 /home/cpaorg/photography.org/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/Resolver.php(210): TEC\Common\lucatume\DI52\Builders\Resolver->resolveUnbound('tickets.cache-c…')

So, in Recovery mode I

upgraded to EC 6.1.1 from 6.0.13.1
and EC Pro to version 6.1.0 from 6.0.12.1

and got your message:

"To begin using Event Tickets Plus, please install (or upgrade) and activate Event Tickets (5.6.0+)." (5.6.0.1 is installed.)

Am tearing it all out yet again, and reverting to previous four releases.

To be absolutely clear: it is not ME taking the site offline. Installing ET 5.6.0.1 literally crashes the entire site. White Screen of Death.

Fix – Resolved issues with Attendee Registration not being bound correctly on loading. [ET-1771]

Avada : 7.11.0
Event Calendar : 6.1.1?
Event Ticket : 5.6.0.1?

Fatal error: Uncaught TEC\Common\lucatume\DI52\NotFoundException: nothing is bound to the ‘tickets.attendee_registration’ id and it’s not an existing or instantiable class. in /home/customer/www/cafedomoun.re/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/ClassBuilder.php:84 Stack trace: #0 /home/customer/www/cafedomoun.re/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/Resolver.php(233): TEC\Common\lucatume\DI52\Builders\ClassBuilder->__construct(‘tickets.attende…’, Object(TEC\Common\lucatume\DI52\Builders\Resolver), ‘tickets.attende…’) #1 /home/customer/www/cafedomoun.re/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/Resolver.php(210): TEC\Common\lucatume\DI52\Builders\Resolver->resolveUnbound(‘tickets.attende…’) #2 /home/customer/www/cafedomoun.re/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Container.php in?/home/customer/www/cafedomoun.re/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/ClassBuilder.php?on line?84

With the Event Tickets updates, I’m no longer seeing the general error messages all over the back-end of the site, but I’m still not able to access attendees lists. I get the following error:

Warning: array_key_exists(): The first argument should be either a string or an integer in [redacted]/public_html/wp-content/plugins/event-tickets/src/Tribe/Status/Manager.php on line 417