| 开发者 | seedvision |
|---|---|
| 更新时间 | 2026年10月8日 18:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
GET /api/v1/ping — when you click "Test connection" in the settings.POST /api/v1/connect — when you save your API key. Data sent: site URL (site_url), store name, administrator contact email.POST /api/v1/orders — when a paid order carries a contribution. Data sent: order id and number, currency, contribution amount, number of trees, customer email and name, so that the certificate can be sent to them.POST /api/v1/disconnect — once, when you delete the plugin. Data sent: site URL and the reason (plugin_uninstalled), so the service stops counting your store as active. No personal data. If the service cannot be reached, the deletion carries on regardless.Yes, in one click, on the classic checkout and on the Checkout Blocks alike. The total updates immediately.
Yes, since version 1.2.2. The choice is made once in your Green Cart dashboard and reaches the plugin on its next connection, so there is nothing to configure here. A store that has made no choice keeps the box ticked, exactly as before.
Yes, since version 1.1.0. Both the contribution line and the box to decline it appear in the cart block and in the checkout block, exactly as on the classic checkout. There is nothing to configure: the plugin detects which checkout is in use.
No, and the plugin never says it is. It funds the planting of trees, and it speaks only of a climate "contribution". It makes no carbon-offsetting or carbon-neutrality claim and publishes no CO2 equivalence, in line with French decree no. 2022-539 and EU Directive 2024/825. If you need certified carbon credits, this is not the right tool.
Yes. The plugin declares compatibility with custom order tables and only reaches orders through the WooCommerce CRUD API.
The contribution is not offered in this version. Multi-currency support is planned.
Plantings are ordered shortly after payment, and a planted tree cannot be unplanted. Contact support for individual cases.
has_session() method; calling it returned a 500 and the customer could not remove the contribution. Storefronts using the Blocks cart in a browser were not affected — they authenticate with a nonce and a cookie — but headless stores and API integrations hit the wall.gccheckout instead of gcc, to rule out collisions with other plugins. Nothing to do on your side: the plugin has never been published, so no site carries the old names.extensionCartUpdate) and writes the same session flag as the classic checkout: one source of truth, and a total recalculated straight away.