Docs & troubleshooting
The fixes for the handful of things that trip stores up most — button placement, caching, Pro emails, importing, and privacy. Can't find it here? Get support.
Cache plugins and the button state
Wishmio is cache-neutral by design: the HTML is identical for every visitor, and each shopper's saved state hydrates from a single REST call after the page loads. Full-page caching stays fully effective — you don't need to exclude any pages.
The one known edge: a few cache plugins also cache /wp-json/ responses. That can serve a logged-in shopper a stale security token, so saves appear to do nothing. The fix is to exclude /wp-json/ from page caching — most cache plugins have this setting. Guests are unaffected either way.
Pages that contain no wishlist elements load zero Wishmio assets, so caching those pages costs nothing.
Pro back-in-stock emails aren't sending
Wishmio Pro sends through your site's own mail system — there's no external service and no per-email fee. That means email problems are almost always site-wide mail problems, not Wishmio problems. Work through these in order:
- Confirm your site can send mail at all. If order confirmations and password resets aren't arriving either, the issue is your server's mail, not Wishmio. Install an SMTP plugin such as WP Mail SMTP and configure a real sender — Wishmio's queue will use it automatically.
- Check the send queue. Wishmio throttles sending through Action Scheduler so a big restock can't melt your mail server. Go to WooCommerce → Status → Scheduled Actions and filter to the
wishmiogroup to see pending, completed, and failed sends. - Verify the product actually went out of stock and back in. Emails fire on the out-of-stock → in-stock transition. A product that was never out of stock has no one waiting on it.
The reverse lookup that powers this — "which shoppers saved product X" — is an indexed query, so a restock on a heavily-wishlisted product notifies everyone waiting without scanning your whole store.
Importing from YITH, TI, or core Shopper Lists
Go to WooCommerce → Wishmio Import. Wishmio detects WooCommerce core Shopper Lists, YITH Wishlist, and TI WooCommerce Wishlist, shows how many items each holds, and imports them in one click.
What carries over
- Account-owned lists only. Any wishlist tied to a registered customer imports cleanly.
- Guest lists can't be mapped. Other plugins store guest lists against their own cookie, which Wishmio has no way to match to a person — so those don't come across. New guest wishlists start fresh under Wishmio.
- Re-running is safe. The importer is idempotent: running it again never creates duplicates, so you can import, add more in the old plugin, and re-import without cleanup.
You can leave the old plugin active during the transition and deactivate it once you've imported.
Privacy, GDPR & data
Wishlist data never leaves your site — there's no external service in the loop.
- Export & erase. Wishlists and Pro stock-alert subscriptions join WordPress's built-in personal-data tools (Tools → Export Personal Data and Erase Personal Data), grouped under "Wishlists" and "Wishlist stock alerts."
- Guest retention. Idle guest lists auto-delete after 60 days. Change the window with the
wishmio_guest_retention_daysfilter:add_filter( 'wishmio_guest_retention_days', fn() => 90 ); - Cookie disclosure. The guest cookie is set only after a shopper first saves something — nothing is stored before that. Add a line to your privacy policy noting that guest wishlists are kept in a first-party cookie.
- Pro email opt-in. Guests who subscribe to stock alerts go through double opt-in, and every email carries an unsubscribe link.
Still stuck? Get support
Email support@wishmio.com — we answer Pro tickets within one business day. Once the plugin is live on WordPress.org, free-plugin questions also have a public support forum there (answered within two business days).
One thing that gets you a fast answer: paste the Wishmio section from Tools → Site Health → Info (it lists versions, row counts, cron status, theme type, and page status), plus your active caching and theme plugins. That usually pinpoints the issue on the first reply.