wpdev b515b8441e fix(2meet-data-optimizer-hivepress-addon): keep HivePress transients in the object cache when there is one ...

- With a persistent object cache (wp_using_ext_object_cache(), Redis on the HivePress sites) the transient filter stores HivePress's per-post transient pairs in the tmdo_hp_transient cache group instead of wp_options, where they piled up (1.15 M rows on dev36). Reads fall back to wp_options for values written before; deletes clear both. Without an object cache nothing changes.
- Verify: HivepressTransientFilterTest object-cache cases (RED before); dev36 with Redis: update/get/delete_post_meta on an HP transient key leaves 0 rows in wp_options and postmeta.
- PR: PR-081

2026-09-27 09:00:03 +08:00

..

integration

fix(2meet-data-optimizer-hivepress-addon): keep HivePress transients in the object cache when there is one

2026-09-27 09:00:03 +08:00

unit

refactor(2meet-data-optimizer-hivepress-addon): leave HivePress queries to the post router

2026-09-26 20:19:27 +08:00

bootstrap.php

refactor(2meet-data-optimizer-hivepress-addon): remove TMDO_HPCT_Import

2026-09-26 00:16:00 +08:00