| 开发者 | wpmelon |
|---|---|
| 更新时间 | 2026年8月24日 21:03 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. All edits go through WooCommerce's standard CRUD API, so your data is handled the same way the core WooCommerce admin handles it. Hooks fire, caches are invalidated, and anything your other plugins do on product save continues to work.
Yes. The plugin runs inside the WordPress admin, so your front-end theme is not involved. It only loads its interface inside the WordPress admin and does not enqueue front-end assets.
Yes. Variations appear as child rows under their parent product. You can edit variation prices, stock, SKUs, and other fields inline, the same way you edit simple products. Sorting preserves the parent–child grouping.
The grid is virtualized, so it renders only the rows currently visible. In practice, stores with tens of thousands of products work fine on normal hosting. If you hit a performance wall, filter down to the subset you actually need — the grid works on whatever the filters return.
Edits are staged as pending changes in the grid before you save, so you can undo them or discard them entirely while they're unsaved. Once saved, the free version can't undo them — keep a backup, as you would with any bulk operation. The Pro version adds Operation History, which records each save so you can review and restore previous field values (see below).
Yes. Pro adds paste from Excel/Google Sheets, Operation History with restore, regex find-and-replace, price rounding, custom and ACF meta field editing, custom taxonomies, bulk variation creation, variation attribute editing, WPML support, fine-grained selection tools for the current grid page, and more. It's available at wpmelon.com. The free version is a complete, standalone tool — Pro extends it, it doesn't gate it.
Operation History is a Pro feature, currently in beta and off by default. When you turn it on, each bulk save is recorded locally so you can review it later and restore previous field values. Each record stores the before and after values of the fields that save changed, the product and variation IDs involved, the user who made the change, and timestamps. The data lives in custom database tables on your own site and is never sent off-site. Records are kept for 30 days by default (configurable) and pruned automatically. You can turn recording on or off, clear the history at any time, and optionally have all history data removed when you uninstall Pro. The free version records nothing and creates no history tables.
The plugin targets WooCommerce products (including variations) specifically. Other post types are not supported.
ACF field editing is a Pro feature. The free version edits WooCommerce core fields.
No. The free version runs entirely inside your WordPress site. It does not send data to any third-party server.
Nothing. No data is lost, no cleanup is needed. The plugin only reads and writes WooCommerce product data through standard APIs; deactivating removes the bulk-edit UI and nothing else.