• Resolved jerrystewart99

    (@jerrystewart99)


    Before updating plugins I always make a copy to localhost in an abundance of caution. I use Laragon as my localhost server.

    I have a free version of The Events Calendar and also Event Tickets both need an update 6.05->6.1.1 and 5.5.4->5.6.0 respectively

    Upgrading TEC and ET using the WordPress Dashboard interface in either order results in a fatal error. (see below for stack trace)

    However, if I upgrade both together by manually copying files, I can upgrade successfully. Also, if I deactivate both plugins, upgrade both then re-activate them it is also successful.

    I also have Restrict Content Pro installed. I mention this because RCP is mentioned in the Stack Trace of the fatal error. I have not touched the RCP plugin during this process.

    I’d appreciate some clarity. Thank you, Jerry

    Extract from debug.log file

    [18-Jun-2023 23:02:48 UTC] PHP Fatal error: Uncaught Error: Class ‘tad_DI52_ServiceProvider’ not found in C:\laragon\www\XXXXXXX\wp-content\plugins\restrict-content-pro\core\includes\PUE\Provider.php:22

    Stack trace:

    #0 C:\laragon\www\XXXXXXX\wp-content\plugins\event-tickets\vendor\composer\ClassLoader.php(444): include()

    #1 C:\laragon\www\XXXXXXX\wp-content\plugins\event-tickets\vendor\composer\ClassLoader.php(322): Composer\Autoload\includeFile(‘C:\laragon\www\…’)

    #2 [internal function]: Composer\Autoload\ClassLoader->loadClass(‘RCP\PUE\Provide…’)

    #3 [internal function]: spl_autoload_call(‘RCP\PUE\Provide…’)

    #4 C:\laragon\www\XXXXXXX\wp-content\plugins\the-events-calendar\common\vendor\vendor-prefixed\lucatume\di52\src\Builders\ClassBuilder.php(83): class_exists(‘RCP\PUE\Provide…’)

    #5 C:\laragon\www\XXXXXXX\wp-content\plugins\the-events-calendar\common\vendor\vendor-prefixed\lucatume\di52\src\Builders\Resolver.php(233): TEC\Common\lucatume\DI52\Builders\ClassBuilder->__construct(‘RCP\PUE\Provide…’, Object( in C:\laragon\www\XXXXXXX\wp-content\plugins\restrict-content-pro\core\includes\PUE\Provider.php on line 22

    • This topic was modified 1 year, 9 months ago by jerrystewart99. Reason: further information
Viewing 5 replies - 16 through 20 (of 20 total)
  • @abuzon I installed the updated Events Calendar and that was fine. But the Event Tickets / Event Tickets Plus update still causes the crash.

    I’m having the same issue when trying to go into TEC Settings

    The Events Calendar – Version 6.1.2.2?

    Fatal error: Uncaught TEC\Common\Exceptions\Not_Bound_Exception: TEC\Common\StellarWP\Telemetry\Opt_In\Opt_In_Subscriber => Error while making TEC\Common\StellarWP\ContainerContract\ContainerInterface $container: parameter $container is not optional and its type (TEC\Common\StellarWP\ContainerContract\ContainerInterface) cannot be resolved to a concrete class. in C:\Program Files\Ampps\www\wp-content\plugins\event-tickets\common\src\Common\Contracts\Container.php:27 Stack trace:

    0 C:\Program Files\Ampps\www\wp-content\plugins\event-tickets\common\src\Common\Telemetry\Telemetry.php(487): TEC\Common\Contracts\Container->get()

    1 C:\Program Files\Ampps\www\wp-content\plugins\event-tickets\common\src\Common\Telemetry\Telemetry.php(166): TEC\Common\Telemetry\Telemetry->register_tec_telemetry_plugins()

    2 C:\Program Files\Ampps\www\wp-content\plugins\the-events-calendar\src\Events\Telemetry\Telemetry.php(90): TEC\Common\Telemetry\Telemetry->init()

    3 C:\Program Files\Ampps\www\wp-content\plugins\the-events-calendar\src\Events in C:\Program Files\Ampps\www\wp-content\plugins\event-tickets\common\src\Common\Contracts\Container.php on line 27

    There seems to be a problem with the newest updates, see my comment prior on the 23rd of June and also @dunbehavin and @spiralx their comments. Same cause of the error: Class ‘tad_DI52_ServiceProvider’ not found! Disabling some of the extensions may work, but this is not a favorable solution. Is there a solution for this?

    Thread Starter jerrystewart99

    (@jerrystewart99)

    I agree with @satorius91, TEC settings (admin) screen causes a fatal error as they reported.

    This seems to be a different error than I first reported. This is not the tad_DI52_ServiceProvider problem now.

    I have TEC 6.1.2.2, Event Tickets 5.6.1.2 and Restrict Content Pro 3.5.34 (all latest version). I’ve deactivated ET and RCP. TEC now crashes all by itself. This does not appear to be a plugin clash problem like the previous error.

    My stack trace is:

    [26-Jun-2023 09:56:22 UTC] PHP Fatal error: Uncaught TEC\Common\Exceptions\Not_Bound_Exception: TEC\Common\StellarWP\Telemetry\Opt_In\Opt_In_Subscriber
    => Error while making TEC\Common\StellarWP\ContainerContract\ContainerInterface $container: parameter $container is not optional and its type (TEC\Common\StellarWP\ContainerContract\ContainerInterface) cannot be resolved to a concrete class. in C:\laragon\www\XXXXXXX\wp-content\plugins\event-tickets\common\src\Common\Contracts\Container.php:27
    Stack trace:

    0 C:\laragon\www\XXXXXXX\wp-content\plugins\event-tickets\common\src\Common\Telemetry\Telemetry.php(487): TEC\Common\Contracts\Container->get(‘TEC\Common\Stel…’)

    1 C:\laragon\www\XXXXXXX\wp-content\plugins\event-tickets\common\src\Common\Telemetry\Telemetry.php(166): TEC\Common\Telemetry\Telemetry->register_tec_telemetry_plugins()

    2 C:\laragon\www\XXXXXXX\wp-content\plugins\the-events-calendar\src\Events\Telemetry\Telemetry.php(90): TEC\Common\Telemetry\Telemetry->init()

    3 C:\laragon\www\XXXXXXX\wp-content\plugins\the in C:\laragon\www\XXXXXXX\wp-content\plugins\event-tickets\common\src\Common\Contracts\Container.php on line 27

    The last stable versions I have are from 22 April as follows:

    RCP 3.5.24.1, TEC 6.0.5, ET 5.5.4

    This is less than ideal

    I’m left wondering if IThemes or whoever runs the show these days actually has a QA department.

    The problem is still present with the latest Restrict Content Pro update. Activating it causes the above fatal error

    • This reply was modified 1 year, 8 months ago by kemseione.
Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Fatal Error when updating TEC to 6.1.1 with Events Tickets’ is closed to new replies.