PHP 8.4 issue

  • 7thcircle

    (@7thcircle)


    2 days, 5 hours ago

    TEC\Common\StellarWP\Uplink\API\Client::validate_license(): Implicitly marking parameter $key as nullable is deprecated, the explicit nullable type must be used instead
    wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/API/Client.php:197

    TEC\Common\StellarWP\Uplink\Resources\Resource::__construct(): Implicitly marking parameter $license_class as nullable is deprecated, the explicit nullable type must be used instead
    wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Resources/Resource.php:158

    TEC\Common\StellarWP\Uplink\Resources\Resource::register(): Implicitly marking parameter $license_class as nullable is deprecated, the explicit nullable type must be used instead
    wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Resources/Resource.php:481

    TEC\Common\StellarWP\Uplink\Resources\Resource::register_resource(): Implicitly marking parameter $license_class as nullable is deprecated, the explicit nullable type must be used instead
    wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Resources/Resource.php:501

    TEC\Common\StellarWP\Uplink\Resources\Plugin::register(): Implicitly marking parameter $license_class as nullable is deprecated, the explicit nullable type must be used instead
    wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Resources/Plugin.php:172

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Darian

    (@d0153)

    2 days, 2 hours ago

    Hi @7thcircle

    Thanks for reaching out and for providing more details about the issue you’re experiencing.

    After reviewing the behavior, I can confirm that this appears to be a valid issue. I’ve created an internal bug ticket for our team to investigate further, and I’ve added your case to it so you’ll be notified when a fix becomes available.

    As a temporary workaround, you can add the following to your wp-config.php file:

    define( 'WP_DEBUG', false );

    Please note that this disables WordPress debugging, so you may want to re-enable it when debugging is needed.

    Rest assured, we’ll update this thread once the issue has been resolved. Thank you for your patience while our team works on this.

    —-
    Internal Bug Ticket Reference: SMTNC-2001

    Thread Starter 7thcircle

    (@7thcircle)

    2 days, 2 hours ago

    I am aware that I can disable debugging. While it is off in production, on my dev site where I am testing to see if your plugin is finally updated I have it on so I can determine if I can update to newer versions of PHP.

    Plugin Support Darian

    (@d0153)

    1 day, 12 hours ago

    Thanks for the clarification, @7thcircle. That makes perfect sense, especially since you’re using the dev site to test PHP compatibility. Keeping debugging enabled there is definitely helpful for identifying any compatibility issues.

    Please feel free to reach out if you encounter anything else during your testing.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.