ChandBood – Price History for WooCommerce
| 开发者 | arefsarkhosh |
|---|---|
| 更新时间 | 2026年8月12日 22:18 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
ChandBood keeps an independent price history for WooCommerce products and variations. It records real price changes made through standard WooCommerce product saves, imports, APIs, quick edits, and ChandBood's own bulk editor.
The plugin can show customers a responsive price history chart and table on product pages. Store managers can also review or correct individual history records from the product editor.
Main features
- Automatically records regular and sale price changes for products and variations.
- Keeps unlimited history by default, with an optional per-product record limit.
- Provides an AJAX bulk editor for regular price, sale price, and stock status.
- Records price changes made through the bulk editor in the same history.
- Displays a responsive Chart.js price chart with selectable date ranges.
- Includes a price history table and current, lowest, and highest price summaries.
- Provides the
[chandbood_chart]shortcode for product templates and other content. - Includes an Elementor product price chart widget when Elementor is active.
- Adds a product metabox for adding, editing, and deleting history records.
- Supports WooCommerce High-Performance Order Storage (HPOS).
- Includes an optional setting to remove ChandBood data during uninstall.
安装:
- Upload the plugin ZIP from Plugins > Add New > Upload Plugin.
- Activate ChandBood. WooCommerce must already be active.
- Open ChandBood > Settings to review history and cleanup options.
- Open ChandBood > Bulk Price Editor to filter and edit products.
- Add the
[chandbood_chart]shortcode or the Elementor widget where a manual chart trigger is needed.
常见问题:
Does ChandBood change existing product prices during activation?
No. The initial history task reads current eligible prices and creates missing history records without changing WooCommerce product data.
Are variation prices tracked separately?
Yes. Each variation has its own price history and can be selected independently in the customer-facing chart.
Are bulk price changes added to the history?
Yes. Successful regular or sale price changes made with the ChandBood bulk editor use WooCommerce CRUD and are recorded by the same tracker.
Can I limit the number of stored records?
Yes. History is unlimited by default. An optional setting can retain only a chosen number of recent records for each product or variation.
Does uninstalling the plugin delete prices?
No. WooCommerce product prices are never deleted. ChandBood history and settings are removed only when the uninstall cleanup option is enabled.
更新日志:
1.9.12
- Addressed Plugin Check findings for translation placeholders, output escaping, request verification, and documented direct database access.
- Renamed the plugin to ChandBood and added the new
[chandbood_chart]shortcode while retaining the legacy shortcode for compatibility. - Replaced direct script and style output with WordPress-enqueued assets.
- Sanitized every bulk-editor request value before it reaches query filters.
- Removed JSON output from inline script context and moved the lazy loader to an enqueued file.
- Rewrote the plugin directory description and documentation in English.
- Displayed readable variation attribute names in the bulk editor while retaining slugs as internal identifiers.
- Recorded price changes for out-of-stock products and variations.
- Included eligible out-of-stock products in the initial history process.
- Stored initial history timestamps using the WordPress site timezone.
- Added a persistent one-time marker for the initial history process.
- Limited the initial task to products and variations without existing history.
- Added a bounded initial price history task and a manual completion tool.
- Hid comparison statistics when a date range contains only one real record.
- Removed synthetic chart points so charts and statistics use stored history only.
- Hardened AJAX, price updates, database errors, scheduled tasks, and custom-role compatibility.
- Improved handling of concurrent saves and partial bulk-operation failures.