Dresium – AI Virtual Try-On & Fitting Room for WooCommerce

Änderungsprotokoll

3.4.18

• Fixed: the try-on button could silently fail on sites with aggressive full-page caching, falling back to the login prompt even for logged-out visitors who were supposed to use guest mode — storefronts behind WP Rocket, LiteSpeed Cache, Cloudflare APO, SG Optimizer or similar page caches served the same cached HTML to every guest visitor, including the embedded WordPress REST nonce. Once that cached nonce became older than the WordPress 24-hour nonce window, every subsequent try-on request returned 403 rest_cookie_invalid_nonce and the widget degraded to the „please log in“ screen with no actionable error for the shopper. The authentication of storefront REST calls has been reworked to use a time-based HMAC token (X-Dresium-Token) that stays valid regardless of how long the HTML sits in a page cache. The legacy nonce header is kept as a fallback so visitors who load an older cached HTML (served by browser cache from a previous version) continue to work during the rollout.

3.4.17

• Fixed: Dresium logo in the guest wizard and event-preset modal was rounded when the merchant set a custom border radius — the override that preserves the logo rectangular shape previously covered only the main, loading and result modals. The guest wizard logo (shown to shoppers who are not logged in) and the event-preset modal logo were missing from the exclusion list and inherited the merchant’s custom corner radius, visibly distorting the Dresium branding. Both are now explicitly included in the exclusion rule.

3.4.16

• Documentation: added explicit price per generation (€0.10) in both the Pricing section and the FAQ — merchants can now see the current cost (10 credits × €0.01 per credit = €0.10 per try-on) directly on the WordPress.org listing without having to install and open the Billing tab. The disclaimer that pricing is dynamic and that the Billing tab always shows the live value before top-up is preserved.

3.4.15

• Fixed: 41 admin strings were showing in English regardless of the WordPress locale — several merchant-facing strings in the Dresium settings (Billing/currency notice, Low-balance email reminder section, Categories page explanatory text, Advanced tab „Shadow DOM“ and „JS fallback for page builders“ descriptions, „Reactivation needed“ notices, „Font preview is approximate“ warning) were present in the source code but missing from the translation files. All six locales (Italian, French, German, Spanish, English US and GB) now have the complete translations.
• Changed: internationalized the „Font preview is approximate“ warning — the warning on the Appearance tab was previously hard-coded in Italian, so merchants on non-Italian stores saw Italian text. The source has been translated to English and the Italian translation moved to the PO file.

3.4.14

• Removed: legacy B2B onboarding form (admin.php?page=dresium-b2b-onboarding) — the pre-v3.4.0 manual onboarding form has been removed. The sole onboarding flow from now on is the „Claim 1,000 free credits“ button in the Dresium admin home (added in v3.4.0), which registers the merchant AND grants the welcome bonus in a single click. Having both flows was confusing: merchants who used the legacy form got a 0-credit account and often didn’t realize they also needed to click Claim to receive the bonus. The two „Complete onboarding“ / „Complete setup“ buttons in the Statistics page and in Dresium > Settings tabs now redirect to the plugin home where the Claim button lives.

3.4.13

• Fixed: WordPress.org readme compliance — removed the easyadv entry from the Contributors header because it is not a valid WordPress.org username (import warning), and shortened the Short Description from 196 to 136 characters to stay within the 150-character limit required by the plugin directory.

3.4.12

