2meet-data-optimizer

Files

T

wpdev 08f9e313e0 fix(2meet-data-optimizer): serialize arrays in text fields instead of storing "Array"

- TMDO_Type_Caster: text / textarea values that are arrays or objects are
  stored with maybe_serialize() (was (string) → the literal "Array", which
  bridge-restore-native then wrote back over native meta); from_db()
  unserializes them with TMDO_Safe_Unserialize. text columns are
  VARCHAR(255): longer values are stored NULL (native keeps them) and
  logged as text_overflow.
- Add `wp tmdo repair-array-literals [--entity] [--confirm]`
  (TMDO_Array_Literal_Repair): rewrites flat "Array" values from native
  meta and lists native rows that are "Array" themselves (backup needed).
- Verify: TypeCasterSerializeTest 13 OK, ArrayLiteralRepairTest 3 OK;
  unit 685 OK, integration 483 OK, phpcs (phpcs.xml) 0, stan OK;
  live `serialized` 3 PASS; dev36 repair dry-run lists the value corrupted
  by the 2026-09-26 round trip (user #1 community-events-location)
- PR: PR-055

2026-09-26 18:45:59 +08:00

phases

fix(2meet-data-optimizer): refuse aeav_only and cleanup on HivePress / WooCommerce sites

2026-09-26 18:29:04 +08:00

class-tmdo-archive-migration.php

refactor: 全部 128 個生產檔加入 declare(strict_types=1)（PR-H）

2026-07-31 06:13:33 +08:00

class-tmdo-array-literal-repair.php

fix(2meet-data-optimizer): serialize arrays in text fields instead of storing "Array"

2026-09-26 18:45:59 +08:00

class-tmdo-cold-migration.php

refactor: 全部 128 個生產檔加入 declare(strict_types=1)（PR-H）