PHP 8 deprecations

Hi @eclev91,

Thank you for reporting these deprecated notices.

While we’re actively working on ensuring full compatibility with PHP 8.1 and 8.2, our plugins are not yet fully compatible with these versions.

WordPress also provides beta support for PHP 8.1 and 8.2 and full compatibility is expected with the next WordPress release.

We appreciate your feedback and we are committed to providing the best possible experience for our users.

For more information, please refer to the following knowledge base article → PHP 8.1 Support

Thank you for your patience and understanding.

I appreciate that WP support for newer PHP versions is “beta”, but their usage of that term is not in line with industry usage and is sort of made up and in flux. In fact, one criteria is adoption of newer versions of PHP, and if third-party plugins are noisy on newer versions, developers are less likely to push clients to update to newer versions of PHP. This self-reinforcing cycle perpetuates “beta” support.

I would love to see these items cleaned up to create a more positive developer experience, regardless of the state of core WP.

Hi @eclev91,

WordPress’s “beta” designation for PHP 8.1 and 8.2 support reflects the ongoing development and testing process to ensure complete compatibility with these PHP versions. While it’s not yet fully compatible, WordPress is actively working towards this goal.

The deprecated notices you’re encountering are part of this compatibility process. They indicate that certain aspects of the plugin code are no longer compatible with newer PHP versions and may need to be updated. These notices serve as reminders to developers to address these compatibility issues in future releases.

I appreciate your feedback regarding the industry usage of the term “beta” and its potential for confusion. It’s true that the term “beta” in this context may not align with the traditional software development lifecycle. However, WordPress uses it to convey the ongoing efforts to ensure full compatibility with newer PHP versions.

I understand your frustration with the noisy behavior of plugins on newer PHP versions. This can discourage developers from pushing clients to update to newer PHP versions, perpetuating the “beta” support cycle.

Ideally, plugins should strive to be compatible with the latest stable PHP versions and minimize these deprecated notices to provide a smoother developer experience. This requires continuous development and testing efforts from plugin developers.

I hope that plugin developers will prioritize addressing these compatibility issues and provide a more positive developer experience in future releases. In the meantime, you can continue reporting these deprecated notices to bring them to our attention.

Thank you for your understanding and for contributing to the improvement of plugin compatibility with newer PHP versions.

Hi @eclev91

Thank you for patiently waiting.

We would like to inform you that we have an update available that should address the problem you reported. It would be helpful if you could update your plugin to the latest version, and please let us know if the issue is resolved on your end.

As always, please test it first on a staging site before applying to your live site.

It does look like that resolved many PHP 8 deprecations. We have since moved toward using 8.2 on our sites, since 8.0 is officially EOL while 8.1 is now security updates only with 11 months until EOL.

On 8.2, there are still outstanding deprecations. But I appreciate your continued attention to the codebase and keeping it updated!

Deprecated: Creation of dynamic property Tribe__Tickets__Main::$plugin_slug is deprecated in /plugins/event-tickets/src/Tribe/Main.php on line 146

Deprecated: Creation of dynamic property Tribe__Tickets__Main::$registered is deprecated in /plugins/event-tickets/src/Tribe/Main.php on line 452

Deprecated: Creation of dynamic property Tribe__Tickets__Tickets_Handler::$path is deprecated in /plugins/event-tickets/src/Tribe/Tickets_Handler.php on line 108

Deprecated: Creation of dynamic property Tribe__Tickets__REST__V1__Messages::$messages is deprecated in /plugins/event-tickets/src/Tribe/REST/V1/Messages.php on line 18

Hi @eclev91

I’m reaching out to let you know that we’ve created an internal ticket to address the issue you reported, and we’ve included your case in it.

Unfortunately, we don’t have an estimated time for when the issue will be resolved, but we’ll keep you updated as soon as a solution becomes available.

—
Internal Bug Ticket Reference: GTRIA-1136

Hi there,

We’re happy to inform you that the mentioned bug ticket GTRIA-1136 / ET-1950 was already fixed and included in the Event Tickets plugin release.

Please update the Event Tickets plugin on your end, and that issue will not be present anymore.

Hi there,

It seems like this thread has been quiet for a bit, so we’ll go ahead and mark it as resolved. However, if any further questions or concerns come up, please don’t hesitate to start a new thread.