AnyTry – AI Virtual Try-On for WooCommerce

Registro de cambios

1.0.30

• Fix (reporting): when a customer returned an item, the report did not record WHICH SIZE came back — so “do try-ons reduce returns” could be answered for the shop, but never for a size. Returns now carry the returned line’s size, exactly as purchases already did. When one order returns two sizes of the same product at once, the size is left empty rather than guessed, because naming one would misreport the other.

1.0.29

• Fix (privacy): size recommendations were sent to AnyTry without the visitor’s session identifier, so the body measurements stored against them could not be found when that shopper later asked for their data to be deleted. The identifier is now sent, exactly as it already was for try-ons. Measurements recorded before this update remain unreachable by session and can only be removed by deleting the plugin data or asking AnyTry support.
• New: “Also remove these settings” in Security and Limits, off by default. Previously, deleting the plugin also deleted your API key and your Size Advisor choice, so reinstalling it left the Size Advisor silently switched off. Your settings now survive a reinstall unless you tick this box. Customer data — try-on history, session identifiers, queued events and cached images — is still removed when the plugin is deleted, whatever this box says.

1.0.28

• Fix (billing): if the page was reloaded at the exact moment a try-on was being sent, the try-on was still created and charged on the AnyTry side, but the browser was left with no way to reach it — no result, and no way to cancel it either. The plugin now remembers the pending send and, on the next page load, asks AnyTry to cancel that try-on. A try-on that has already started generating cannot be cancelled and stays charged, because the work has genuinely been done.
• Internal (analytics contract): checkout and conversion events now use the API’s canonical source field, identify the plugin release where raw diagnostics need it, and no longer send redundant domain/send-time fields or unused lists of all products and jobs tried during the session.
• Fix (analytics): the number of size measurements reported to AnyTry counted every time a size recommendation was drawn on screen, including when it was redrawn from cache — for example when switching back and forth between saved try-ons. It now counts only genuine new measurements. Expect the “measured sizes” figure in the AnyTry portal to fall after this update: the earlier number was overstated, the new one is the real one.
• Fix: when a photo was rejected because of its file type, the message said it was “too large or in the wrong format” and advised trying a smaller photo — unhelpful when the file was tiny and the format was the only problem. Size and format now get their own messages.
• Internal (diagnostics): the ways a photo can be rejected before upload now report a stable machine-readable code to AnyTry instead of a truncated translated sentence, so those faults can be counted the same way regardless of shop language. Other error paths are unchanged.
• Compatibility: verified on WordPress 7.1.

1.0.27

• Fix: the daily try-on limit shown in the settings screen said 30 while the plugin actually allowed 50. The screen now shows the limit that is really applied; nothing about the limit itself changed.
• Change: the analytics figures were removed from the plugin’s settings screen. They were fetched from AnyTry on every visit to that screen and never shown, so the page now loads without that request. Your statistics live in the AnyTry portal.
• Internal: events sent to AnyTry now carry the plugin version and the time the event actually happened (order date, refund date), instead of only the time they were received. This makes reporting accurate when an event is delivered later than it occurred.

1.0.26

• Fix (statistics honesty): a completed order was marked “reported” the moment the plugin handed the purchase over to be sent, not when the AnyTry service confirmed it had arrived. If that send then failed — a server hiccup, a timeout, a missing API key — the purchase was lost permanently: the order was already marked as done, so it was never tried again. Purchases are now queued and retried until they are genuinely delivered, and the order is only marked once every item has arrived.
• Fix (statistics honesty): a refund could be reported for an order whose purchase never arrived, which is what produced returns with no matching sale in your statistics. A refund now waits for its purchase and is sent afterwards, rather than being sent regardless or dropped.
• Fix: if the purchase reached the plugin only after the order had already changed status — which is normal with bank and BLIK-style payment confirmations — the sale could go unreported entirely. It is now recorded at that point too.
• Fix (privacy): the checkout form’s hidden tracking field was only filled in when analytics were enabled, but the code receiving it did not check. Withdrawing consent between opening and submitting the checkout could still attach try-on data to the order. Both sides now check.
• New: administrators are warned in wp-admin if purchase events stop reaching the server, instead of it happening silently. Site owners with command-line access can inspect and retry the queue with wp anytry outbox status and wp anytry outbox redrive.

1.0.25

