FATAL error -STILL- exists in 6.1.1

I wasn’t getting any errors in 6.1.0.2, but as of 6.1.1, I’m now getting warnings all over the back end of my site to the tune of:

Warning: file_get_contents(/the-events-calendar/the-events-calendar.php): failed to open stream: No such file or directory in [redacted]/public_html/wp-includes/functions.php on line 6651

Is this related?

Sorry for my evident frustration above, but I’ve been programming for 44 years now, so I feel I’m entitled. (Or, maybe just old: I was the first third-party developer ever hired by Apple, back in 1978. )

Releasing an update that takes a site completely off the air is embarassing enough, but then to do it twice in the same day? Someone there needs to get a grip. A couple of weeks ago, I pointed out that your code is only barely compatible with PHP 8, which came out almost three years ago!

Keeping up with libraries is BOOORRRRING, I know.Been there; done that. But failing to do so leads to situations like this, which I guarantee you will only get worse!

Time to put on your big-boy pants: some people’s livlihood depends on your software working.

I got the site back up by reverting to all the -previous- versions of EC and ET.

Let me know when you’re ready to beta test the next revision…

Same situation, my ticket for ‘nothing is bound’ was mark resolved and saying me to upload the 2 plugins. Error still here after their update

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

Hi @tvalleau @daivernon, really sorry to hear about this. Letting you know that this is our highest priority at the moment, and we appreciate you working with us regarding this issue.

A couple more information I would need here, versions of the following:

• PHP
• WordPress
• Theme and Version

Lastly, by any chance, were you able to do the testing for conflicts? Is there any third-party plugins that might have caused any issues? Please kindly include and share it with us, including its version.

Please do not share any credentials, as always this is for us to follow the WordPress Forum Guidelines.

Appreciate your patience, and looking forward to your response, this would definitely help us further.

Best,
Abz

Hi @redcapscorner, thanks for bringing this to our attention. This could also be related, and we’re also investigating this. I have another user who shared the same issue regarding file_get_contents.

Could you also share the information asked in my previous response? Thank you so much. Looking forward to you response.

Best,
Abz

Conflict seem to be with : Avada Builder Version 3.10.1
(Avada is a partner of Event Calendar in my mind)

PHP Version : 7.4.33
Avada Theme : 7.10.1
Avada Core : 5.10.1 
Avada Builder : 3.10.1
Event Calendar : 6.1.1
Event ticket : 5.6.0

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

@daivernon thank you so much for actually taking the time and doing the conflict testing, it helps us narrow down the problem so we can release a fix for all customers. I will start investigating why Avada Builder is causing this issue.

@redcapscorner thank you for reporting that issue, we are working on a solution to the file_get_contents problem. After some extra debugging I was able to reproduce it locally. It’s a specific activation route that causes this to happen.

@tvalleau Thank you for all your feedback. Unfortunately for everyone the issue you are reporting was not happening on any of our testing, as @daivernon mentioned it seems to be a compatibility problem, which is something I mentioned to you and other customers on the thread I marked as Resolved since we resolved all the issues that could have been causing this problem from our codebase and we needed some more information to try to solve.

• This reply was modified 1 year, 5 months ago by Gustavo Bordoni. Reason: Change an answer to a customer

Trying to help, I went right to where the error was located: /wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Builders/ClassBuilder.php

I did look around. FTP’d in and looked for the lucatume directory. (Is not lucatume support for codeception/ wp-browser, which is used for testing and debugging? Did you accidentally leave testing code in place?)

During that time, I did notice a difference between the previous and current version of event-tickets:

in the previous/working version of the plugin (5.5.11.1), the directory lucatume is at wp-content/plugins/event-tickets/common/vendor/lucatume
but in the new version (5.6.0) it has been moved one directory deeper: and puts the directory at wp-content/plugins/event-tickets/common/vendor/VENDOR-PREFIXED/lucatume

Did the calling code get adjusted for this changed directory path?

I also noted in my, and others, reports a lot of “nothing is bound to the ‘tickets.attendee_registration’ (or some name) id and it’s not an existing or instantiable class” and or “nothing is bound to the ‘tickets.cache-central’ id ” There are a LOT of unbound IDs reported. It’s the same basic error, with different classes. Did some header not get included? Is the aforementioned directory path possibly causing this?

Hi @tvalleau,

Yeaps that is the main error that is being reported. It’s not something specific to a header or inclusion it has more to do with Order of Operations, we modified the code to use a new version of a Module that we use for loading Just in Time, which caused some bugs due to legacy pieces of the code not waiting for their time to load.

When I mean that this was an edge case, was due to how we cannot get this reproduced easily, until we found that most users facing this problem have it related to using the legacy views for the Tickets UI.

Check if you have the following TRIBE_TICKETS_NEW_VIEWS constant which we found to be one of the culprits.

We need to run tests to make sure we have this properly fixed.

On your case, where does the error show up? Is there a specific moment where you see the error or does it show up on all pages?

Were you able to run the Conflict resolution testing?

Best Regards,

I can setup a clone staging environnement with admin credentials / ftp for your team. Let me know if could be helpful to reproduce bug (will be a specific case but who know’s ^^)

• This reply was modified 1 year, 5 months ago by daivernon. Reason: check email notification
• This reply was modified 1 year, 5 months ago by daivernon.

Check if you have the following TRIBE_TICKETS_NEW_VIEWS constant

Where would it be if I have it. Which file?

On your case, where does the error show up? Is there a specific moment where you see the error or does it show up on all pages?

It shows up by the entire site crashing hard IMMEDIATELY after it’s installed. There is no error appearing: the site just goes OTA.

Were you able to run the Conflict resolution testing?

No. Site (photography.org) is world-famous and busy. Has full automation of billing, memberships, sales and so on. Plugin tests would require many hours and take the site off the air.

@daivernon we cannot ask for customers admin credentials here on the forum under any circumstance, I am sorry.

I would be super helpful if you could set that staging website and run the Conflict resolution testing I mentioned. It would give us a bunch, just to make there isn’t any other plugins that might be causing the issue. Since we tested with Avada on those versions and couldn’t reproduce the issue.

@tvalleau I was hoping you had a Staging site where the problem was happening that we could test to figure out your problem. In any case, that constant would be on your wp-config.php. 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

TRIBE_TICKETS_NEW_VIEWS does not appear in our wp-config file.

we are running:

event-tickets-plus.5.6.10
event-tickets.5.5.11.1
events-calendar-pro.6.0.12.1
the-events-calendar.6.0.13

in order to keep the site up.

@Gustavo Bordoni for sure not sending credential here, let me know if you can a ticketing URL where sending it or a devteam email.

The issues caused by this are very bad on our school’s site.
Warning: file_get_contents(/the-events-calendar/the-events-calendar.php): failed to open stream: No such file or directory in /home/customer/www/domianname.org/public_html/wp-includes/functions.php on line 6651

Made a new post to our blog and it kicks back a page not found plus showing the above error message on the back end of our site.

When do you foresee a update fix coming out?