Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP8.4 alpha 1 warnings - nullable is deprecated, the explicit nullable type must be used instead #38226

Open
ipajen opened this issue Jul 6, 2024 · 4 comments
Labels
[Package] Connection [Pri] Normal [Status] Priority Review Triggered The guild in charge of triage has been notified of this issue in Slack Triaged [Type] Bug When a feature is broken and / or not performing as intended

Comments

@ipajen
Copy link

ipajen commented Jul 6, 2024

Impacted plugin

Protect

Quick summary

PHP warning in PHP 8.4 alpha 1.

Deprecated: Automattic\Jetpack\Connection\Manager::setup_xmlrpc_handlers(): Implicitly marking parameter $xmlrpc_server as nullable is deprecated, the explicit nullable type must be used instead in C:\wamp64\www\wp\wp-content\plugins\jetpack-protect\jetpack_vendor\automattic\jetpack-connection\src\class-manager.php on line 171

nullable-deprecated

Steps to reproduce

  1. Use PHP 8.4 alpha 1 and WordPress 6.5 RC2 with Debug enabled
  2. Install and activate plugin Jetpack Protect 2.2.0

A clear and concise description of what you expected to happen.

No response

What actually happened

No response

Impact

Some (< 50%)

Available workarounds?

No but the platform is still usable

Platform (Simple and/or Atomic)

Self-hosted

Logs or notes

Environment

  • WordPress: 6.6-RC2
  • PHP: 8.4.0alpha1
  • Server: Apache/2.4.59 (Win64) PHP/8.4.0alpha1 mod_fcgid/2.3.10-dev
  • Database: mysqli (Server: 8.3.0 / Client: mysqlnd 8.4.0alpha1)
  • Browser: Edge 126.0.0.0 (Windows 10/11)
  • Theme: Twenty Twenty-Four 1.1
  • MU-Plugins:
  • Plugins:
    • Jetpack Protect 2.2.0
    • WordPress Beta Tester 3.5.5
@ipajen ipajen added [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Jul 6, 2024
@github-actions github-actions bot added [Status] Priority Review Triggered The guild in charge of triage has been notified of this issue in Slack [Plugin] Protect A plugin with features to protect a site: brute force protection, security scanning, and a WAF. [Pri] High labels Jul 6, 2024
@fgiannar fgiannar added Triaged [Package] Connection and removed Needs triage Ticket needs to be triaged [Plugin] Protect A plugin with features to protect a site: brute force protection, security scanning, and a WAF. labels Jul 8, 2024
@anomiex
Copy link
Contributor

anomiex commented Jul 8, 2024

We're already aware of this, but we've decided not to do anything about it until we drop support for PHP 7.0 since it's not possible to use ?Class in that version. At the latest that will come when WordPress 6.7 is released, at which time we'll drop support for WordPress 6.5.

@fgiannar
Copy link
Contributor

@anomiex Thanks for the update! If that's the case I guess we can remove it from Vulcan's board and add it in Garage's one as a future task to serve as a reminder?

@anomiex
Copy link
Contributor

anomiex commented Jul 10, 2024

That works, although I may forget this task exists when I fix the issue as part of the general dropping of PHP 7.0 and 7.1 support and/or enabling 8.4 in CI. 😀

Once we drop 7.0 we can remove what #36673 added to .github/files/phpcompatibility-dev-phpcs.xml and then CI will have us fix all these.

@jeherve
Copy link
Member

jeherve commented Jul 11, 2024

@anomiex I created #38296 so we can keep track of all those. Feel free to add to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Package] Connection [Pri] Normal [Status] Priority Review Triggered The guild in charge of triage has been notified of this issue in Slack Triaged [Type] Bug When a feature is broken and / or not performing as intended
5 participants