| 开发者 | lucasmacon |
|---|---|
| 更新时间 | 2026年10月25日 06:36 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. This plugin is an integration with the Alter Product platform.
No. API requests are disabled until credentials are saved.
Product designs, customer order files, and mockup previews are stored on your shop server by default. Settings -> Storage lets you connect your own private AWS S3 bucket, select it for new files and explicitly migrate existing file groups between S3 and the shop server. WordPress continues to serve file downloads. AWS storage, request and transfer charges are billed to your AWS account.
New and updated local project documents, editable layers, templates and generator revisions use lossless gzip when it reduces storage size. WordPress serves decoded JSON to the editors. Older plain JSON remains readable and is compressed when rewritten. Searchable database metadata stays ordinary JSON. Raster previews and editable source layers remain separate. Private customer-order layer files are compressed and encrypted; existing referenced files migrate in small background batches. Keep WordPress salts together with database and uploads backups: replacing the salts without re-encrypting these files makes them unreadable, just like encrypted AI history and provider keys.
Yes. Store owners can create, import, duplicate, edit, and manage product designs from the WordPress admin area, then map them to WooCommerce products.
New Designer color presets use the WooCommerce attribute term's Swatch color first. Set it under Products → Attributes → Configure terms as a six-digit HEX value such as #F2EBDD. This also supplies the swatch shown in product variation dropdowns. When no swatch is set, the Designer uses an approximate palette of 116 named shades, including Clay, Sage, Ivory, Navy, Charcoal, heather and solid variants. Unknown names start as white. These previews are not manufacturer color specifications. Already mapped presets and their per-area edits are preserved; edit an existing preset in the Designer to change its color. POD imports only initialize new term swatches when the provider supplies an explicit HEX value.
Yes. Product assets, graphics, logos, backgrounds, fonts, mockups, and design templates can be imported and managed in WordPress when your plan supports it. Files can use the shop server or your configured private AWS S3 storage and are served through your site.
Use Assets → Model templates, Mannequins, Textures, and Model backgrounds. Each library has Local and Import from Alter views, download/update actions, and an explicit update check. Environment selection uses the existing shared Assets → Environments library. Downloading a model template stores it for reuse; Create model creates a separate local generator project.
The Product Generator import list contains published models with an available generator from your account or the global catalog. WordPress imports the published generator revision and model resources. Existing local projects appear under Local projects. Standalone templates belong to Assets; a linked Product Designer project displays a clickable Generator badge.
In the WordPress integration, project metadata and revision references are kept in your WordPress database. Model, project and library files use the shop server or your configured private AWS S3 storage. Alter Product serves the embedded frontend and verifies subscription/session access using the shared session limit. Downloads, missing-resource imports and explicit catalog refreshes contact Alter Product; later reads reuse your chosen storage.
No. Checkout remains unchanged. The plugin only adds configuration data, mockup previews, and edit/view design links when appropriate.
The 3D tools load inside an iframe. With the product gallery integration, the tool loads only after the customer selects 3D, leaving ordinary photo browsing available without starting a 3D session. Automatically embedded tools still load when their page opens.
Yes. Open the customer's design from a WooCommerce order and use the Printing manager to download files or save them to the order. The order item's Print files list also supports uploads, previews, downloads and selecting artwork for POD placements. Submitting a provider order requires a separate administrator action in the order's POD controls.
Yes. WooCommerce must be installed and active.
English, Polish, German, Spanish, French, Russian, Brazilian Portuguese, Simplified Chinese, Hindi, Swedish, Norwegian Bokmål, Italian, Dutch, Romanian, Greek, Danish, Czech, European Portuguese, Turkish, Ukrainian, Japanese and Arabic translations are included for the WordPress plugin's PHP and JavaScript interface. The administration area uses the language selected in Users -> Profile -> Language; the storefront uses Settings -> General -> Site Language. Standard POT, PO, MO and JavaScript JSON catalogs are bundled in the languages directory. User-created product names and the separately hosted editor use their own content and language settings.
The embed session token is requested server-side through a nonce-protected WordPress REST endpoint and then passed to the iframe with origin-verified postMessage. The iframe does not receive WordPress API credentials; API secrets remain on the server.