NeoWish Wishlist

Changelog

1.0.8

• Improvement: A saved product is easy to tell apart. The button now reads “Saved” next to the filled heart, in your brand colour, instead of “Remove from wishlist”; a text-only button turns your brand colour too. The heart-only tooltip says “Saved” as well.
• Accessibility: Screen readers announce a saved button as “Saved, button, Remove from wishlist” – what is true, then what a click does – instead of saying the state twice.
• Developer: New neowish_button_labels filter to change the button’s three texts. Extension API 1.6.

1.0.7

• Improvement: The “Heart icon only” button style now shows its label (“Add to wishlist” or “Remove from wishlist”) as a tooltip when a shopper hovers over it or reaches it with the keyboard, so the heart is never a mystery. Screen readers announce it as before. The hearts on shop pages get the same tooltip.
• Improvement: Heart-only buttons have a larger tap area (at least 32 by 32 pixels), easier to hit on phones and above the 24-pixel accessibility minimum.
• New: The [neowish_button] shortcode takes a style attribute (icon, text or icon_text) to choose the look of one button without changing the setting.

1.0.6

• New: Protection against bots and scripts. Guests can save without an account, so anything that can send a request could create guest wishlists, and on some stores automated traffic creates thousands of them. NeoWish now refuses saves from search engine crawlers and command-line tools, and limits how fast one browser or one address can save, including how many new guest wishlists one address can start in an hour. Real shoppers never come near the limits, and logged-in customers are never limited.
• Privacy: The limits are counted without storing IP addresses. Each counter is keyed by a one-way scrambled value and disappears when its time window ends.
• Tweak: A shopper who does hit the limit sees “You are saving very quickly. Please wait a moment and try again.” instead of a general error.
• Developer: New neowish_write_limits and neowish_is_bot_request filters. Extension API 1.5.

1.0.5

• New: A Site Health check, “Wishlist state and caching”, under Tools > Site Health. Each shopper’s saved products load from a separate address that must never be cached, and some server caches, CDN rules and “cache the REST API” options cache it anyway, which can show one shopper another’s wishlist. The check asks your site for a wishlist twice and reports whether an answer came from a cache, whether something rewrote NeoWish’s no-cache instruction, and exactly which address to exclude. It runs in the background, so Site Health opens as fast as before.
• Tweak: The caching question in the FAQ now explains what to exclude, and why your pages can stay cached.
• Developer: New neowish_detected_page_caches filter, for naming a host-specific cache in the check’s advice. Extension API 1.4.

1.0.4

• Fix: Products added to the page after it loads now show the right wishlist state. Shop filters, “load more” buttons, infinite scroll, quick views and product sliders insert new products without reloading, and their hearts stayed empty even for products the shopper had saved. They now update on their own, with no extra request to your server.
• Developer: New 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.

1.0.3

• Fix: The wishlist button now appears on product pages built with a page builder such as Elementor Pro’s Theme Builder. With the button set to “After the price” it was missing on those pages, because they skip the part of the page WooCommerce normally provides; it now shows after the Add to Cart button there instead. Themes that already showed it are unchanged.
• Fix: Out-of-stock products on page-builder product pages get their wishlist button too. They have no Add to Cart button to sit beside, so the button appears before the product details, or at the end of the product.
• Fix: When WooCommerce’s own experimental Wishlists feature is also switched on, My Account no longer shows two identical “Wishlist” links. NeoWish keeps its own and hides WooCommerce’s menu link; nothing is deleted.
• Developer: New filters neowish_button_fallback_hooks and neowish_hide_core_wishlist_menu_item. Extension API 1.2.
• Tested with WordPress 7.1 and WooCommerce 11.1.

1.0.2

• The settings tabs can now be scrolled sideways on a phone or a narrow browser window, so the later tabs are reachable instead of running off the side of the screen.
• Opening a later tab on a small screen now scrolls that tab into view, so you can see which one you are on.
• Tighter spacing on the tabs and the settings below them on small screens, which leaves more room for the fields themselves.

1.0.1

• Faster wishlist page: all saved products now load in one batch instead of one query each, which matters most on long lists.
• Guest wishlists whose browser cookie expired long ago are now cleaned up automatically, one month after the cookie’s own lifetime has passed. Lists belonging to an account are never touched.
• The nightly analytics cleanup now works in small batches on an indexed column, so it stays light on busy stores.
• Removed a scheduler check that ran a database query on every single page view.
• The Most Wishlisted report cache now simply refreshes every hour instead of being cleared every time a product is saved.

1.0.0

• Add to Wishlist button on the product page and the shop page, with position and placement settings and a shortcode.
• Guest wishlists with no account needed, and an automatic merge into the account on registration or login.
• Saves the exact variation a shopper chooses.
• Wishlist page created on activation, with add to cart, optional remove after adding, and optional go straight to checkout.
• Sharing by copy link, WhatsApp, X and Facebook, with a privacy switch for each list.
• A confirmation message when a product is saved.
• Most Wishlisted report in the dashboard.
• Colour and corner rounding settings.
• Shows the reward points each saved product would earn when NeoGrow is active.
• REST API, keyboard and screen reader support, right-to-left ready, and HPOS compatible.