PERSONAIZER – AI Chatbot & Live Chat for WooCommerce

Changelog

3.1.5

• First release on WordPress.org, with screenshots, banners and an expanded FAQ. The plugin lives in the personaizer-chat folder and updates through WordPress.org; if you installed an earlier zip, deactivate and delete it, then install this one and connect again.
• Recognising signed-in customers is opt-in again: off until you turn it on. When on, the chat also gets their profile picture.
• The PERSONAIZER page shows the persona in the title row, usage bars that can run past the plan’s limit, and what each source knows (“X of Y known”, counting what the site can send).
• “Last checked” falls back to PERSONAIZER’s own record when the site has none.

3.1.4

• The plugin moves to the personaizer-chat folder, ready for WordPress.org.

3.1.3

• Store facts no longer say “sells to every country” when that is only WooCommerce’s default setting.
• Links to pages, products and categories are sent readable (/product-category/აქსესუარები/), not percent-encoded.

3.1.2

• A sync no longer stalls on hosts where WordPress’s scheduled tasks (WP-Cron) don’t run: queued records are also sent on every refresh of the PERSONAIZER page, and after ordinary visits (once the visitor already has the page, at most every 30 seconds).

3.1.1

• While records are still being sent, PERSONAIZER shows each stream as being written (with how many are left) instead of “ready” between batches.
• Pages with no text of their own (cart, checkout, my account, or pages a theme draws from elsewhere) are no longer sent, so they stop showing up as refused.

3.1.0

• Records are named by their WordPress post ID, the same id PERSONAIZER gives them when it reads your site before the plugin is installed, so installing enriches that knowledge instead of adding a second copy. After updating, the plugin sends its full lists once more on its own; nothing needs doing.
• New Store facts stream: your shop’s name, currency, address, where it sells and ships, taxes, payment methods, time zone, privacy and terms pages, and the product category tree with links — kept current as you change those settings.
• Synced pages and posts no longer repeat their title inside the text.

3.0.5

• The settings page no longer reads the brand name when PERSONAIZER can’t be reached and no earlier answer is stored, so it renders without PHP warnings.
• After connecting, the tab lands on PERSONAIZER marked as an arrival from WordPress.

3.0.4

• The first content sync starts the moment the site is connected: the backfill now queues its first page at the end of the connect request and of every plugin-page load while it is pending, instead of waiting for WP-Cron’s next visitor. Cron remains the continuation for large catalogs.
• The brand description handed to PERSONAIZER on connect is the tagline with HTML entities decoded, so quotes arrive as quotes.

3.0.3

• No code change: a code-standards annotation in the outbox was scoped so the wordpress.org Plugin Check report reads clean.

3.0.2

• The batch insert into the outbox builds its placeholders inline, and the backfill and daily check no longer set suppress_filters explicitly — get_posts() already does, which is what keeps a language plugin from hiding the other languages’ records. Both are what wordpress.org’s Plugin Check asked for on 3.0.1.

3.0.1

• Requires WordPress 6.2 or newer: every query on the plugin’s outbox table is now fully prepared, the table name through WordPress’s %i identifier placeholder.
• The admin page’s working variables no longer live in the request’s global scope.
• The plugin’s URI is its repository, not the company site.

3.0.0

• Rebuilt from the ground up around one outbox: every change on the site becomes a row, and a worker sends rows to PERSONAIZER in batches of up to 100 — a 500-page backfill is a handful of requests instead of 500, and nothing is lost when a request dies mid-way.
• Connect tells PERSONAIZER what your site is before you get there — name, logo, colours, every language your site publishes in (WPML, Polylang, TranslatePress) with the primary first, currency, and what you sell — so the brand form on the consent screen arrives filled in and the persona can be built right there, with no crawling.
• Pages and posts are sent as real markdown (headings, lists, links, tables) instead of stripped text.
• Hidden and private WooCommerce products are no longer sent.
• The admin page is a status page: what you are connected as, whether the persona is ready, and per stream how much is synced, waiting, or refused — plus Sync now and Disconnect. Everything else is a link to personaizer.com.
• Talks to the four-call sync API introduced with this release. The plugin’s readers are tested against the API’s own recorded responses, so the two cannot drift apart unnoticed again.
• A site whose connection was removed on personaizer.com says so and offers to connect again, instead of showing its last known state as if nothing had happened.
• You must connect your site again after this update. Nothing on personaizer.com is lost.

2.1.1

• Wording follows the account model: the Identity Secret that signs customer-recognition tokens is your account’s, shared by every persona you embed, so rotating it on personaizer.com rotates it for this site too.

2.1.0

• Follows the names personaizer.com now uses: your site is an integration, what it syncs are streams, and its credential is an integration key (ik_). Existing installs reconnect once from the plugin’s settings.
• All sync calls moved to /v1/integration/…; the daily check and manifest are unchanged in behaviour.
• WooCommerce attribute taxonomies (pa_*) are left untouched by the rename.

2.0.0

