| 开发者 | mujahidwp |
|---|---|
| 更新时间 | 2026年10月10日 01:27 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes. Kassebridge depends on WooCommerce checkout pages, sessions, orders, payment methods, and Checkout blocks.
No. Preview and gradual rollout keep the existing checkout page in place. Kassebridge uses a second block checkout page until you choose to make it permanent.
When the safety net is enabled, Kassebridge can pause the rollout if the block checkout has enough traffic but no successful orders, clearly more payment failures, or a statistically visible conversion drop. Traffic then returns to the classic checkout and an alert is created.
No. It has no telemetry or remote Kassebridge service. The optional loopback health test requests only the checkout URL on the same site.
Kassebridge does not set its own cookie. It uses the WooCommerce session for rollout assignment.
Yes.
It checks active plugins, must-use plugins, and the active theme and parent theme. WooCommerce itself and Kassebridge are skipped. The scan is read-only.
It sets the selected block checkout page as WooCommerce's checkout page. Kassebridge keeps the previous checkout page available so the change can be undone from the plugin while its saved state is still present.
By default, settings and aggregate totals remain. If "Delete all Kassebridge data when the plugin is deleted" is enabled, Kassebridge removes its settings, scan results, custom table, user preview preference, locks, and private Kassebridge order metadata.
Yes. User-facing strings use the kassebridge-checkout-migration-health-for-woocommerce text domain.