hardening 2.1: 2meet-data-optimizer-hivepress-addon 0.2.0 (staged rollout) #2
Reference in New Issue
Block a user
Delete Branch "hardening/2.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hardening 2.1 for
2meet-data-optimizer-hivepress-addon(version 0.2.0), released with2meet-data-optimizer1.1.0 (search-index mode, ADR-004 in core).Commits
Summary
optimize_query/optimize_searchare no longer bound while core's post router is active: core routes HivePress searches (filters and_sort) to the entity flat tables, and two routers would claim the same clauses.Verification
fe.sh9 URLs identical to native.Rollout
Deploy together with core 1.1.0 (staged, dev22 first);
plugins/is untouched by this merge.- Do not bind optimize_query / optimize_search on hivepress/v1/models/{listing,vendor}/{query,search} while core's TMDO_Post_Query_Router is active: core now routes HivePress searches (filters and _sort) to the entity flat tables, and two routers would claim the same clauses - Version 0.2.0 (released with core 1.1.0); CHANGELOG - Verify: composer test (144, +2 binding tests); integration 49; dev36 fe.sh 9 URLs ids == native (except known flat drift) - PR: PR-063