Opened 7 years ago
Closed 5 years ago
#3632 closed enhancement (fixed)
Add or link detailed PHP Extension Recommendations from Requirements page
Reported by: | kirasong | Owned by: | coffee2code |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | General | Keywords: | needs-patch |
Cc: |
Description
As a part of writing hosting best practices docs, the hosting community team audited WordPress for PHP extension use and documented the extensions that are recommended in the hosting handbook.
Since this isn't very discoverable, I'm opening this ticket to discuss how we might make it more so.
Initially, I think it might belong in, or in a subsection of: https://wordpress.org/about/requirements/
If not, it could be a link from there, or something else entirely. Thoughts?
Change History (11)
This ticket was mentioned in Slack in #hosting-community by mike. View the logs.
7 years ago
This ticket was mentioned in Slack in #hosting-community by mike. View the logs.
6 years ago
This ticket was mentioned in Slack in #hosting-community by mike. View the logs.
6 years ago
#5
@
6 years ago
Hey there! Sorry, Konstantin -- missed this on when you first commented. Apparently I've got to fix notifications.
I think something similar to this would work fine to get things started:
Following "That said, we can’t test every possible environment and each of the hosts on our hosting page supports the above and more with no problems.":
"For detailed PHP extension recommendations, see the Hosting Handbook."
This ticket was mentioned in Slack in #hosting-community by ataylorme. View the logs.
6 years ago
#9
follow-up:
↓ 10
@
6 years ago
The hosting handbook recommends installing mcrypt
extension "for the sake of completeness".
It has been deprecated in PHP 7.1.0 and was removed in 7.2.0. Sure, there's a PECL version available, but I wouldn't call hosting best practices recommending installing it.
#10
in reply to:
↑ 9
@
6 years ago
Replying to skithund:
The hosting handbook recommends installing
mcrypt
extension "for the sake of completeness".
<snip>
Thanks for the note! This is definitely not the intent of the wording. That section is meant to document other modules WordPress could use, but won't under optimal/best practice setup.
Specifically, the handbook says:
For the sake of completeness, below is a list of the remaining PHP modules WordPress may use in certain situations or if other modules are unavailable. These are fallbacks and not needed in an optimal environment, but installing them won't hurt.
How do you think we should reference them?
Happy to take suggestions for a change here, or you can submit a pull request on GitHub.
I think linking to it would probably be the best first step. Do you have a copy suggestion for me that would include that link?