| 开发者 |
converswp
parvezvai shamsbd71 |
|---|---|
| 更新时间 | 2026年8月8日 02:41 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[trust_badges id="1"] and a bare [trust_badges] behave exactly as before; [trust_badges id="footer"] and other named groups now work as well, where previously they rendered nothing.[trust_badges id="footer"]trust-badges directory to the /wp-content/plugins/ directory.A trust badge is a small icon shown near a purchase decision that signals the transaction is safe — a payment logo such as Visa or PayPal, an SSL or secure-checkout seal, or a guarantee like "30 day money back". They are most commonly placed under an add-to-cart button, on the cart page, or in the site footer.
Yes. Trust Badges is free and open source under GPLv2 or later. Every feature described on this page is included; there is no paid tier or upsell required to use them.
No. WooCommerce and Easy Digital Downloads get automatic badge placement, but on any other WordPress site you can put badges anywhere with the [trust_badges] shortcode.
On WooCommerce product pages (under the add-to-cart form), on the WooCommerce cart page (both the classic cart and the Cart block), and on Easy Digital Downloads download pages (after the purchase link). The footer group displays on every page. Anywhere else, use the shortcode.
Use the shortcode in a block or template on the checkout page, for example [trust_badges id="checkout"] after creating a group with that ID. Automatic checkout placement was removed in 1.1.0 because it conflicted with block-based checkouts.
459 badges are bundled, all as SVG files. They cover payment methods, banks and wallets, security and SSL seals, shipping and delivery, and money-back and satisfaction guarantees.
It should not. Badges are SVG files rendered server-side, there is no front-end JavaScript, and badge lookups are cached. Version 1.2.0 specifically removed the largest cost: the badge manifest is now parsed once per request rather than once per badge.
Yes. The "mono" and "mono-card" styles recolour any badge to a single colour of your choosing using a CSS mask, so payment logos can be made to match your palette. Size, spacing, alignment, border radius and hover effects are all configurable too.
Yes, you can add your own images alongside the bundled library and style them the same way.
There is no technical limit. Three to five is a common choice — enough to reassure without crowding the buy button.
Settings → Trust Badges in your WordPress dashboard.
Yes. The Cart block is supported through a dedicated hook. Note that versions before 1.2.0 contained a bug that disabled the WooCommerce Cart and Checkout blocks site-wide; upgrading to 1.2.0 fixes it.
No. The plugin makes no external requests and stores only your badge configuration in your own database.
Yes, all interface strings use the trust-badges text domain.
/badges REST endpoint, which exposed every badge group's stored configuration to anonymous visitors.X-Forwarded-For header, allowing the options table to be flooded.REMOTE_ADDR; sites behind a reverse proxy can opt in via the new trust_badges_client_ip filter.is_default flag from the database rather than trusting a cached value.assets/badges.json is 50% smaller and no longer embeds absolute URLs.wp-admin/includes/plugin.php is no longer loaded on every front-end request.woocommerce_should_load_cart_block / woocommerce_should_load_checkout_block override that disabled the WooCommerce Cart and Checkout blocks site-wide.[trust_badges id="1"] and a bare [trust_badges] are unchanged; [trust_badges id="footer"], "cart" and "product_page" now work too, where previously they rendered nothing.wpdb::prepare() call with no placeholders that triggered a _doing_it_wrong() notice on WordPress 6.2+.dbDelta() can now upgrade the schema on existing installs.