| 开发者 | ristorehemagi |
|---|---|
| 更新时间 | 2026年11月19日 17:39 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
X-Croco-API-Key header. WordPress
Application Passwords are not bridge credentials. Authenticated clients can inspect supported
operations, limits, and quick-edit constraints through GET /wp-json/crocoai-data-bridge/v1/capabilities.
Croco can read products, variations, categories, attributes, prices, inventory, dimensions, media
URLs, and Croco-managed metadata. Authorized clients can publish product and media changes. Treat
the API key like an administrator credential and use the bridge only over HTTPS.
Croco is an optional compatible catalog-management service. The plugin is
fully usable without purchasing or registering for that service.
No. The plugin exposes a documented authenticated bridge that can be used by any compatible API client. The Croco service is one optional client.
It can read catalog and diagnostic data and invoke the bridge's product, taxonomy, media, and staged publication operations. It cannot create or rotate API keys. Store the key securely and use HTTPS.
No. It does not send analytics or telemetry and does not connect to the Croco service by itself.
Operational tables and settings are retained by default. Enable permanent data removal in Health before uninstalling to delete those tables and settings. Published WooCommerce content remains.
assets/build/admin.js is a generated bundle. The readable, non-minified source is
assets/src/admin.js, with styles in assets/src/admin.css. Both source files are included in
the plugin zip.
/catalog/manifest list: the parent, modification time, and stock of every exported product and variation, with a signature of the attribute and brand terms.include parameter to the catalog export, so Croco can fetch only the products that changed since its last capture.before upper bound to the catalog export and the /catalog/ids list, so Croco can read the catalog in parallel ID ranges.brands field and selected-release protocol 6 through capability discovery.brands entries with term ID, name, and slug.crocoai-data-bridge. Existing option keys, tables, post meta, and Action Scheduler events are migrated on activation or upgrade. The previous wpi/v1 REST namespace remains as a compatibility alias.crocoai-data-bridge slug, author metadata, translations, and WooCommerce dependency declaration.variation_to_simple, preserve translated child IDs, and roll back the complete language family.set_options() on a missing duplicate attribute during structural updates.{key, name, values}; the key is the slug the store keeps the taxonomy under and the name is the label shown over it. A renamed attribute now updates its label in place instead of becoming a second attribute beside the first.useData passed its loader straight to useEffect, and that loader returns a promise. React treats an effect's return value as the cleanup function, so leaving Jobs made React call a promise, which threw TypeError and unmounted the whole screen. The page went blank and Health — the only place that creates the API key — could not be reached.wpml_make_duplicate is not a hook WPML registers, so do_action on it created nothing and said nothing, and every translated publication failed on a store that was working correctly. Each way of duplicating is now tried in turn, most exact first, and the result is checked after each. The error names what was tried.CROCOAI_DBRIDGE_VERSION was last set at 0.3.28, so 0.3.29, 0.3.30 and 0.3.31 all reported themselves as 0.3.28 in diagnostics and in every version check that reads it. Packaging now refuses to build when the plugin header, the constant and the stable tag disagree.crocoai-data-bridge/v1/diagnostics now says whether wpml_make_duplicate and wpml_admin_make_post_duplicates have a listener on this store. A do_action on a hook nobody registered creates nothing and reports nothing, which reads exactly like a duplication that ran and failed.