wpdev/2meet-data-optimizer
1
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases 1 Wiki Activity
60 Commits 14 Branches 1 Tag
d86c0a7bac7d1d00370a29036cd5e3b4a380c9f1
Commit Graph

14 Commits

Author SHA1 Message Date
wpdev d86c0a7bac feat(2meet-data-optimizer): write flat-table data back to native meta 
- TMDO_Native_Restorer copies an entity's flat-table values into its native meta table so the value each key reads today is what native returns afterwards: the owning group (by post type for posts) wins, values are stored as WP stores them, NULL removes the native row
- Resumable per-group id cursor, catch-up pass for rows updated during the run, optional demote to dual_write; CLI wp tmdo bridge-restore-native <entity> [--dry-run] [--batch=<n>] [--demote]
- Verify: NativeRestorerTest (5, user) + NativeRestorerPostTest (2, scoped vs legacy routing); core unit 652 / integration 456, HP 148, WC 10 OK; scale estimate dev21 user ~5.1M / post ~4.0M flat rows
- PR: PR-031
 2026-09-26 00:44:53 +08:00
wpdev c84d2409b7 feat(2meet-data-optimizer): warn when HivePress / WooCommerce run without their AddOn 
- TMDO_Compatibility::missing_integration_addons() reports active HivePress / WooCommerce whose AddOn bootstrap class is absent
- Surface it as Site Health test wpdo_missing_integration_addons (also on the admin Doctor tab) and an administrator notice (TMDO_Missing_Addons_Notice)
- Verify: MissingIntegrationAddonsTest (5, class stand-ins in separate processes); core unit 651 / integration 449, HP 148, WC 10 OK; read-only check: dev20/21 HivePress+WooCommerce, dev22 HivePress, others clean
- PR: PR-035
 2026-09-26 00:36:02 +08:00
wpdev 3d650eb848 docs(2meet-data-optimizer): partner self-registration guide and deprecated AddOn notice 
- Add docs/PARTNER-REGISTRATION.md: TMDO_Anti_EAV_Aware bridge setup (plugins_loaded:3), table and entity-group registration with post_types scopes, frozen definitions, and the AddOn → self-registration migration checked with [COLLISION]/[ORPHAN]
- TMDO_Deprecated_Addons_Notice warns administrators while any of the 8 in-house partner AddOns is active (site or network)
- Trait register_entity_fields() forwards an optional $args (post_types) to the registry
- Verify: DeprecatedAddonsNoticeTest (4); core unit 645 / integration 449, HP 148, WC 10 OK
- PR: PR-021
 2026-09-26 00:31:34 +08:00
wpdev e0683a19b1 feat(2meet-data-optimizer): reconcile post rows written to the wrong group table 
- TMDO_Post_Group_Reconciler copies non-NULL values that legacy routing stored in another group's table into the post type's own group (NULL/missing legacy values keep the scoped value), resumable via a cursor, with a catch-up pass for rows updated during the run, then switches on tmdo_post_scoped_routing
- CLI: wp tmdo post-reconcile-groups [--dry-run] [--batch=<n>]; registry exposes get_group_post_types()
- Verify: PostGroupReconcilerPlanTest (4), PostGroupReconcilerTest (6); core unit 635 / integration 449, HP 145/49, WC 10/22 OK; read-only dry-run: dev20 320 values / 0 overwrites, dev21/22 none
- PR: PR-034
 2026-09-26 00:04:38 +08:00
wpdev 9fa84845be fix: NinjaFirewall 相容性 — 保護 WAF 設定選項不被重導向 
評估 NinjaFirewall (WP Edition) 4.9 的相容性，結論是兩者可共存且
不需要開發 AddOn（該外掛全 codebase 零個 apply_filters('nfw_*') /
do_action('nfw_*')，官方相容手段全在部署層）。但核心有一個隱患必須補。

