Repository navigation
v1.62.0
What's Changed
Added
- Site Health check
package_assets_reachable(Health\Check\PackageAssetsReachable,
categorytimber-kit, needs$site_health). It is registered only when
$admin_resizable_sidebaristrue. It sends an anonymousHEADrequest
to the sidebar stylesheet thatpackageAssetUrl()builds. Any answer other
than 200 is repeated asGET. 200 is good. 403 or 404 isrecommendedand
names both causes with a fix for each: a theme.htaccessthat denies
vendor/without the static-file allow rule, and avendor/directory the
web server user cannot enter. A 403 body that containsServer unable to read htaccess filepoints to the second cause. A failed loopback is
recommended("could not verify"), never critical. Neither request follows
redirects, so a redirect to a login page or a soft-404 handler is reported as
unverified, not as a healthy stylesheet.
Changed
search_post_type_filter()is hooked only when$disable_searchisfalse.
With the search disabled, the main search query is a 404 and the filter had
nothing to scope. A project that sets$disable_search = falsegets the same
behaviour as before. A project that callssearch_post_type_filter()itself
is not affected.
Fixed
search_post_type_filter()rewrotepost_typeon everyWP_Querywith a
search term, not only on the frontend search. REST searches
(/wp/v2/pages?search=,/wp/v2/media?search=,/wp/v2/search),
get_posts()and WP-CLI got$search_post_typesinstead of the type they
asked for. In the block editor the "Parent" picker listed posts instead of
pages, and the media picker found nothing. The filter now acts on the main
query only, the same guarddisable_search()has. A frontend/?s=request
is unchanged. A theme that relied on the filter for a secondary search query
must now passpost_typeitself.
Pull Requests
- #211 — fix(search): limit search_post_type_filter to the main query
- #213 — feat(health): report package assets that vendor/ does not serve
Full Changelog: v1.61.0...v1.62.0