-
Notifications
You must be signed in to change notification settings - Fork 384
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
Omit page caching and object caching tests for Site Health if on WP>=6.1 #7643
Comments
Actually, since page caching detection is now part of Site Health in WordPress core, I think we can just remove our check entirely now, right? There is a filter that caching plugins can use to add recognition of their own headers, as noted in the support topic. |
For the impending release, we could just disable the tests by default. Then in the next release we could remove them entirely, if this would make it easier to get the release out the door. |
We are also using page cache tests internally. amp-wp/src/Admin/OptionsMenu.php Line 250 in a2d8418
|
Presumably these should be using what core has now for WP>=6.1. |
I need to dig in more but seems like it could be tricky to determine due to the visibility of methods. |
Ah yes. Well, in that case, we can just add a condition to only include the following tests if WP<6.1: amp-wp/src/Admin/SiteHealth.php Lines 183 to 186 in a2d8418
amp-wp/src/Admin/SiteHealth.php Lines 220 to 227 in a2d8418
The latter essentially already has such a test, but for WP 5.6. |
Feature Description
New description from @westonruter: The Site Health tests for page caching and object caching from the AMP plugin have been incorporated into WordPress core as of 6.1. See WordPress/performance#220 (Core-56041) and WordPress/performance#35 (Core-56040). At the very least these tests can be disabled in WP 6.1+. But I think it would be better to just remove them entirely.
Original description
We got a support topic where the user is getting a site health a warning for cache plugin, although he is using a cache plugin (Litespeed cache) because LiteSpeed uses a different header it's not able to detect it.
The Litespeed author suggested that we use a filter so that other vendors can pass their headers so it will fix warnings for their plugins.
Acceptance Criteria
No response
Implementation Brief
No response
QA Testing Instructions
No response
Demo
No response
Changelog Entry
No response
The text was updated successfully, but these errors were encountered: