Find the cause, then fix it

Check that Free is active, catalog or product buttons are enabled, the chosen position exists in your theme, and the product is in an allowed category. Clear generated page caches after changing settings. Test with a standard WooCommerce product before adding custom options.

A temporary loading label means the save controls are not ready yet. Stalled requests end with an error and an explicit retry option. If the host temporarily limits requests with HTTP 429, wait for the retry countdown before trying again. Persistent HTTP 429 responses need your host to inspect its request limits. The plugin cannot remove a hosting limit.

From 0.5.9, confirmed wishlist-to-cart additions refresh supported WooCommerce Classic and Blocks cart displays. If a custom theme still shows an old count, check the actual cart, clear generated assets and test theme or optimization conflicts on staging. Wishlist cart writes are not automatically repeated. After an uncertain result, inspect the WooCommerce cart before starting another action. Wishlist-to-cart requires MySQL or MariaDB with working named locks; SQLite-based WordPress Playground does not support this cart locking. If loading still fails, check that plugin scripts load and test script-delay or optimization changes on staging.

To save a specific variation or add a variable product to the cart, select its required options first. Saving the parent product for later does not require selecting a variation. Check product publication, stock, purchase restrictions, and WooCommerce validation. The plugin preserves error details instead of silently substituting another selection. A changed item may require reopening its editor before saving.

Review sending controls in Automations, the shopper’s notification choices, and waiting or held messages in Message activity. Check Overview for scheduler warnings. Check that the product still qualifies and the shopper still has it saved. Daily rate limits and held unknown outcomes can intentionally delay or prevent sending. Use Message activity → Send a test email, or Customer email setup → Delivery checks & shopper consent → Send a test to my account, to check delivery to your own WordPress profile email. Configure an SMTP or email delivery plugin in that plugin’s settings. Transport acceptance is separate from confirming I received this test; neither a successful preview nor a saved workflow proves inbox delivery.

Resume a report to continue from the last completed paid-order page. Use a shorter date range if the activity cohort exceeds the report limit. For imports, review each result and prepare a new preview if source data changed or the preview expired. Check the destination account’s list allowance and available server resources; individual wishlists have no fixed product-count ceiling.

Include plugin, WordPress, WooCommerce, PHP, and theme versions; the exact steps; what you expected; and what happened instead. Exclude passwords, license keys, customer data, and private sharing links. Submit the Support form and keep the private receipt URL.

Keep your current plugin installed. Download the matching Pro package from your customer account, or contact support if you need help with access. Pro installers are not available on the public Downloads page. Check the WordPress, WooCommerce, PHP and Free requirements before updating, and never bypass a failed package verification.