| 开发者 | castrasteel |
|---|---|
| 更新时间 | 2026年9月1日 06:18 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/angra-kop/) created automatically on activation./wp-content/plugins/angerratt-se-for-woocommerce directory, or install the plugin through the WordPress Plugins screen directly./angra-kop/) containing the [ngersefo_angerratt] shortcode is created automatically on activation.On activation the plugin creates a page at /angra-kop/ containing the [ngersefo_angerratt] shortcode. You can move the shortcode to any page you like.
Yes. Identity is verified with a one-time code sent to the order's email address, so customers do not need an account.
Yes. Partial returns are optional and disabled by default — the plugin then registers a full withdrawal of the selected order, exactly as before. When you enable partial returns under WooCommerce → Ångerrätt, the customer gets a checkbox in front of each eligible product in the confirmation step and can withdraw only the items they choose. The order total is recalculated to reflect the selected products, and you can choose per store whether the shipping cost is refunded on a partial return.
Withdrawal declarations are stored in a dedicated table in your own WordPress database. Records are removed automatically after the retention period you set in the settings.
No, and that's deliberate. The confirmation email only confirms that the declaration was received and lists which products it covers — it never states a refund amount, shipping status or a processing timeline, since those depend on your review of the declaration. You decide the outcome and communicate it separately; the plugin doesn't commit to anything on your behalf before that.
The Distance Contracts Act requires this information before the customer is bound by the contract, which happens at checkout — not when items are merely added to the cart. The plugin shows the notice at checkout and on the order confirmation page, which satisfies the requirement; the cart page was intentionally left out.
REMOTE_ADDR is the proxy's own address in those setups, so the limit became a single bucket for the whole internet and switched the withdrawal form off for everyone after 15 requests. Reported from a live store. Proxy headers are now trusted only when REMOTE_ADDR is a private or reserved address, which is exactly the case where it cannot be the visitor: stores without a proxy keep a limit that cannot be spoofed. A new ngersefo_client_ip filter covers setups such as Cloudflare, where the address is public but still not the visitor's.{site_title} were printed literally in the footer of the customer's acknowledgement, and the emails were sent without WooCommerce's inline styles. Both came from rendering WooCommerce's templates outside its email system; the emails now go through it.ngersefo_email_headers filter for anyone who does want to set the sender in code.$wpdb->prepare() placeholder for the internal table name, and remove a redundant suppress_filters flag. No functional changes.wp_parse_url() usage brought fully in line with the WordPress coding standards.