• Your site is now a connector on personaizer.com: it belongs to a brand, syncs with its own key, and the lanes it syncs are switched on and off there — next to everything else the AI knows. What the plugin syncs is read-only on personaizer.com, so your site is the source of truth.
• A daily check compares each lane with what PERSONAIZER holds, pushes what is missing or changed, and removes what no longer exists on your site. “Check what’s out of date” runs it on demand.
• The consent screen asks for the brand, the persona and the lanes in one step; a site can sync knowledge without embedding a widget.
• You must connect your site again after this update — see Updating. Nothing on personaizer.com is lost.

1.3.1

• Conversations started from your site now show as “WordPress” in the PERSONAIZER inbox and analytics, instead of a generic website embed. Nothing about what is sent changes — the widget just tells PERSONAIZER which plugin it is running in.

1.3.0

• AI Search has been removed. PERSONAIZER no longer offers the search product it was built on, so the “Let visitors search with AI” setting, the [personaizer_search] shortcode and the search box are gone. If a page still contains the shortcode, remove it from that page. Chat and content syncing are unchanged.

1.2.3

• Plugin updates now come from our GitHub releases page — the same place the plugin is downloaded from. Update notices in WordPress are unchanged; they are simply served from one place instead of two, so a released version can no longer be missing from the update check.
• No changes to how your site or its products are synced.

1.2.2

• Product photos are now described by PERSONAIZER’s image analysis, so customers can find a product by what it visibly is — its colour, its shape, or text printed on the packaging — even when none of that appears in the product’s own text. The plugin used to send the product’s name as the photo’s description, and a photo that already had a description was left alone, so this analysis never ran for any product and the name was simply repeated back.
• Your next sync re-sends every product so their photos get described.

1.2.1

• Deleting many products at once no longer leaves your AI recommending products you removed. Each deletion used to contact PERSONAIZER on the spot, so emptying a whole category meant hundreds of calls inside one page request — WordPress cut it short part-way, and every deletion it hadn’t reached yet was lost with nothing to retry it. Deletions are now recorded first and sent together, so a bulk delete arrives complete, and anything a slow connection interrupts is retried instead of dropped.
• Deleting a single product is unchanged — it still reaches your AI right away.

1.2.0

• Products now sync with every category they belong to, not just one. WooCommerce lets a product sit in several categories and doesn’t say which is “the” one, so the plugin used to guess — and a product in two branches (say an LED driver that is both lighting and a power supply) lost one of them, along with that branch’s filters. All of its categories are now sent as full paths, and PERSONAIZER decides how to group them.
• Sub-categories are preserved as paths (“Sheet materials > Dibond”) instead of being flattened to a single name, so two different branches that happen to share a sub-category name no longer collide.
• Stores with many categories no longer fail to sync. Previously a catalog with more categories than the account’s limit was rejected outright, syncing nothing; now everything syncs and the deepest categories simply group under their parent.
• Your next sync re-sends every product, so the new categories take effect without any action from you.

1.1.2

• Display name simplified to “PERSONAIZER” (was “PERSONAIZER Chat & Search”) — no functional change.

1.1.1

• Fix: page-builder post types (Elementor, ElementsKit and similar) no longer show up as sync lanes — only genuine content types do. A collided lane label (two custom types both named “Templates”) now shows its type slug so they’re distinguishable.

1.1.0

• AI Search: an optional AI-powered search box, either the [personaizer_search] shortcode or bound to your theme’s own search field via a CSS selector. Two quality modes (Smart / Fast) trading relevance against credit cost. Off by default.

1.0.0

• One-click Connect: approve your site on the PERSONAIZER consent screen and the plugin provisions its own credentials — no IDs to copy.
• Chat widget injection, with the widget’s appearance, greeting, FAQ and contact form managed on the persona in the PERSONAIZER dashboard.
• Content sync in independent lanes — Pages, Posts and any custom post type — including featured and inline images, kept in sync through WordPress hooks. Each lane switches on and off without deleting anything.
• WooCommerce Products lane: products sync as structured commerce data (price, sale price, stock, SKU, attributes, categories, images) with per-SKU variants, and stock re-syncs in real time as it changes. Attributes in any language are supported, including non-Latin scripts.
• Check what’s out of date: compare what your AI holds against what your site actually has. It reports how many items are missing, out of date, or no longer on your site, and changes nothing — updating is a separate click that sends only the differences. It finishes immediately, so it works even where WordPress’s scheduled tasks are unreliable.
• Syncing is designed not to lose items: a rejected batch is retried item by item, anything that still doesn’t land is queued and re-tried automatically, and an interrupted sync resumes on its own. When something hasn’t synced, the plugin says why.
• Removals made while a lane is switched off are queued, re-verified against the live site, and applied when that lane resumes.
• Plan-aware syncing: content beyond your plan’s knowledge allowance is reported clearly with an upgrade link, remembered, and synced automatically once the plan has room.
• Optional recognition of signed-in customers (off by default), sending their name, email, phone and picture in a token signed with a per-site Identity Secret.
• Warns when your server is still running a cached copy of an older build, which would otherwise make an update appear to do nothing.
• Disconnect and uninstall remove every credential, setting and scheduled task the plugin created.