release 0.1.1: 2meet-data-optimizer-infocards-addon #2
Reference in New Issue
Block a user
Delete Branch "release/0.1.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?
Version 0.1.1: the partner-detection / install fix that has been live in
plugins/since August but was never pushed to Gitea. Brings Gitea main in line with the deployed code.Commits
Rollout
Packaged as
2meet-data-optimizer-infocards-addon-v0.1.1.zipinwp-local-dev/dist. Merging does not changeplugins/.TMDO_Infocards::register() 舊版在 bootstrap 當下以 class_exists('TMEETIC_*') 偵測 partner,失敗即 early return。但本 AddOn bootstrap 掛在 plugins_loaded:6, 而 2meet-infocards 要到 :20(tmeetic_run)才 require 自身類別——在 :6 當下 TMEETIC_* 一律不存在,偵測必定失敗,兩個註冊 hook 從未被掛上,整個 AddOn 等同未啟用。 三處修法: 1. 偵測從 bootstrap 移進 hook callback 內執行,hook 一律先掛上 2. 偵測改以 TMEETIC_VERSION / TMEETIC_PLUGIN_DIR 常數優先(檔案解析當下即 define,早於 plugins_loaded),class_exists() 退為後備 3. bootstrap priority 6 → 3;wpdo_register_custom_tables callback prio 設 5, 讓本 AddOn 較豐富的定義勝過主外掛無 expected_columns 的版本 同時修正 IG token 兩個欄位的 meta_key 錯配(tmeetic_ig_access_token_enc / tmeetic_ig_token_expiry),以及 registry 索引 config key expected_indexes → indexes。 實測驗證: - wpdo_register_fields 掛載 prio 10、wpdo_register_custom_tables prio 5 - 2meet_vendor_profiles 由本 AddOn 註冊(16 欄位 / 1 索引 / doctor_callback) - 缺 expected_columns 由 26/29 降為 0/46 - wp wpdo doctor 60 OK / 0 FAIL;anti-EAV lint 通過;站台 200/200