TextMe SMS

2.2.1

• Fix: The OTP / phone-login flows now release PHP’s session lock before each outbound SMS to the gateway, so a slow gateway response no longer blocks the same visitor’s other requests (page loads, AJAX) while they wait. The session is reopened immediately afterwards — using session_status() rather than session_id(), so no verification data is lost — keeping the OTP round-trip intact.

2.2.0

• Fix: The built-in Admin order notifications (e.g. “New Order – Admin SMS”) now also send when a matching Shipping Rule handles the order. Previously a matching shipping rule replaced the default notifications entirely, so the admin SMS was silently skipped for orders that hit a rule. The shipping rule still owns the customer message; the rule’s own “Admin” copy and the built-in Admin notification are independent toggles, so if both are enabled the admin receives both.
• Feat: The API Logs tab now has a “Details” column with a per-row “View” toggle that shows the full request and response JSON (pretty-printed; passwords and gateway tokens remain masked) — so gateway errors can be diagnosed directly in the admin without a database query.

2.1.9

• Fix: Sending a back-in-stock SMS from the Restock SMS page no longer fails with “No valid phone numbers found” when the product’s stored request list has gaps in its keys (left behind by earlier saves that filtered out empty entries without reindexing). The page renders requests by position, so the send and delete actions now map the selected position back to the stored entry instead of treating the position as a storage key — which also means the correct request is moved to the sent log or deleted when a list has gaps.
• Fix: New stock-notification signups are stored with sequential keys, so no new gaps are created.

2.1.8

• Fix: SMS recipient phone is now sent to the gateway as a plain string (per the TextMe API spec) instead of a nested object, which the gateway could not read — it had been recording a null recipient and returning “api failure” for regular order/customer SMS. OTP was unaffected. The v1 XML path and the API log reader were updated to match.
• Feat: The Sender Name field is now validated on save — a text sender may be at most 11 characters (a numeric sender up to 15), matching the gateway limit — so an over-long sender is rejected with a clear message at configuration time instead of failing silently on every send (gateway error 992). Counted by characters, so Hebrew is measured correctly.
• Fix: SMS is no longer dispatched to the gateway with an empty recipient phone (e.g. an order with no phone on file); the attempt is skipped and logged with its originating hook for traceability.
• UI: New shipping-rule rows now start with their “On” and “Admin” toggles unchecked, consistent with the rest of the plugin’s default-off toggles. Saved rules are unaffected.

2.1.7

• Fix: The “Send Stock Notification” dialog on the product edit screen now displays correctly in right-to-left (Hebrew) admins — it opens centered and stays draggable instead of being pinned off-screen to the right. Also: the dialog title is now translated, the close button shows a clean icon (no stray “Close” text or focus outline), the dialog sits above the editor toolbar, and the action buttons are a uniform size.

2.1.6

• Fix: Admin OTP no longer blocks REST API / Application Password authentication for administrators. Enforcing an interactive SMS challenge on machine credentials (WooCommerce REST API keys, WP Application Passwords) broke legitimate server-to-server integrations — e.g. a POS polling /wc/v3/orders — that have no way to complete an OTP prompt. Interactive admin logins (wp-login.php) remain fully OTP-gated, and the XML-RPC guard is unchanged.