SendSMS for WooCommerce
| 开发者 |
sendsms
neamtua catalinsendsms |
|---|---|
| 更新时间 | 2026年8月14日 17:27 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 |
| 版权网址: | 版权信息 |
详情介绍:
SendSMS for WooCommerce connects your WooCommerce store to the sendsms.ro SMS gateway so customers get a text message at every step of their order — placed, paid, shipped, completed, refunded, or any other status you choose.
Why SMS? It has a ~95% open rate, and most messages are read within five seconds of arrival. For order updates, that's hard to beat.
Features:
- Per-status message templates with variables:
{billing_first_name},{billing_last_name},{shipping_first_name},{shipping_last_name},{order_number},{order_date},{order_total}. - Campaign sender with date / county / product filters that pulls phone numbers from past orders.
- "Send a test SMS" page for verifying templates against any phone number.
- Per-order "Send SMS" sidebar metabox for one-off messages, with the SMS body recorded as an order note.
- SMS history table with full searching and sorting.
- Compatible with WooCommerce High-Performance Order Storage (HPOS).
- Optional unsubscribe-link (GDPR) and short-URL flags per status.
- Customer opt-out checkbox available at checkout.
安装:
- Install WooCommerce if you don't already have it.
- Upload the
sendsms-for-woocommercefolder to/wp-content/plugins/, or install the plugin from the WordPress.org directory. - Activate the plugin under Plugins in the WordPress admin.
- Go to SendSMS → Configuration and enter your sendsms.ro username and API key.
屏幕截图:
常见问题:
Do I need an account with sendsms.ro?
Yes. Sign up for free at https://www.sendsms.ro/ro/ and create an API key.
Does this plugin work with WooCommerce HPOS (High-Performance Order Storage)?
Yes. The plugin reads and writes order data through the WooCommerce order API so it works regardless of whether your store uses legacy CPT storage or HPOS.
What PHP versions are supported?
PHP 7.4 through PHP 8.3+. Tested on PHP 7.4 and PHP 8.3 against WordPress 7.0 and WooCommerce 10.7.
Can my customers opt out of SMS notifications?
Yes. Enable the "Opt-out in cart" setting under Configuration; a checkbox appears at checkout. Customers who tick it never receive automated SMS for that order.
更新日志:
2.0.4
- Verified against WordPress 7.1;
Tested up toraised to 7.1. No code changes were needed — the plugin registers no block-editor assets, does no image processing, and does not use jQuery UI, so none of the 7.1 editor, media, or jQuery UI changes affect it. Requires at leastraised from 4.0 to 6.5. The old value was inaccurate: the plugin usessanitize_textarea_field()(WordPress 4.7) andwp_json_encode()(WordPress 4.1), and itsRequires Plugins: woocommerceheader is only honoured from WordPress 6.5 onwards.
- Plugin prefix changed to
rosendsms_(PHP namespaceRosendsms\\ForWooCommerce, settings optionrosendsms_options, history table{prefix}rosendsms_history, order opt-out meta keyrosendsms_optout, AJAX actionswp_ajax_rosendsms_campaign/wp_ajax_rosendsms_single, extensibility hooksrosendsms_should_send/rosendsms_message/rosendsms_recipient_phone/rosendsms_after_send). - Migration now handles two earlier naming schemes: v1.x (
wc_sendsms_*/wcsendsms_history/wc_sendsms_optout) and v2.0.2 (sendsmsro_*/sendsmsro_history/sendsmsro_optout). Both are migrated to the currentrosendsms_*names on activation.
- Renamed every stored name (PHP namespace, settings option, history table, order opt-out meta key, AJAX action names, extensibility hooks) to a single prefix to satisfy WordPress.org Plugin Directory naming conventions.
- Added an activation-time migration that copies the v1.x stored data (settings option, price cache, history table, order opt-out meta) into the new names. Upgrading from a v1.x install carries over every setting and SMS-history row automatically.
register_setting()sanitize callback now applies per-field sanitization (sanitize_text_field,sanitize_textarea_field,sanitize_key, and recursive sanitization for the per-status template/flag arrays).readme.txtnow includes an== External services ==section disclosing every sendsms.ro endpoint used, the data sent, and links to the gateway's terms / privacy / ISO certification.- Added
sendsms(the plugin's WordPress.org owner account) to the Contributors line.
- Settings page: fixed a bug where saving any tab wiped the values stored on the other tabs. Each tab now merges into the existing option instead of overwriting it.
- Order metabox: the Phone field is now pre-filled with the order's billing phone, and is no longer cleared after a successful send so follow-up messages don't require retyping the number.
- Settings page: added cell padding on the per-status template table so column headers and labels are no longer flush against the edges.
- Code reorganised into a PSR-4 namespace tree (
SendSMS\\ForWooCommerce\\…) with one class per responsibility (API client, settings reader, order listeners, admin pages, AJAX handlers). - Settings page redesigned with three tabs: Account, Customer notifications, Owner notification. The per-status template list is now a single table.
- Admin scripts moved to
assets/js/and enqueued only on the relevant pages. - New extensibility hooks for third-party developers:
sendsms_for_woocommerce_should_send,sendsms_for_woocommerce_message,sendsms_for_woocommerce_recipient_phone, andsendsms_for_woocommerce_after_send. - Continued from the 1.4.3 security baseline (legacy repository now archived):
- Single-send AJAX endpoint guarded with nonce +
manage_woocommercecapability. - Test-send form CSRF-protected.
- Stored password never rendered back into the settings form.
- Stored-XSS escaping on every column of the History page.
- HPOS-aware throughout (declared via
FeaturesUtil::declare_compatibility). - In-memory CSV for campaign sends (no
batches/filesystem write). - Minimum PHP raised to 7.4; verified on PHP 7.4 and PHP 8.3.