• Fix (statistics honesty): when a purchase could not be linked to the buyer’s own try-on session, the plugin used to ask the AnyTry service which shopper last tried the product and attached that shopper’s session to the sale. On shops where many customers try the same products, this credited sales to the wrong person’s session and inflated the conversion numbers your dashboard shows. Recovered matches are now recorded without any visitor identity and are labelled as server-side recoveries, so your dashboard can tell hard attribution apart from best-effort matching.
• Improvement: the buyer’s own try-on session is now saved with the order at checkout. Payment confirmations that arrive server-to-server (for example BLIK, Przelewy24 or other bank callbacks) used to lose that link about one purchase in five; those sales were still counted, but not connected to the try-on that led to them.
• Improvement: every purchase event now states how it was attributed (buyer’s own browser data, checkout form, or server-side recovery), matching what the PrestaShop plugin has always reported.
• Fix (statistics honesty): refunds and cancellations are recorded against the order they belong to, and no longer against whoever happened to be signed in when the status changed. Previously, processing a refund from the shop admin could attach that browser’s try-on session to the record; on a few orders it did. Those records now carry the order’s own attribution or none at all.
• Fix (size question): the plugin now asks WooCommerce which sizes a product is actually sold in, instead of reading the size selector out of your theme’s page. Reading the page failed in two common situations: on category and shop pages, where WooCommerce prints no size selector at all, and in any shop whose size attribute is not literally called “Rozmiar” or “Size” – a German “Grosse” or French “Taille” was invisible to it. In both cases the customer was shown your shop’s entire size range instead of the sizes that product comes in. Since the size the customer picks is what the recommendation is built on, offering a size the product is not sold in produced a confident but wrong suggestion.
• Fix (size question): on shops whose size attribute has an unusual name, the size advisor did not appear at all on product pages – no message, no error, it was simply absent. It now appears wherever the product genuinely has more than one size. Products that really do come in one size are still not asked about, as before.
• Fix (size question): starting a try-on from a “related products” or quick-view tile no longer offers the sizes of the product whose page you happen to be on. It offers the sizes of the product you actually clicked.
• Improvement (size recommendation): the size table sent to the advisor is now matched to the product’s own sizes rather than to your shop-wide setting. If your shop is set to letter sizes while a product is sold in numbers (or the other way round), the advisor is no longer asked to answer in a vocabulary your catalogue does not use, and it can no longer recommend a size that product is not available in.

1.0.24

• Fix: the numeric size table stopped at 44. Anything above that could not be entered and was never sent to the size advisor, so it could not suggest those sizes. The table now runs 32 to 62, which covers petite and plus-size ranges. It scrolls sideways rather than stretching the settings page, and sizes you leave blank are simply not sent.
• Fix: size rows you left blank are no longer sent. Previously a table you had opened but not filled in was passed along as a row of zeros, which the advisor treated as real measurements.
• Fix: if you use the optional Cloudflare address list, a typo in one entry no longer quietly disables the origin check that entry was meant to configure. Shops that never set that list up are unaffected. A rejected entry is now written to the error log, so a mistake is visible instead of silent.
• Fix (Safari, iPhone and iPad): your photo is now kept correctly while the try-on window is open. On Safari it was never stored at all, which is why re-opening the size question or coming back to a finished try-on could ask you for the photo again. Every browser on iPhone and iPad uses Safari’s engine, so this affected all of them.
• Fix (Safari, iPhone and iPad): tapping Save now saves the picture even when the share sheet does not open in time. Before, that case tried to open a new tab, which the phone usually blocks – so the tap appeared to do nothing.
• Housekeeping: removed about 150 lines of error-handling code that nothing in the plugin has ever called, so the download is smaller. No behaviour changes.

1.0.22

• New: a single switch to pause the Try-On across the whole shop without deleting your API key or losing any other setting. Turn it back on when you are ready.
• New: test mode — the Try-On becomes visible only to the shop users you list, so you can trial it with your own staff before opening it to customers. Everyone else sees your shop exactly as it looked before the plugin was installed.
• Note: while test mode is on, conversion tracking records nothing, because ordinary customers never reach the Try-On. Turn test mode off before you start measuring sales.
• Note: pausing the Try-On stops the plugin from loading anything on your shop pages, but it does not stop conversion tracking. Sales of items a customer tried on before you paused are still recorded, so you keep the data you already paid for.

