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

Update rules for determining minimum PHP version for brand plugins #30

Open
wpscholar opened this issue Jul 22, 2024 · 0 comments
Open

Comments

@wpscholar
Copy link
Member

This is our current rule:

If WordPress currently recommends PHP 7.4, we support two versions prior, which would be 7.2.
See

### PHP
WordPress provides recommendations and minimums.
At writing (January 2023), [WordPress recommends](https://wordpress.org/about/requirements/) PHP 7.4 and supports 5.6.20+.
We currently support two point releases below WordPress' recommendation -- all our products must work 100% two point releases below the recommendation.
We expect our code to execute error-free in any minimum version WordPress supports. However, we do not expect our products to be fully-functional or even functional with PHP 5.x. Reduced functionality or throwing up an upgrade screen are both acceptable if faced with writing PHP 5.x-7.1 compatible code.

We should probably create a clearer rule regarding PHP versions that take into account a few things:

If we apply all these rules without hosting-level PHP version stats, we're looking at PHP 7.2 as our lowest supported version. However, for Bluehost and HostGator we support 7.3+. That said, I think we should be fine to support PHP 7.3+ for all plugins, given the only rule that would dictate we support 7.2 would be if we support the lowest compatible version for the last 3 WP versions. If we ignore that rule the minimum becomes 7.3+ based on usage stats. Unless the hosting stats show otherwise, we'll use what we have from Hiive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant