| 开发者 | mtpamir |
|---|---|
| 更新时间 | 2026年10月19日 14:18 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/neowish-wishlist.NeoWish lives under Marketing > NeoWish, next to the other WooCommerce marketing tools. If the WooCommerce Marketing menu is switched off on your site, you will find it under WooCommerce > NeoWish instead.
Newer WooCommerce versions include an experimental wishlist feature that is switched off by default, is available to logged-in customers only, keeps one fixed list, and renders through block templates. NeoWish works for guests from the first click, keeps the list through login, works in classic themes as well as block themes, remembers the exact variation, and adds sharing and the Most Wishlisted report. Both can be installed on the same site without conflict, because they store their data separately.
No. Anyone can save products right away. Their list is kept safely in their browser. When they register or log in, it moves into their account by itself, and nothing is repeated twice.
Yes. The button looks the same for every visitor, and each person's saved items are loaded after the page has loaded. So a cached page can never show the wrong hearts.
There is one thing that must never be cached: the address those saved items come from, /wp-json/neowish/v1/ (or ?rest_route=/neowish/v1/ without pretty permalinks). NeoWish already tells caches not to store it, and the usual caching plugins respect that. Some server caches, CDN "cache everything" rules and "cache the REST API" options do not. To check your store, open Tools > Site Health and look for Wishlist state and caching. It asks your site for a wishlist twice and tells you if an answer came from a cache, and where to look. If it reports a problem, add that address to your cache's exclusions. Keep your pages themselves cached.
Yes. When they save from a product page, NeoWish remembers the exact one they chose, and the wishlist shows it.
On the shop page, set Button Placement to Over the product image. That option does not depend on your theme. On the product page, try one of the other positions. If none of them fit, set the position to Hidden and place the [neowish_button] shortcode wherever you like. Add style="icon", style="text" or style="icon_text" to choose the look of that one button.
They are saved for one hour so your dashboard stays fast. New activity is recorded immediately and appears at the next refresh.
Only if the NeoGrow plugin is active. Each saved product then shows the points it would earn when bought.
Turning the plugin off keeps all your data, so you can switch it on again later. Deleting the plugin removes everything it created, including the wishlists. That cannot be undone.
neowish_item_quantity_changed action, NeoWish\API\Wishlist::set_item_quantity() and a neowish/v1/quantity REST route. Extension API 1.7.neowish_button_labels filter to change the button's three texts. Extension API 1.6.[neowish_button] shortcode takes a style attribute (icon, text or icon_text) to choose the look of one button without changing the setting.neowish_write_limits and neowish_is_bot_request filters. Extension API 1.5.neowish_detected_page_caches filter, for naming a host-specific cache in the check's advice. Extension API 1.4.neowish:refresh JavaScript event. Dispatch it on document to repaint every wishlist button, or pass { detail: { refetch: true } } to reload the shopper's wishlist from the server first. Extension API 1.3.neowish_button_fallback_hooks and neowish_hide_core_wishlist_menu_item. Extension API 1.2.