1.0.21

• Reliability: the try-on window can no longer end up in a contradictory minimized-yet-open state. Re-showing the window cleared the internal flag but left the minimized marker on the element, so which state won was decided only by stylesheet order — a reorder would have hidden both the window and the floating progress bubble at once, leaving no way back except the Try-On button.
• Reliability: the background-jobs view no longer dismantles the window (hiding the result, the upload area and the floating bubble) before checking whether it has anything to display, which could leave an empty white window.
• Reliability: switching from one product to another now always shows the correct product’s size options — or none, when the Size Advisor is turned off — instead of briefly carrying over the previous product’s size choices.
• Reliability: switching to a different product while a result is still downloading no longer shows the wrong product’s result or freezes the try-on that is still running.
• Reliability: opening the same store in two browser tabs no longer lets one tab cancel or drop the other tab’s in-progress — and already paid-for — try-on.
• Reliability: a finished try-on is now picked up correctly after a phone browser tab is briefly frozen in the background and reopened, instead of appearing stuck.
• Reliability: the Save button, and restoring a saved try-on, no longer hang on browsers where the local image store is slow or blocked to open — the widget now falls back to fetching the result instead of waiting indefinitely.
• Reliability: a size suggestion that arrives late no longer appears on top of an error screen.
• Reliability: a finished try-on shown in the multi-item comparison list now becomes clickable on its own, instead of remaining on “loading result…”.
• Reliability: a temporary network or CDN hiccup while fetching a finished try-on no longer shows a dead error. The widget now retries the same, already-generated result a few times before giving up — it never re-runs or re-charges the try-on. This closes the most common “generated but not shown” case.
• Diagnostics: clearer error categories (a connection problem is now labelled as such, an unsupported image as an image problem, instead of a generic “unknown”), and error events now include the try-on identifier so a store can see exactly which requests hit a display problem.

1.0.20

• Maintenance: translations now follow the standard WordPress.org model — the plugin ships English source text, and translations are delivered as community language packs from translate.wordpress.org rather than as catalogs bundled inside the plugin. No change to any feature or behaviour.
• Compatibility: verified on WordPress 7.0.2 with PHP 7.4 through 8.5.

1.0.19

• Security: try-on and size requests now require a real, published, try-on-enabled product and no longer accept a caller-supplied product image, preventing use of the paid try-on pipeline outside the intended flow.
• Security: an anonymous request can no longer change the store-wide streaming-proxy setting, and malformed job tokens are now rejected instead of silently ignored.
• Privacy: with analytics turned off, the storefront now writes no tracking cookie, local storage, or data-layer event.
• Privacy: Size Advisor now stays fully disabled on both the storefront and the server when turned off in settings.
• Privacy: GDPR order-data erasure now reliably removes all AnyTry order data.
• Privacy: cancellation and refund analytics are now limited to products the shopper actually tried on.
• Reliability: the page-resume mini widget loads its stylesheet correctly, cancels only its own job when closed, and clears that job’s cached photo and result.
• Admin: the Data controller example now suggests your own store name.
• Maintenance: refreshed bundled translations and added third-party licence notices; aligned the main bundle version banner.
• Compatibility: removed global PHP ini_set() overrides (max_execution_time / default_socket_timeout) that could push a host out of its configured limits — the request timeout is set on the HTTP call itself, and the live-status stream now restores its output settings on shutdown.

1.0.18

• Reliability: HEIC/HEIF photo uploads no longer emit a PHP notice during image-type detection on the try-on request (the image-info value is now always initialised).
• Maintenance: internal static-analysis hardening (PHPStan level 5, clean) and minor type-safety cleanups — no change to behaviour.

1.0.17

• Reliability: made result finalization idempotent so a very slow result download can no longer render twice or double-count a completion.
• Privacy: swapping to a new photo now clears the previous try-on’s cached result images from the browser immediately (previously cleared only on closing the try-on window).
• Accuracy: eyewear auto-detection on shop/quick-view cards no longer reads a neighbouring product’s description.
• Hardening: strip line breaks from the product category before it is sent to the API; apply the same Cloudflare source-IP verification to the conversion-tracking rate limit as the rest of the plugin.

Older entries (1.0.0 – 1.0.16) are kept in the plugin’s source repository and in the release history on wordpress.org.