• Changed: FAQ updated — Shopify app is now live, no longer „coming soon“ — the FAQ answer „Can I use Dresium on platforms other than WooCommerce?“ previously said the Shopify app was coming soon. The Dresium Shopify app is now officially published on the Shopify App Store (https://apps.shopify.com/dresium), and the FAQ has been updated accordingly.

3.4.11

• Fixed: residual camera icon and „No photos uploaded“ text during the first photo upload — follow-up to 3.4.10. The two „Upload your first photo“ / „Or take a selfie“ buttons were hidden during the upload procedure, but the camera icon and the „No photos uploaded“ text in the same container were still visible on top of the grid loading the newly uploaded photo. Now the entire empty-state block (icon + text + buttons) is hidden together while the upload is in progress.

3.4.10

• Fixed: no more flash of the empty-state buttons when confirming the crop of the first photo — follow-up to the fix in 3.4.9. The „Upload your first photo“ and „Or take a selfie“ buttons are now hidden as soon as the user clicks either one of them, stay hidden through the crop step, and are restored only if the user cancels the procedure (closing the file picker without choosing a file, closing the crop modal with the X / backdrop / Cancel, denying webcam access, or canceling the webcam dialog). This eliminates the brief visual flicker between crop-confirm and the newly uploaded photo tile appearing in the grid.
• Internal: CropModal.open now accepts a third argument onCancel that fires when the user closes the crop modal without confirming. Previously there was no way to tell apart „crop confirmed“ from „crop cancelled“ at the call site.

3.4.9

• Fixed: hover feedback restored on the empty-state photo upload buttons — the „Upload your first photo“ and „Or take a selfie“ buttons in the empty Photos tab had an override that forced their background to stay white on hover, making them look non-interactive. They now use the standard secondary-button hover (#f9fafb) consistent with the rest of the Try-On UI.
• Fixed: flash of empty-state buttons after cropping and confirming the first photo — after confirming the crop of the first uploaded photo, there was a brief visual flicker where the „Upload your first photo“ and „Or take a selfie“ buttons appeared alongside the newly uploaded photo tile. The empty-state container is now hidden immediately when the photo grid starts loading, so the user never sees the old empty UI during the reload.

3.4.8

• Improved: clearer feedback when a photo is already the default — in the Setting modal, after a customer uploads their first photo (which is auto-selected as the default), the „Select this photo“ button becomes disabled with no explanation, leaving the user wondering what to do. The button label now switches to „Photo selected“ (localized in IT/EN/FR/DE/ES) whenever it is disabled, making the state obvious. When another photo is clicked, the label switches back to the original „Select this photo“ and the button becomes clickable again.

3.4.7

• Fixed: Try-On modals now actually get localized when Shadow DOM isolation is enabled — this was the root cause of all residual Italian strings reported on non-Italian storefronts. When Shadow DOM CSS isolation is enabled (available since 3.0.14, now the default on new installs since 3.4.1), the Try-On dialog markup is moved from the light DOM into the <dresium-tryon-app> custom element’s Shadow DOM. The hydrateI18n() function used document.querySelectorAll('[data-i18n]') which does NOT traverse Shadow DOM, so every data-i18n element inside the dialog markup (161 elements per the test instance — size modal title, setting sidebar labels, step headers, all buttons, etc.) kept the fallback Italian text from the PHP template regardless of the browser locale. hydrateI18n() now explicitly recurses into every shadowRoot under the scope. All i18n-eligible elements are now properly translated at page load.

3.4.6

• Fixed: Try-On storefront UI now ALWAYS follows the browser language, not the store language — previous versions prioritized the WordPress site locale (set by the merchant) over the shopper’s browser locale on WooCommerce, so a shopper with an English browser visiting an Italian store would see Italian strings in the Try-On widget (e.g. „Qual è la tua taglia?“ instead of „What’s your size?“). The locale picker is now navigator.language → navigator.languages[] → data-locale → html[lang] on both WooCommerce and Shopify, matching the original design intent and the behavior shoppers expect. The site locale remains as a secondary fallback only if the shopper’s browser language is not one of the five supported languages (IT/EN/FR/DE/ES).
• Internal: both pickI18nDict() (UI strings) and pickLang() (curiosities language) now share the same browser-first priority order.

3.4.5

• Fixed: „Sign in to continue“ overlay now localized — the overlay shown to guest shoppers who open the Try-On settings/gallery (title, description and „Sign in“ button) was hardcoded in Italian regardless of the browser locale. Now fully localized in IT/EN/FR/DE/ES.
• Fixed: fullscreen gallery arrow buttons now read correctly in screen readers — the „Previous“ / „Next“ ARIA labels on the zoom modal navigation were set to Italian at creation time and only replaced on page load (not when the buttons were newly created). Now set to the user’s browser language from the start.
• Fixed: „My Dresium look“ share title and „Copy the link“ prompt now localized — the title passed to the native Web Share API and the fallback copy-link prompt were in Italian. Now in the user’s language.
• Fixed: „Checking…“ transient tooltip on the Animate button — brief tooltip during eligibility check was in Italian. Now localized.
• Fixed: „Generated outfit“ alt text on gallery tiles — now follows the browser language instead of being hardcoded in English, improving screen-reader experience for non-English shoppers.

3.4.4

• Fixed: more residual Italian strings localized — follow-up to 3.4.3. Fixed the video badges in the gallery („Generate video“, „Generating…“, „Play video“, „Stop video“) that remained in Italian regardless of the browser locale, the „Saved“ confirmation on Setting dropdowns, and the „Preset occasion“ / „Close“ ARIA labels in several modals that lacked a client-side translation attribute. All strings are now covered in IT/EN/FR/DE/ES.

3.4.3

• Fixed: storefront UI no longer shows a mix of languages — several hard-coded Italian strings in the gallery and share flows (button titles „Delete / View / Share / Open fullscreen“, „Error: …“, „Network error“, Instagram share instructions) were previously shown in Italian regardless of the browser language. These strings are now fully localized in all 5 supported languages (IT/EN/FR/DE/ES).
• Fixed: race condition in client-side locale detection — if the i18n bundle wasn’t yet loaded when the first translation lookup happened, the detector cached an empty dictionary and every subsequent string fell back to the hard-coded fallback (always Italian) for the rest of the session. The cache now only stores a non-empty dictionary.
• Fixed: automatic English fallback when a key is missing — if a translation key is missing from the user’s locale (e.g. French), the lookup now falls back to English before falling back to the hard-coded Italian fallback in the source. Previously French/German/Spanish shoppers would see occasional Italian strings scattered through the UI.
• Added: missing „common.*“ translation keys — delete, view, share, fullscreen, error, unknown, networkError, networkErrorReload, share.instagramTitle, share.instagramInstructions — in all 5 languages.

3.4.2

• Fixed: Try-On button now appears out of the box after activation — on fresh installs with the default category configuration, clicking „Activate the Try-On button“ now immediately shows the button on all product pages, without requiring manual category selection. Previously the storefront kept the button hidden until at least one category was explicitly saved.
• Fixed: your Style preferences are now reflected everywhere automatically — the preferences you set in Settings > Style (scene, action, time of day, weather, expression, framing) are now pre-populated in the Try-On wizard’s „Personalize scene“ step without requiring a Save click first. Changes auto-save on every dropdown change (debounced), synced to both your local browser and your server account.
• Fixed: „Claim 1,000 free credits“ flow no longer loops after a server-side reset — an edge case where clicking the claim button could ping-pong between „already claimed“ and „please claim“ has been resolved. The claim rate limit was also relaxed from 1/5min to 5/5min per IP to accommodate normal retries.
• Changed: legal setup is now a soft, dismissible reminder — the Legal tab banner no longer says „try-on generation is blocked“; it now explains that signing Privacy, DPA and Terms is optional but recommended for GDPR compliance. The reminder is shown as a dismissible card on the Dresium admin home (not as a WordPress admin notice) and can be hidden for 30 days.
• Changed: Categories tab shows the current state clearly — the Categories tab now displays an info banner explaining „Try-On is shown on all categories by default“ with all categories pre-selected. Uncheck specific categories and save to limit the Try-On button to a subset.
• Added: „Reactivation needed“ banner on the Settings tabs — if your Dresium account was reset or deleted server-side, the Settings tabs now show a clear path back to the Dashboard with a one-click reactivation CTA, instead of raw „Cannot load…“ error messages.
• Improved: Try-On activation card UI — removed the 720px max-width constraint so the activation card uses the full admin width on wide screens. Fixed button overflow and the loss of rounded corners on focus/active states; buttons no longer inherit WordPress admin’s default button border.
• Improved: copy on the free-credits CTA — reworded for clarity („no financial commitment, no card required“) and expanded to a short narrative pitch instead of a terse button label.
• Improved: full translations in all 6 locales — Italian, English (US / GB), French, German and Spanish retranslated for all v3.4.x strings (legal tab, activation card, reactivation banner, info banners, Settings style preferences).
• Internal: diagnostic endpoint opcache-reset.php (admin-only) added for troubleshooting merchant HMAC state on live servers where WP-CLI is unavailable. Reverted a shadow-DOM CSS bundle change that caused a regression in a subset of themes; v3.4.1 shadow-DOM behavior is restored. A developer-only „Reset locale“ button is also available in the admin home when DRESIUM_DEV_MODE is defined in wp-config.php.

3.4.1

• Added: „Dashboard“ quick link in the Plugins list — a direct shortcut to the Dresium admin landing right from the „Installed plugins“ row, next to Settings and Deactivate.
• Added: one-click Try-On activation on your product pages — a dedicated card on the Dresium admin page lets you turn on the Try-On button on your WooCommerce products with a single click. Works on both classic WooCommerce templates and modern block themes (Gutenberg / Full Site Editing). You can disable the automatic placement in one click if you prefer the shortcode or Gutenberg block.
• Changed: automatic Try-On button is now OFF by default on new installs — nothing appears on your storefront until you explicitly activate it. Existing installs keep their current behavior unchanged.
• Changed: readme highlights the 1,000 free credits — the plugin page on WordPress.org now makes clear that the full plugin is testable for free with 1,000 welcome credits.

3.4.0

• Added: 1,000 free credits to try the plugin — the first time you open the Dresium admin page, a welcome box offers 1,000 free credits with a single click. Credits are added immediately, no payment or billing setup required. They are consumed only when a shopper actually generates a virtual try-on on your storefront.
• Added: video tutorial in the admin landing — a 2-minute embedded walkthrough shows exactly what shoppers experience and how to configure the plugin.
• Changed: legal acceptance is now optional — the „Privacy / DPA / Terms“ banner is no longer blocking. Try-On works out of the box; signing the GDPR legal pack is a one-click reminder you can dismiss for 30 days from the Dresium admin page. This mirrors how our Shopify app behaves, removes friction for new installs, and leaves the data-controller responsibility with the merchant.
• Changed: no more forced onboarding redirect — opening WooCommerce → Settings → Dresium no longer forces a redirect to a mandatory onboarding form. The merchant account is created automatically the first time you claim the 1,000 free credits.
• Changed: storefront no longer hidden when legal is unsigned — the Try-On button now appears on your product pages even if you haven’t signed Privacy/DPA/Terms yet.
• Internal: client support for the new /woocommerce/claim-free-credits endpoint.

3.3.1

• Fixed: event presets now consistently generate the matching scene — tapping „First date“, „Fashion show“, „Job interview“ or „Wedding“ sometimes produced an unrelated background (e.g. a fashion-show preset generated a beach scene) because any saved Style defaults (scene/time/weather/action) could compete with the event preset at generation time. The event preset now always wins over saved custom scene fields; if no event preset is selected, saved defaults keep working exactly as before.

3.3.0

• Added: body-shape picker before each try-on — shoppers choose an approximate size (XS to XXL) with a visual silhouette before generating. This hint helps the AI render body proportions more accurately. Visually a 2×3 grid of silhouette thumbnails; one tap and continue. The chosen size is remembered in the browser for subsequent try-ons but can be changed any time. Does not change which product variant goes into the cart — that’s still the variant selected on the product page.
• Removed: redundant „Build“ dropdown from Custom Scene and Guest wizard — the new body-shape step replaces it. The Style settings page keeps a default build selector for logged-in customers who want to set a profile-wide preference.

3.2.3

• Fixed: SVG icons clipped when the merchant used a custom radius — the cascade that applies the merchant-configured corner radius to modal elements was also rounding/clipping the icon SVGs inside modals (close × , back arrows, download, play, share, chevrons, check marks). Re-applied the targeted neutralization rule (border-radius 0 + overflow visible + no mask/clip) on all <svg> descendants of Dresium dialogs. The fix was in place in a previous version but was lost during a modal split refactor.

3.2.2

• Added: visual feedback on the Add-to-cart button — after a successful click the button animates from brand purple to green with a check-mark icon, confirming the item was added. No toast, no popup — zero friction UX.

3.2.1

• Fixed: Add-to-cart from the try-on result modal didn’t actually add items — WooCommerce initializes the cart/session only during standard page requests, not during REST API calls, so the backend add silently failed. The endpoint now bootstraps WC session + customer + cart handlers before adding, and explicitly persists the cart cookie after the add. Both guest and logged-in sessions work.

3.2.0

• Added: Add-to-cart button in the try-on result modal — after a successful virtual try-on, shoppers can add the product to their cart in one click without leaving the result modal. The size and any variant currently selected on the product page (or the first available variant if none selected) is used automatically — no size picker, no interruption. Mini-cart badge refreshes via standard WooCommerce fragments; works on all WC-compliant themes.

3.1.0

• Added: low-balance email reminder — enable optional email alerts in WooCommerce > Settings > Dresium > Billing. When your credit balance drops below your chosen threshold, Dresium sends a reminder to your contact email (at most once per day while the balance stays low). Email language follows your WordPress admin language, with English fallback. Delivered from info@dresium.com via your site’s existing SMTP setup.

3.0.16

• Fixed: misleading error message when the store runs out of credits — the storefront previously showed „Oops! The service is being updated. Please try again in a few minutes.“ for a 402 insufficient-balance response. It now correctly says „The store has run out of credits. Please try again later.“ in all 5 supported languages (IT/EN/FR/DE/ES).
• Fixed: generic daily rate limit fell back to Italian in all languages — the i18n key for the generic 429 message was missing from the storefront bundle, so non-Italian shoppers saw the Italian fallback. Added main.rateLimit localization in IT/EN/FR/DE/ES.
• Fixed: AI service unavailable (503) showed raw backend text — when the AI pipeline is temporarily down, the storefront now shows a dedicated localized message („The service is temporarily unavailable. Please try again in a few minutes.“) instead of a raw Italian server message. Both guest and logged-in flows are covered.

3.0.15

• Fixed: crop modal could accidentally close during drag — when a crop drag ended outside the image area, the modal treated it as a backdrop click and closed, cancelling the operation. It now closes only on a real click on the modal backdrop.
• Added: take a selfie on the spot when logged in — previously only guest visitors had this shortcut. On mobile it opens the front camera directly; on desktop it opens a webcam capture dialog. The existing „upload from device“ path is unchanged.

3.0.14

• Shadow DOM CSS isolation — try-on modals are now fully isolated from your theme’s CSS. Enabled by default on fresh installs, disabled by default on existing installs (opt-in from WooCommerce > Dresium > Advanced, to avoid any visual change without your consent). Solves cross-theme conflicts on themes with aggressive CSS resets (Kadence, Astra, Divi, Bricks, and themes based on normalize.css / html5boilerplate). Includes a JavaScript fallback for page builders that skip WooCommerce hooks (Elementor Pro Product Templates, Divi Theme Builder, Bricks Builder).
• Product category picker — the Advanced tab now shows product categories as a nested tree with strict parent-child logic: enabling a subcategory requires its parent to be enabled too. Much clearer to configure than the previous flat list.
• Fullscreen gallery: video first — when a product image has an associated video, the fullscreen gallery now opens directly on the video instead of the static image.
• Minor bug fixes.

3.0.13

Critical fix: theme compatibility. Some WordPress themes (with CSS resets inherited from normalize.css / html5boilerplate) applied dialog { display: block }, which overrode the browser default dialog:not([open]) { display: none } and caused all Dresium try-on modals to appear as visible blocks at the bottom of product pages when closed. Fixed by restoring the browser default via a targeted rule on Dresium dialogs only.

3.0.12

Minor bug fixes

3.0.11

Minor bug fixes

3.0.10

Minor bug fixes

3.0.9

Minor bug fixes

3.0.8

Minor bug fixes

3.0.7

Post-3.0.3 refinement release. Consolidates fixes and UX improvements from 3.0.4 → 3.0.7 development iterations. Backwards compatible with 3.0.3 — no data migration, no re-onboarding required.

Admin UX — Appearance tab

• Live preview on the Preview button and on the Button Size tiles (small/medium/large) now reflects all style changes in real time: palette, custom colors, uppercase, show-icon, CTA text, border radius and font family — previously radius and font were applied silently only after saving.
• Border radius is applied live to the Preview button and the Button Size tiles via JavaScript listeners on the slider and the number input.
• Font family is applied live to the Preview button and the Button Size tiles by loading the 12 Google Fonts of the whitelist (Inter, Poppins, Montserrat, Roboto, Open Sans, Lato, Raleway, Nunito, Playfair Display, Merriweather, Lora, DM Sans) directly in the admin page via <link rel="stylesheet"> output in output_section_appearance() (bypassing wp_enqueue_style which could HTML-escape the & characters in the CSS2 URL bundle).
• Font application uses document.fonts.ready to re-sync the preview once the Google Fonts WOFF2 files are actually downloaded, avoiding the initial pageload flashing with the system font.
• Fallback family per-font-category (serif vs sans-serif) so if a Google Fonts file fails to load, the preview at least maintains the correct typography category.
• Added a yellow disclaimer under the Typography section informing merchants that the font preview is approximate and that the accurate rendering can be verified only by saving and opening a product page in a new tab.

Admin UX — Financials tab (B2B Pricing Configuration)

• Introduced a new pricing input model with 4 primary fields (image total cost in €, credits per image, video total cost in €, credits per video). The credit price is derived automatically from the image_price / image_credits ratio.
• All fields accept EUR values with 2-decimal precision (0.01 step). Backend stores in cents (integer) with round(eur * 100). Retrocompatibility layer accepts legacy *_cents POST parameters.
• Live preview info box (blue) shows internal derived credit price, example €100 top-up conversion in credits and video intrinsic value with warning if declared video cost diverges from the intrinsic value.
• New backend getters Dresium_Merchant_Balance::get_image_price_cents() and get_video_price_cents() return the costs saved directly by the admin — no more derivation via credit_price × credits which caused rounding-to-integer-cents artifacts (€0.30 / 20 credits → €0.015 was rounded to €0.02 making €0.30 incorrectly rendered as €0.40 after save).
• The endpoint /merchants/self and /pricing/current now expose image_price_cents and video_price_cents as the source of truth. Frontend (Shopify Remix admin, storefront extension, WooCommerce client plugin) consume these instead of recomputing from credit price. Fallback to legacy calculation for merchants pre-3.0.7 without the new options stored.
• Stripe checkout now uses float precision for credit calculation: credits = floor(topup_cents / (image_price_cents / image_credits)) instead of intdiv(topup_cents, credit_price_cents). Fixes an issue where a €100 top-up produced 5000 credits instead of the expected 6666 (with €0.30/20 credits config).
• Hint box in the B2B Pricing Configuration section with concrete example configuration and derived calculations to help merchants understand the credit model.

Storefront — theme compatibility

• Fixed the fullscreen zoom modal close button (X icon) being invisible on Astra theme. Astra’s default button rule applies padding: 15px 30px !important-equivalent and font-size: 16px to any button element, overriding the Dresium close button’s fixed 40×40 sizing and squishing the SVG X.
• Fix: theme-guard now applies explicit width: 48px, height: 48px, padding: 0, font-size: 0 and line-height: 1 with !important to #dresium-tryon-zoom-modal .dresium-zoom-modal__close. The inner SVG has explicit width/height: 24px and color: #ffffff with !important.

Compatibility

• No breaking changes. All previously stored merchant balances, subscriptions and auto-topup configurations continue to work unchanged.
• Zero-config upgrade: existing pricing configuration (10 credits per image, 40 credits per video, €0.10 per credit, €10 minimum recharge, €100 whitelabel threshold) is preserved. Merchants can adopt the new 4-input pricing model at any time from Financials tab.

Older releases (<= 3.0.3)

The full changelog for releases 3.0.3 and earlier (including the 3.0 beta/alpha cycle and the pre-B2B 2.x history) is available on GitHub: https://github.com/DresiumAI/dresium/blob/44aa616b/client/wp/wp-content/plugins/dresium/readme.txt