Skladify – Price & Stock Sync for MoySklad
| 开发者 | skarb88 |
|---|---|
| 更新时间 | 2026年8月23日 03:20 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
WooCommerce SKU = MoySklad article
Free plugin scope:
- Manual synchronization started by an authorized WooCommerce administrator.
- Background batch processing after the manual start, using one-off WordPress queue events.
- Stock from exactly one explicitly selected MoySklad warehouse.
- WooCommerce regular-price updates.
- WooCommerce stock quantity and stock-status updates.
- Simple products and individual variations.
- Dry-run mode and synchronization logs.
- No plugin-imposed limit on the number of product cards.
安装:
- Back up the WordPress database and files.
- Deactivate the legacy “MoySklad WC Standalone Price & Stock Sync” plugin if it is active.
- Upload the plugin ZIP through Plugins > Add New > Upload Plugin, then activate it.
- Open WooCommerce > MoySklad Sync.
- Save a MoySklad access token, or save a login and password.
- Click Test connection to load warehouses and sampled price types.
- Select exactly one warehouse and save the settings.
- Keep Dry run enabled for the first synchronization and click Synchronize now.
- Review the counters and logs. Disable Dry run only after the matches and settings are correct.
屏幕截图:
常见问题:
Does the plugin create products?
No. Products and variations must already exist in WooCommerce. Only products whose SKU exactly matches the MoySklad article are considered.
Is there a product-card limit?
No. The plugin does not impose a catalog-size limit. Products are read from MoySklad in bounded background batches.
Does the plugin synchronize automatically?
No recurring schedule is included. An administrator must start each run manually. After that click, the run continues through one-off background queue events until all MoySklad product pages have been processed or the queue is stopped.
Why can I select only one warehouse?
This plugin intentionally reads stock from one explicitly selected warehouse. It sends one warehouse UUID in the stock request and does not aggregate stock across warehouses.
Can a separate add-on add scheduling and multiple warehouses?
Yes. The plugin exposes a stock-provider interface, a pssmwc_stock_provider filter, settings-page hooks, and the public PSSMWC\Sync::start() entry point. A separate add-on must contain its own scheduler, multi-warehouse settings, and aggregation implementation.
What happens when a stock value is missing?
A missing or null stock value is treated as unknown and is not written to WooCommerce. It is not silently converted to zero.
What if WP-Cron is disabled?
The manual run still depends on one-off WordPress queue events between batches. When DISABLE_WP_CRON is enabled, configure a real server cron request for wp-cron.php; otherwise a queued run can remain in the Running state.
Are settings removed on deactivation?
No. Deactivation stops the queue but retains settings and logs so the plugin can be reactivated safely. The legacy plugin option is also retained during migration to allow rollback.
What is removed when I delete the plugin?
Uninstall removes this plugin's settings, queue state, cached reference data, log table, and private mapping metadata. WooCommerce product prices and stock values already written by a completed synchronization are preserved. Data owned by the legacy plugin is not deleted.
更新日志:
- Moved the synchronization keep-alive JavaScript into an enqueued asset loaded only on this plugin's settings page while a run is active.
- Passed the REST endpoint and nonce through
wp_add_inline_script()instead of printing a raw script tag in PHP. - No settings change and no data migration.
- Removed a discouraged PHP execution-limit override; queue processing remains bounded by the existing execution-time budget.
- Kept SSL verification at the WordPress HTTP API default for same-site loopback requests and retained the existing fallback queue channels when loopback is unavailable.
- No settings change and no data migration.
- Limited dependency and action messages to the plugin row and the plugin's own settings screen.
- Moved loopback runner authentication into the REST permission callback.
- Removed bundled translation catalogues so WordPress.org language packs can provide translations.
- No settings change and no data migration.
- A synchronization run now processes as many batches as the request can afford instead of exactly one, so throughput no longer depends on how often the site happens to receive traffic.
- The batch time budget is derived from the host's own
max_execution_time, and a run stops before starting a batch that could not finish inside it. - Background work is carried by Action Scheduler, by a self-chaining loopback request and by WP-Cron, whichever the host supports; losing one channel no longer stalls a run.
- The loopback channel authenticates with a site-specific secret compared in constant time, verifies once every twelve hours that loopback requests reach the site, and can be disabled with the
pssmwc_enable_loopbackfilter. - The settings screen keeps a running queue moving while it is open and reloads itself when the run ends.
- A running queue is now considered abandoned after six hours rather than one, because restarting a queue resets its offset and a shorter threshold could make a scheduled run repeat the same catalogue indefinitely. The threshold is filterable through
pssmwc_stale_queue_ttl. - The settings screen reports which background channels are available instead of warning only about
DISABLE_WP_CRON. - New filter
pssmwc_drain_time_budgetfor hosts with unusual execution limits. - No settings change and no data migration.
- Action notices are now stored server side for one minute instead of being carried in the page URL, so their text can no longer be supplied through the address bar.
- Log table queries now pass the table name through the
%iplaceholder of$wpdb->prepare(), which raises the minimum WordPress version to 6.2. - Recent log rows are served from the object cache and invalidated on write.
- Removed the manual
load_plugin_textdomain()call; WordPress loads translations on demand. - No settings change and no data migration.
- Added the table-row level action
pssmwc_render_stock_source_row, so an add-on that replaces the stock source owns a complete table row including its own header cell and field label. - The built-in warehouse row is now skipped entirely when an add-on both suppresses the default field and supplies a replacement row, which removes an orphaned field label from the settings screen.
- The cell level action
pssmwc_render_stock_source_fieldis retained and documented as cell content only, so add-ons written against 1.0.0 keep working unchanged.
- Initial public Free release.
- Manual synchronization only.
- One selected warehouse only.
- No product-card limit.
- Added extension points for a separately distributed scheduler and stock provider.
- Added safe migration from the legacy multi-warehouse build without selecting an arbitrary warehouse.