fix(2meet-data-optimizer-latepoint-addon): drop the booking index table on uninstall
Tests / PHP Lint (pull_request) Successful in 4s
Tests / PHP Lint (pull_request) Successful in 4s
- 0.1.1 started creating wp_hpct_latepoint_idx, but uninstall.php was still the Phase 0 stub and left it behind (package check §10: CREATE without DROP) - Uninstall drops the table and the tmdo_latepoint_db_version option on every site; LatePoint's own tables are kept (the index is rebuilt from its bookings) - Version 0.1.2, CHANGELOG - Verify: php -l; dev36 uninstall run removed a stand-in table and the option
This commit is contained in:
@@ -13,6 +13,17 @@ Versioning follows [Semantic Versioning](https://semver.org/).
|
||||
|
||||
---
|
||||
|
||||
## [0.1.2] — 2026-09-26
|
||||
|
||||
### Fixed
|
||||
|
||||
- Uninstall now drops `wp_hpct_latepoint_idx` (every site on multisite) and the
|
||||
`tmdo_latepoint_db_version` option. 0.1.1 started creating the table, but
|
||||
`uninstall.php` was still the Phase 0 stub and left it behind. The table is
|
||||
an index rebuilt from LatePoint's bookings; LatePoint's own tables are kept.
|
||||
|
||||
---
|
||||
|
||||
## [0.1.1] — 2026-08-08 — 補上從未存在的 `wp_hpct_latepoint_idx` 建表流程
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in New Issue
Block a user