| 开发者 |
dresium
rgwebdev easyadv |
|---|---|
| 更新时间 | 2026年10月5日 04:29 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Dresium Try-On CTA, or shortcode [dresium_tryon]Dresium adds a "Try it on" button to your product pages. The shopper uploads a photo and the AI generates an image of them wearing the product. Everything happens on your store, with no redirect to external sites.
Yes. Dresium works as an AI virtual fitting room for clothing: t-shirts, shirts, jackets, dresses, pants, hoodies and more. Enable the Try-On button only on your fashion categories from the Categories tab.
No. Dresium 3.x is a B2B service: you (the merchant) buy credits, your customers use the virtual try-on for free with no signup required. Guest access is enabled by default.
The plugin is free to install. Each successful image generation consumes credits from your Dresium balance, and failed generations are refunded automatically. Pricing is dynamic: the credit price, credits per generation and minimum recharge are configured server-side by Dresium and fetched by the plugin every hour. The Billing tab always shows the current cost per generation that will apply to your next top-up. Existing credits are always spent at the rate contracted at purchase — future pricing changes never invalidate deposits already made.
Credits are billed in EUR (€) via secure Stripe checkout. Merchants outside the Eurozone see the checkout amount in EUR; the actual charge on your card is in your local currency at your bank's daily exchange rate (banks typically add a 0–3% FX fee depending on the card issuer; fintech cards such as Revolut, Wise or N26 usually have 0% FX fee).
Shoppers see the product on themselves before buying, which removes many "it looked different" returns. The Analytics dashboard tracks purchases and refunds attributed to try-ons, so you can measure the effect on your own store.
Dresium is designed to work with most WooCommerce themes. It has been tested with Storefront, Astra, Kadence, Woodmart and Flatsome. The button can be positioned via three integration methods: automatic hook, Gutenberg block, or the [dresium_tryon] shortcode.
Themes built with page builders often replace the WooCommerce product page layout with their own, which prevents the automatic hook from firing. In this case, add the button manually where you want it inside the builder:
[dresium_tryon][dresium_tryon][dresium_tryon]A dedicated Shopify app is coming soon. For other e-commerce platforms (BigCommerce, Magento, custom systems) a universal JavaScript SDK is on the roadmap. Contact support@dresium.com if you want to be notified when they are released.
Yes, Dresium is fully compatible with WooCommerce High-Performance Order Storage (HPOS).
Photos are transmitted over HTTPS to Dresium servers for AI processing. They are not permanently stored unless the customer explicitly saves them. Photos are never shared with third parties or used for AI training. See the Data Processing Agreement for full details.
Yes. Before the Try-On button is exposed to customers, you must sign a Data Processing Agreement inside the Legal tab (GDPR Article 28). If the DPA is not signed, the button stays invisible on the storefront and no data is transmitted. Customers can request deletion of their photos at any time.
When a customer generates a try-on and purchases the same product within 7 days, the sale is attributed to Dresium in the Analytics dashboard. Refunds within the same window are subtracted from attributed revenue. Guest purchases (no customer_id) are not attributed.
main.rateLimit localization in IT/EN/FR/DE/ES.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
<link rel="stylesheet"> output in output_section_appearance() (bypassing wp_enqueue_style which could HTML-escape the & characters in the CSS2 URL bundle).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.round(eur * 100). Retrocompatibility layer accepts legacy *_cents POST parameters.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)./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.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).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.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.Dresium_Pricing_Cache client fetches the current B2B pricing (credit price, credits per image try-on, credits per animate video, minimum recharge and whitelabel threshold) from the Dresium server every hour via the public endpoint GET /wp-json/dresium/v1/pricing/current. Cached in a WP transient. Fallback to hardcoded defaults if the endpoint is unreachable.sprintf(__()) with placeholders — automatically reflect the current pricing._n(...).dresium_price_per_cred, dresium_image_credits_at_purchase, dresium_video_credits_at_purchase, dresium_min_topup_at_purchase, dresium_wl_threshold_at_purchase). Future pricing changes never invalidate deposits already made.readme.txt Pricing & currency section rewritten to explicitly explain that the values shown are current defaults and that the Billing screen always shows the up-to-date pricing.:root and on the .dresium-tryon-block container (fixes theme override on themes with block-scoped defaults like Kadence).button:hover/focus/active in the parent theme (Kadence, Astra, Woodmart) overrode the Try-On button on click, briefly making the label unreadable.--dresium-tryon-radius — step badges, close buttons, notice boxes, preview containers, replace-photo button, gallery navigation arrows, gallery scope toggle, loading progress bar and reference images all react to the merchant's radius setting instead of being hardcoded.<script> tag in the FAQ content; it broke next-intl's ICU parser and caused the placeholder key to leak into the rendered page.interest field was made optional on the backend since the redesigned form no longer collects it. Previously the endpoint returned HTTP 400 rest_missing_callback_param.Dresium > Statistiche is now a server-rendered dashboard with 7/30/90-day filter, Chart.js daily trend, top products, and CSV export. Fully backed by real merchant analytics from Dresium servers.Dresium Try-On CTA, and shortcode [dresium_tryon].dresium.php reduced from 1785 to 340 lines (-80%). class-dresium-api-client.php reduced from 1475 to 130 lines (only HMAC B2B methods retained).