docs(2meet-data-optimizer): add PR-116 and PR-117 to the 1.3.0 release notes

- routed count cache: placeholder escape and count version group - PR: PR-101 (follow-up)
2026-09-27 17:58:07 +08:00
parent ca2cbdab65
commit 947e130386
2 changed files with 8 additions and 2 deletions
@@ -109,7 +109,7 @@ The Classifier tab analyzes your existing `wp_postmeta` data (access frequency,

 = 1.3.0 =
 * Declared flat-table indexes are added only from WP-CLI or WP-Cron, one process at a time (MySQL GET_LOCK); web requests schedule `tmdo_ensure_group_indexes`, and doctor lists indexes not added yet
-* Routed searches with post__not_in count from a cached base count minus the excluded posts (HivePress keyword + price search no longer slower than native)
+* Routed searches with post__not_in count from a cached base count minus the excluded posts; the cache key ignores wpdb's per-request placeholder escape and follows post saves and managed-key writes only, not every post meta write (HivePress keyword + price search no longer slower than native)
 * Rate-limited view requests sample their statistics (1 in 10) instead of writing an option each time
 * Logger info / notice lines only with WP_DEBUG_LOG (filter `tmdo_log_info`)
 * The public listings REST output withholds email, phone, address and IP fields even when declared public