Major feature release: Live Human Chat. Two new database tables\nare created automatically on first admin page load after upgrade.\nNo breaking changes to existing AI chat functionality.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3582152,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3582152,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3582152,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3582152,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.92","1.0.93","1.0.95","1.1.01","1.1.14","1.10.4","1.10.5","1.3.10","1.3.32","1.3.7","1.3.8","1.3.9"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The chat widget open on a WooCommerce product page \u2014 AI-powered product search in action.","2":"Product comparison result \u2014 side-by-side specs and prices from your own catalogue.","3":"Live Human Chat active \u2014 visitor chatting with a real agent after requesting human help.","4":"Admin Live Chats dashboard \u2014 two-panel interface showing active, waiting, and closed sessions.","5":"General Settings panel \u2014 AI provider selection, API key input, and Amazon affiliate tag.","6":"Chat Appearance tab \u2014 primary color, icon picker, welcome message, and font controls.","7":"Live Chat settings \u2014 enable toggle, notification email, timeout thresholds, and offline message.","8":"Basic AI mode \u2014 the built-in assistant answering a policy question with no API key required."}},"plugin_section":[],"plugin_tags":[90336,2364,2379,247874,286],"plugin_category":[45],"plugin_contributors":[265289,266869],"plugin_business_model":[],"class_list":["post-298319","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-chat","plugin_tags-chatbot","plugin_tags-live-chat","plugin_tags-shopping-assistant","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-fahadali158","plugin_contributors-winalttechnologies","plugin_committers-fahadali158","plugin_committers-winalttechnologies","plugin_support_reps-fahadali158"],"banners":{"banner":"https:\/\/ps.w.org\/winaltchat-for-woocommerce\/assets\/banner-772x250.png?rev=3582152","banner_2x":"https:\/\/ps.w.org\/winaltchat-for-woocommerce\/assets\/banner-1544x500.png?rev=3582152","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/winaltchat-for-woocommerce\/assets\/icon-128x128.png?rev=3582152","icon_2x":"https:\/\/ps.w.org\/winaltchat-for-woocommerce\/assets\/icon-256x256.png?rev=3582152","generated":false},"screenshots":[],"raw_content":"\n
WinaltChat<\/strong> adds a fast, intelligent chat widget to your\nWooCommerce store. Customers can search your product catalogue,\nget instant answers about shipping and returns, and \u2014 when they\nneed a real person \u2014 connect to your support team through a built-in\nlive chat system, all without leaving your store.<\/p>\n\n We aim to respond to all support requests within 48 hours.<\/p>\n\n This plugin connects to third-party AI providers only when you\nconfigure an external AI mode and enter your own API key. In Basic\nAI mode and during live human chat, no external AI service is used.<\/p>\n\n AI Providers (optional \u2014 only when an API key is configured)<\/strong><\/p>\n\n Customer messages, recent conversation context, and relevant store\nand product context are sent to the AI provider you select so it\ncan generate a response. No data is sent to these providers when\nusing Basic AI mode.<\/p>\n\n Amazon Associate Program (optional \u2014 only when a tag is configured)<\/strong><\/p>\n\n When the Amazon fallback is enabled and no matching product is\nfound in your store, the plugin generates an Amazon search link\nwith your Associate tag. No customer data is transmitted to Amazon\nby the plugin \u2014 the link simply directs the visitor's browser.<\/p>\n\n No. The built-in Basic AI mode handles product search, comparisons,\npolicy questions, and conversation without any API key or external\nservice. Real AI mode (Groq, OpenAI, Claude, Gemini) is optional\nand improves response quality for complex queries.<\/p><\/dd>\n No. It runs entirely within your WordPress site using the WordPress\nREST API. No Pusher, no LiveChat subscription, no third-party\naccounts needed.<\/p><\/dd>\n Two ways: a browser notification fires in the Live Chats tab (if\nyou grant notification permission), and an email is sent to your\nconfigured notify address. Keep the Live Chats tab open while\nyou work to stay marked as online.<\/p><\/dd>\n The AI assistant keeps helping the customer seamlessly. A message\nexplains the team is unavailable, and the customer is offered an\noptional email field so you can follow up. No dead ends.<\/p><\/dd>\n At 90 seconds of no response, the visitor sees a friendly\n\"thanks for your patience\" message. At 5 minutes, the chat\ngracefully returns to AI mode with an email capture option. Both\nthresholds are configurable in the Live Human Chat settings.<\/p><\/dd>\n Currently any admin with the manage_options capability can see and\nreply to all live chats. Multi-agent role management is planned for\na future release.<\/p><\/dd>\n Deleting the plugin via the WordPress Plugins screen automatically\nremoves all WinaltChat settings, options, and live chat database\ntables from your site.<\/p><\/dd>\n Yes. The chat widget is injected into the page footer and uses its\nown scoped CSS so it does not conflict with theme styles.<\/p><\/dd>\n The AI chat widget loads asynchronously and does not block page\nrendering. Live chat polling only runs while an active live session\nis in progress \u2014 normal AI chat and idle pages make zero polling\nrequests.<\/p><\/dd>\n\n<\/dl>\n\n\nAI Shopping Assistant<\/h4>\n\n
\n
Live Human Chat<\/h4>\n\n
\n
Privacy & Security<\/h4>\n\n
\n
Bundled Libraries<\/h4>\n\n
\n
assets\/js\/vendor\/purify.min.js<\/code>; not loaded\nfrom a CDN. \u00a9 Cure53 and other contributors. Dual-licensed under\nthe Apache License 2.0 and Mozilla Public License 2.0, both\nGPL-compatible. github.com\/cure53\/DOMPurify<\/a><\/li>\n<\/ul>\n\nRequirements<\/h4>\n\n
\n
Support<\/h4>\n\n
\n
External Services<\/h3>\n\n
\n
\n
\n
winaltchat-for-woocommerce<\/code> folder to\n \/wp-content\/plugins\/, or install directly via the WordPress\nPlugins screen.<\/li>\n\n
Do I need an API key to use this plugin?<\/h3><\/dt>\n
Does Live Human Chat require any external service?<\/h3><\/dt>\n
How does the admin know a customer is waiting?<\/h3><\/dt>\n
What happens if no admin is online when a customer asks for help?<\/h3><\/dt>\n
How long before an unanswered live chat falls back to the AI?<\/h3><\/dt>\n
Can multiple admins handle chats at the same time?<\/h3><\/dt>\n
How do I remove all plugin data on uninstall?<\/h3><\/dt>\n
Does it work with my theme?<\/h3><\/dt>\n
Will it slow down my site?<\/h3><\/dt>\n
1.10.5<\/h4>\n\n
\n
$_SERVER<\/code> accesses in wp_unslash()<\/code> only, which satisfies the \"unslashed\" half of the WordPress.Security.ValidatedSanitizedInput<\/code> sniff but not the \"sanitized\" half \u2014 the sniff separately requires a sanitizing function call (e.g. sanitize_text_field()<\/code>) at the same point. Both call sites now use sanitize_text_field( wp_unslash( $_SERVER[...] ) )<\/code>, matching the pattern already used two lines below for REMOTE_ADDR<\/code>. No functional change (first_valid_ip_from_header()<\/code> already sanitized internally).<\/li>\n<\/ul>\n\n1.10.4<\/h4>\n\n
\n
https:\/\/www.google.com\/s2\/favicons?domain=...<\/code> \u2014 an undisclosed external request to Google every time an admin opened the settings page, a WordPress.org guideline violation. Replaced with the four provider logos bundled locally at assets\/images\/providers\/<\/code>, referenced via WINALT_URL<\/code> + esc_url()<\/code>. Added assets\/images\/index.php<\/code> and assets\/images\/providers\/index.php<\/code> silence stubs matching the existing pattern.<\/li>\nTested up to<\/code> listed 7.0<\/code>, a WordPress version that has never been released. Corrected to 6.8<\/code>.<\/li>\nassets\/css\/css_readme.txt<\/code>, assets\/js\/js_readme.txt<\/code>) that had no runtime purpose and weren't excluded from the SVN push; also added them to .distignore<\/code>\/.gitattributes<\/code> as a backstop.<\/li>\nlanguages\/winaltchat-for-woocommerce.pot<\/code>, generated via wp i18n make-pot<\/code>) so translators can contribute \u2014 none previously shipped.<\/li>\n1.10.3<\/h4>\n\n
\n
1.10.2<\/h4>\n\n
\n
PROXY_HEADER_PRIORITY<\/code> in class-winalt-rate-limiter.php<\/code> was tagged @since 1.8.2<\/code>, a version that never shipped (Free went 1.8.1 \u2192 1.9.0 directly). Corrected to @since 1.10.0<\/code>, the version that actually introduced it (verified via git log -S<\/code>). All other @since<\/code> tags in the file checked out correctly.<\/li>\nvar<\/code> declarations in chat-config.js<\/code> (added after the last var<\/code>\u2192let<\/code> pass) to const<\/code>.<\/li>\nconsole.error()<\/code> calls (chat-api.js<\/code>, chat-ui.js<\/code>) behind winaltConfig.debug<\/code>, matching the existing pattern in chat-core.js<\/code>.<\/li>\nverify_nonce()<\/code> in Winalt_Live_Chat_REST<\/code> has neither the cookie-absence bypass nor any Application-Password exemption \u2014 confirmed correct, matches the \"do NOT port Pro's bypass\" comment. No change needed.<\/li>\nwp_safe_remote_post()<\/code> in all AI calls) and P-M2 (Pro's tracking-stats query, no InterpolatedNotPrepared<\/code> suppressions) both already correctly fixed; no changes needed.<\/li>\n<\/ul>\n\n1.10.1<\/h4>\n\n
\n
sessionRow()<\/code> creates each conversation row with class winalt-session-item<\/code>, but the search filter's querySelectorAll()<\/code> looked for .winalt-live-session-item<\/code> (an extra, non-existent \"live-\") \u2014 so it always matched zero elements and silently filtered nothing. This mismatch was introduced when Pro's search feature was ported to Free; Pro's own implementation was unaffected (self-consistent naming throughout). Verified against the pre-fix and post-fix file with a DOM simulation using real session data \u2014 confirmed the bug reproduces exactly as reported (no filtering, no console errors) and is resolved by the fix.<\/li>\n<\/ul>\n\n1.9.0 \u2013 1.10.0<\/h4>\n\n
\n
winalt_rate_limit_strict_cloudflare_verify<\/code> and winalt_proxy_header_priority<\/code> filters. Full details on GitHub.<\/li>\n<\/ul>\n\n1.7.3 \u2013 1.8.1<\/h4>\n\n
\n
\/chat<\/code> and live-chat routes, and repo hygiene fixes. Full details on GitHub.<\/li>\n<\/ul>\n\n1.7.2 and earlier<\/h4>\n\n
\n