TMDO_Options_Manager::register_settings_group() 以 pre_update_option_{key}
回傳 $old_value，讓選項不再落地 wp_options、改存專屬設定表。而
NinjaFirewall 的 Full WAF 走 auto_prepend_file，在 WordPress 載入前就以
原生 mysqli 直查 wp_options 取 nfw_options / nfw_rules。一旦這些鍵被
重導向，WAF 會讀不到設定而靜默停止防護 —— 不報錯、不寫 log。

nfw_rules 約 77KB 且 autoload=auto，正是 autoload 瘦身最誘人的目標，
因此這條路徑並非理論風險。

Added
- PROTECTED_OPTIONS 常數與註冊守衛（nfw_options / nfw_rules / nfw_checked），
  命中時發出 _doing_it_wrong()。守衛置於方法開頭，全部鍵都被擋時提前返回，
  不再建立空的設定表。
- tests/unit/OptionsManagerProtectedTest.php（4 tests / 10 assertions），
  鎖住「受保護鍵絕不會被掛上 pre_option_* / pre_update_option_* 攔截」。
- docs/WAF-COMPATIBILITY.md：模式差異、symlink 多租戶部署、WP SaaS 開站
  流程與驗證清單、三條開發約束、實測風險矩陣。

Changed
- Migration Wizard 輪詢 500ms → 2s，與四個 stress-test 面板一致。
  原本 2 req/s 打同一 REST endpoint，易觸發 WAF rate-limit 與 bot 偵測。

autoload 最佳化不受影響：optimize_autoload() 只改 autoload 欄位、不刪列，
而 Full WAF 的 SELECT * 不看 autoload。

驗證：591 tests / 1166 assertions 通過，PHPCS 零違規，版本一致性 1.0.2。
dev30 於 Full WAF 與 WP WAF 兩種模式下實測，firewall log 中 TMDO 相關
攔截 0 筆。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SdjXAU473eekjPBB8vPVRS
 2026-08-15 20:38:09 +08:00
wpdev 9f587c39dc fix: Schema Registry cold zone 註冊改為冪等（修復欄位重複累積）
Tests / PHP Lint (pull_request) Successful in 13s
Details
Anti-EAV Lint + Quality Gate / anti-eav-lint (pull_request) Failing after 25s
Details
Tests / Unit Tests (pull_request) Successful in 36s
Details
Tests / PHPCS (pull_request) Successful in 30s
Details
Tests / PHPStan (pull_request) Successful in 53s
Details
Tests / Integration Tests (pull_request) Successful in 2m47s
Details 
三個 zone 索引的寫入方式並不一致：
- hot  -> hot_columns[post_type][column]  以 column 為 key，天生冪等
- warm -> warm_fields[meta_key]           以 meta_key 為 key，天生冪等
- cold -> cold_fields[post_type][]        append，無去重

而 wpdo_register_fields 本來就會被觸發多次：核心自身於 plugins_loaded:4
觸發，主檔另有 late-bind safety net 於 :30 再觸發一次（讓在 :6 之後才
bootstrap 的 AddOn 趕上）；加上主外掛與其 AddOn 可能同時註冊同一批欄位。

實測影響：某站台 cold_fields['hp_vendor'] 累積到 35 筆但只有 9 個相異值，
每個 key 重複 4 次。修正後為 9 筆、零重複。

修法：cold 分支加入 in_array() 去重，使 register() 對同一
(post_type, meta_key) 成為冪等操作，與 hot / warm 既有行為一致。

驗證：核心單元測試 587 tests / 1156 assertions 全綠；
wp wpdo doctor 於兩個站台皆 0 FAIL。

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
 2026-08-08 14:27:15 +08:00
