WordPress.org
Get WordPress

Plugin Directory

Changeset 3682677


Ignore:
Timestamp:
09/05/2026 05:09:01 PM (7 weeks ago)
Author:
rynexai
Message:

2.12.1: release

Location:
rynex-ai-for-woocommerce
Files:
44 added
2 edited

Legend:

Unmodified
Added
Removed

  • rynex-ai-for-woocommerce/trunk/readme.txt

    r3670881 r3682677  
    55Tested up to: 7.0.3
    66Requires PHP: 7.4
    7 Stable tag: 2.12.0
     7Stable tag: 2.12.1
    88License: GPLv2 or later
    99License URI: https://www.gnu.org/licenses/gpl-2.0.html
    … …  
    7272* **On connect (WordPress site without WooCommerce):** your site URL, your site's REST API base URL, your WordPress and plugin version numbers, the administrator email as above, the same permalink/REST diagnostics as above (2.12.0+), and a one-time pairing token — the plugin publishes only the token's SHA-256 hash at /wp-json/rynex/v1/pair-verify for five minutes so Rynex can verify you control the site. No API key is created. Rynex then fetches your home page once to seed the assistant's knowledge.
    7373* **While connected (both modes):** your site loads the Rynex widget script; conversations are processed by Rynex to power the assistant and analytics. The widget stores an anonymous visitor ID in the browser and sends it with conversation events; on pages it recognizes as product pages it also reports the page URL and product identifier, so Rynex can personalize the assistant and the optional on-site "You may also like" recommendations. Setting `ShopAgentConfig.trackingConsent = false` disables both the stored ID and the browsing signal. **WooCommerce stores only:** order and product webhooks are sent to Rynex for catalog freshness and revenue attribution.
     74* **Visitor audiences (both modes):** to let you show a welcome message, coupon or other widget screen only to certain visitors, the widget also reports page views and widget opens (page URL, referrer, UTM parameters, device type, language) together with the anonymous visitor ID and a session ID stored in the browser under `shopagent_visitor_id` and `shopagent_session_id`. From this Rynex derives five coarse labels across visits within 30 days — returning visitor, opened the widget before, chatted before, came from a paid campaign, browsed 3+ products — and returns only those labels to the widget; no browsing history leaves Rynex. Labels are computed only when one of your widget rules targets an audience. Setting `ShopAgentConfig.trackingConsent = false` (or calling `window.ShopAgent.optOut()`) sends page views and widget opens without any visitor or session identifier (aggregate counts only) and disables audience labels for that shopper; if a shopper withdraws consent later, the widget dispatches the `shopagent:consent-changed` event and Rynex erases the behavioural data derived from that visitor ID (product views, interest profile, visitor/session identifiers on traffic events). Conversations are kept for service delivery. Because this is behavioural targeting, describe it in your privacy policy and wire your consent tool to the setting above.
    7475* **Signed-in shoppers (2.11.0+, both modes):** when a logged-in customer opens a page, the widget tag carries a signed customer token (the WooCommerce/WordPress customer ID, e-mail address and name) that expires after 24 hours; it is sent to Rynex with the shopper's chat requests so your inbox can show who is talking. Nothing is emitted for guests.
    7576* **On the settings page:** a status check identifying your store; from 2.7.1 it also carries the administrator email above so existing connections gain an account contact without reconnecting.
    … …  
    177178== Changelog ==
    178179
     180= 2.12.1 =
     181* Updated: the External services section now describes visitor audiences — the widget reports page views and widget opens (page URL, referrer, UTM parameters, device type, language) with the anonymous visitor and session IDs so Rynex can derive coarse, cross-visit audiences (returning, opened the widget before, chatted before, arrived from a paid campaign, browsed 3+ products) that you can target from Widget Studio. It also lists the browser storage involved and how a consent tool opts a shopper out (`ShopAgentConfig.trackingConsent = false` or `window.ShopAgent.optOut()`, which also erases the derived behavioural data). No plugin code changes.
     182
    179183= 2.12.0 =
    180184* Fixed: stores with plain permalinks or WordPress in a subdirectory could not connect (the connection check ignored the site's REST base). Both now connect.

  • rynex-ai-for-woocommerce/trunk/rynex-woo.php

    r3670881 r3682677  
    33 * Plugin Name: Rynex – Free AI Chatbot for WooCommerce (AI Sales & Support Agent)
    44 * Description: AI chatbot for WooCommerce and WordPress. One-click connect: on a store it recommends products, adds them to the cart and reports the revenue each conversation produced; without WooCommerce it answers from your own content. Free plan included.
    5  * Version: 2.12.0
     5 * Version: 2.12.1
    66 * Author: Rynex
    77 * Author URI: https://rynex.io
    … …  
    2020}
    2121
    22 define( 'RYNEX_WOO_VERSION', '2.12.0' );
     22define( 'RYNEX_WOO_VERSION', '2.12.1' );
    2323define( 'RYNEX_WOO_PLUGIN_FILE', __FILE__ );
    2424if ( ! defined( 'RYNEX_WOO_API_BASE' ) ) {
Note: See TracChangeset for help on using the changeset viewer.