| 开发者 | ipomper |
|---|---|
| 更新时间 | 2026年10月8日 03:22 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
uploads/pomp-personalizer/generated/YEAR/MONTH/ for previewsuploads/pomp-personalizer/generated/print/YEAR/MONTH/ for print filespomp_configuration_ttl_days moves it.
What it costs to run
The output is vector, so nothing is rasterized. There are no image libraries in the path that draws a design, no headless browser, no queue, and no calls to anyone else's server.
Measured on the demo shop's own hosting in 40 rounds, as the time each request takes beyond an empty request to the same site, so the network and WordPress itself are left out:
wp-content/plugins/.[pomp_personalizer] and [pomp_catalog] there. A page that carries the block or the shortcode is left exactly as you built it.Choose Sold through the configurator on the product, and add a design whose text has a box for the name, written in square brackets: Happy birthday [Name]. Customers then pick the design, type their name, and see it on the product before they add it to the cart. The order carries a print-ready file with that name in it.
All three words get used for this kind of product customization. It works as a product customizer built around your own designs: you design, the customer personalizes. You put the designs in the catalog, and the customer fills in their name and picks the product and its color. Nobody is handed a blank canvas to draw on, which is what keeps every order printable. Writing their own text or uploading their own artwork, which is what a product designer offers, is in Pro.
Yes, for shops that print, or that send the file to whoever prints for them. Every order carries a vector print file in the shape of that product's print area, ready to scale to whatever size you print. It does not connect to a print-on-demand fulfillment service on its own; the file is yours to send wherever you print.
Yes. The print file is an SVG with the text converted to vector outlines, so engraving, cutting and RIP software can open it without the font installed. Set the product's print color to the one your process expects, black for engraving for instance. If your printer or RIP prefers PDF, switch the print file to PDF, or to both, under Pomp -> Settings.
It has been tested from catalog to order and print file with Twenty Twenty-Five, Storefront, Astra, Kadence, GeneratePress, OceanWP, Blocksy, Neve, Hello Elementor, WoodMart and Betheme, and alongside Elementor, Yoast SEO, Rank Math, WP Rocket, LiteSpeed Cache, Wordfence, Polylang, TranslatePress, and WooCommerce's block cart and checkout.
Yes, six of them, each one real job in a real shop from start to finish: installing it and the first products, from the order to the print file, a T-shirt in six colors, a design built around a drawing in a font of your own, putting it anywhere with blocks and shortcodes, and a hundred designs from one CSV file. They are in the WooCommerce tutorials playlist on YouTube.
Yes. Every string in the interface can be translated, and a .pot file ships in the languages folder.
No. Everything runs on your own server. Designs live in your database, generated files in your uploads folder.
An SVG, a PDF, or both, as you choose under Pomp -> Settings or on the product itself. Either one is vector, in the shape of the product's print area, so it scales to any print size without loss, and both carry the same paths in the same colors. The PDF is made from the SVG the first time someone downloads it. The production email links to the files, and they are also on the order in the admin.
No. Products you include in the configurator cannot be added to the cart directly - otherwise you would receive orders with nothing to print.
Yes. Color and size are read from the variation, and you can give each color its own mockup image. Size does not change the print, so all sizes of one color share an image.
Not with this plugin, which offers the designs you put in the catalog. Both are in Pro, which is the full version of this plugin sold separately - not an unlock, and none of its code is in here.
Yes. Under Pomp -> Settings, "Placeholder backgrounds" lets you add your own images alongside the bundled set, and set the text color for any of them - built in or your own - instead of the default (its own color, darkened).
Yes, on its own. A product in the configurator never shows its normal WooCommerce page, so anything a plugin adds there would otherwise go unseen - this plugin reads it back out from the same two places WooCommerce's own product page does (the product tabs, and the area around the Add to cart button), so a size guide (or similar) plugin needs no changes on its side.
Yes, and you can pick how far you want to go. Place the [pomp_personalizer] shortcode in a page you have built yourself and the configurator fits into your own layout. Or pick the Pomp: configurator page template and restyle it with CSS - the body carries an pomp-template--configurator class to target. Or, for full control of the markup, copy templates/pomp-configurator.php out of the plugin into yourtheme/pomp-personalizer/pomp-configurator.php and edit it there: a copy in the theme is always used ahead of the plugin's own, and it survives plugin updates. The same goes for pomp-catalog.php.
In the block editor, both come as blocks, Design catalogue and Personalisation configurator, with the same options in the block's sidebar. The shortcodes draw the same thing, for the classic editor and page builders.
[pomp_personalizer] takes product_id and design, to open on a particular product or a particular design.
[pomp_catalog] takes chrome, search, categories, products, count, pagination and per_page. chrome="no" turns off everything around the grid at once, and any of the others can still be named to override that - so [pomp_catalog chrome="no" per_page="8"] is eight designs and nothing else, ready to drop into a page you have laid out yourself.
No. Nothing is rendered until a customer asks for it, and on the demo shop's hosting a preview takes about 26 ms beyond the request itself, without touching an image library. See "What it costs to run" above for the measurements.
Turn off combine JavaScript (Autoptimize calls it "aggregate", LiteSpeed and WP Rocket call it "combine") and clear the cache. Combining puts every script on the page into one file, so if any single one of them comes out of the minifier broken, nothing on the page runs at all - and the broken one is usually not this plugin's. WooCommerce's block cart and block checkout draw themselves with JavaScript, so there it shows as a page with nothing on it.
Minifying, deferring and page caching are all fine. This plugin marks the configurator and the design pages as not to be cached - DONOTCACHEPAGE, backed by real no-cache headers - so caches leave those alone and keep serving the rest of the shop from cache.
One more thing worth checking: some optimizers hand scripts and stylesheets out of their cache folder as .php files, and some hosts refuse to serve .php from inside wp-content/cache (a 403 or a 410 in the browser console, with "refused to execute script" beside it). Then nothing on the page loads, this plugin included. Switching that optimizer to write plain .js and .css files fixes it.
About 27 kB per configuration, for the preview and the print file together. Configurations that were never ordered are cleared after seven days; anything attached to an order is kept.