wpdev fa356a63b1 fix(bootstrap): 舊外掛互斥偵測改查 active_plugins
Anti-EAV Lint + Quality Gate / anti-eav-lint (push) Successful in 8s
Details
Tests / Unit Tests (push) Successful in 10s
Details
Tests / Integration Tests (push) Successful in 33s
Details
Tests / PHP Lint (push) Successful in 8s
Details
Tests / PHPCS (push) Successful in 20s
Details
Tests / PHPStan (push) Successful in 22s
Details
Release / Test Gate (lint + phpcs + phpstan + unit + integration) (push) Successful in 1m2s
Details
Release / release (push) Successful in 11s
Details 
WPDO_VERSION 由 class-tmdo-back-compat.php 自行 define 為 TMDO_VERSION，
兩者永遠相等，admin notice 從未觸發；PHPStan L6 認出 notIdentical.alwaysFalse
並卡掉 main run #8 與 v1.0.0 tag 的 Test Gate。改查 active_plugins basename，
與 HP AddOn detector 的偵測方式一致。
 2026-07-31 09:50:23 +08:00
wpdev fbe41e2130 release: v1.0.0 — 取代 wp-data-optimizer v3.4.6
Anti-EAV Lint + Quality Gate / anti-eav-lint (push) Successful in 9s
Details
Tests / Unit Tests (push) Successful in 10s
Details
Tests / Integration Tests (push) Successful in 33s
Details
Tests / PHP Lint (push) Successful in 8s
Details
Tests / PHPCS (push) Successful in 20s
Details
Tests / PHPStan (push) Failing after 25s
Details
Release / Test Gate (lint + phpcs + phpstan + unit + integration) (push) Failing after 36s
Details
Release / release (push) Has been skipped
Details 
版本 0.1.0 → 1.0.0（含 TMDO_VERSION / TWO_MEET_DATA_OPTIMIZER_VERSION /
WP_DATA_OPTIMIZER_VERSION 與 unit bootstrap）。姊妹外掛只在診斷 CLI 顯示
WP_DATA_OPTIMIZER_VERSION、無版本比較，故報 1.0.0 安全。

wp-data-optimizer 退休：兩站台已停用，本機三個目錄改名為 *.retired
（wp-data-optimizer / -v3.1.1 / _audit），git 歷史保留在 gitea。

CHANGELOG 記錄本次 backport 全貌與 4 項 ABI/行為變更。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY
 2026-07-31 09:45:22 +08:00
wpdev 76c01e44df refactor: 全部 128 個生產檔加入 declare(strict_types=1)（PR-H） 
對齊 A v3.2.0。型別強制會把隱式轉換變成 TypeError，所以一次全檔加入
並跑完整測試（unit 451 / integration 398 全綠，無迴歸）。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY
 2026-07-31 06:13:33 +08:00
wpdev 56d534619e feat(interceptors): 核心加入 Standard_Post_Interceptor 抽象基底（F1） 
Template Method 基底（A v3.0.1），收斂 action_delete_post /
filter_update_meta / action_insert_post 三件套。子類只需宣告
public const FIELD_MAP + get_post_type() + get_table_key() +
build_insert_data()。

HP AddOn 的 4 個 interceptor 隨即改為繼承它（573 → 344 行）；未來
LatePoint / bookings / quotation 等 post↔自訂表 1:1 鏡射也可直接用。
back-compat 補 WPDO_Standard_Post_Interceptor alias。

unit 451 / integration 398 GREEN

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY
 2026-07-31 06:07:20 +08:00
wpdev c46814ce83 refactor(migration): 回填 Migration Phase Strategy 體系（PR-D） 
A v3.0.1 把 orchestrator 的 11 個 phase 抽成可注入的 Phase 物件，B 仍是
1107 行單體、以 'phase_' . $current 字串魔法分派、completed 甚至 inline
在 tick() 裡。本 commit 對齊：

新增 13 檔
- includes/migration/interface-migration-phase.php
- includes/migration/class-tmdo-migration-phase-base.php（log/get_managed_keys/
  execute_bulk_pivot/values_loose_equal 等共用 helper）
- includes/migration/phases/ 11 個 phase 類別

orchestrator 1107 → 640 行
- tick() 改 make_phase() 工廠 + $phase->execute($job)
- 移除 final、self::ENTITY_TYPE → static::（A v3.3.0 late static binding）
- 保留 B 原有的 '✓ %s (%.2fs)' 耗時 log（改為 tick 自行量測，A 版已簡化掉）
- 公開介面（preflight/start/tick/get_status/cancel/resume/needs_attention/
  cron_tick）經 diff 確認與 A 完全一致，呼叫端零影響

連帶
- Schema_Manager 補 table_exists 的 request-scoped cache 與
  flush_table_exists_cache()（A v3.1.6 + v3.4.6），Phase 測試需要它
- back-compat 補 12 個 Phase 類別的 WPDO_ alias
- 移植 MigrationPhaseTest + MigrationPhaseRemainingTest（527 行）

測試隔離差異（B 的 unit bootstrap 會載入 Member_Fields / Post_Fields，
A 的不會）：MigrationPhaseRemainingTest 的 setUp 需額外清空 Entity_Registry
與 wpdo_register_entity_fields listener，否則 install_schema 會真的走進
dbDelta。MigrationPhaseTest 的 interface 斷言改用 TMDO_ 正式名稱
（PHP 無法 class_alias 介面，且該契約是核心內部擴充點）。

unit 451 / integration 398 GREEN

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY
 2026-07-31 05:54:49 +08:00
wpdev f187ac5401 refactor(zones): 回填 Zone_Router + Routing_Predicate（PR-C） 
A v3.0.1/v3.4.0 的架構深化，B 完全缺席：

新增
- includes/zones/class-tmdo-zone-router.php：module_name / read / write /
  delete_field / delete_post 五個 static 分派點
- includes/class-tmdo-routing-predicate.php：entity_bridge_owns（含
  request-level cache，B 原本沒有）+ should_{write,read,query}_from_zone
  + flush_cache

改寫
- Sync_Bridge 改用兩者，移除 5 個 private wrapper（get_zone_module /
  read_from_zone / write_to_zone / delete_from_zone / is_owned_by_entity_bridge）
  與 44 行 inline cleanup_post → Zone_Router::delete_post 一行（400→269 行）
- Query_Router 抽出 extract_hot_clauses() public static，pre_get_posts 變薄殼
- 收斂 5 處重複的 'hot_'/'cold_' . sanitize_key()（rest-api ×3、
  hot/cold-migration ×2）
- back-compat 補 WPDO_Zone_Router / WPDO_Routing_Predicate alias

測試
- 移植 ZoneRouterTest（250 行）+ RoutingPredicateTest（85 行）
- SyncBridgeEntityGuardTest 的 setUp/tearDownAfterClass 補 flush_cache()，
  否則 entity_bridge_cache 會跨測試污染（A v3.4.6 踩過同一個坑）

unit 409 / integration 398 GREEN

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY
 2026-07-31 05:47:08 +08:00
wpdev a0847a27bf fix(audit,sso): audit 表補 group_name/action 欄 + 註冊 Audit_Logger + known_login_ips（A11/A12/A14） 
- wpdo_audit CREATE 補 group_name varchar(50) 與 action varchar(20)：
  TMDO_Audit_Logger::write_row() 一直在寫這兩個 key，表卻沒有該欄位。
  SCHEMA_VERSION 2.0.0 → 2.1.0 觸發既有站台 dbDelta ALTER；主檔與兩個
  test bootstrap 的 TMDO_DB_VERSION 同步（BackCompatTest 守門要求一致）。
- TMDO_Core::run() 註冊 TMDO_Audit_Logger::init()：先前完全沒掛，
  wpdo_after_write / wpdo_after_delete 的稽核監聽器形同不存在。
- register_sso_group() 補 known_login_ips（A v3.4.4）：2meet-spoke-sso 的
  TMSO_Login_Notify 以 set_entity 寫此欄，未註冊時降級落 wp_usermeta。
  對應測試改為 test_sso_group_has_eight_fields。

unit 379 / integration 398 GREEN

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY
 2026-07-31 05:16:33 +08:00
wpdev d36bb954d1 chore: initial snapshot of 2meet-data-optimizer v0.1.0 
Baseline before backporting wp-data-optimizer v3.0.1-v3.4.6.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY
 2026-07-31 05:06:36 +08:00