Fitri Sinta

Hi @namespending,

Thanks for the follow-up!

Pre-seeding a set of default wishlists for all users automatically is something we’re planning to include in the Pro version of SaveTo Wishlist.

Since discussing Pro features falls outside what we can cover in the free plugin’s support forum, feel free to reach out to us directly at support[at]savetowishlist.com for more information.

Thanks again for your interest!

Hi @stefan1904,

Thank you for your feedback and for considering our plugin for your B2B store.

At the moment, our plugin does not have a direct integration with the Tiered Pricing Table for WooCommerce plugin. As a result, tiered pricing rules, as well as minimum/maximum/step quantity settings from that plugin, are not currently reflected, and the standard product prices are displayed instead.

We’ve forwarded your integration request to our development team for review and consideration in a future update.

Thank you again for your feedback and suggestion. We appreciate your support and will keep this integration request in mind as we continue improving the plugin.

Best regards,

Hi @stefan1904,

Thank you so much for your kind words! We are thrilled to hear that you are enjoying our feature-rich plugin and that you appreciate the value it brings compared to other paid alternatives.

Regarding your first suggestion about adding visible “+/-” quantity buttons to create a more modern and user-friendly experience, we think that is a fantastic idea. We will gladly raise this feature request with our development team for future updates.

For your second point regarding products with no price showing up with a $0 price/subtotal and an active “Add to Cart” button in the wishlist, we would love to look into this further to see how we can better support your setup.

To help us investigate, could you please clarify how these specific products are set up on your store?

1. Are you currently using a third-party catalog/quote plugin, or a custom code snippet to remove the prices and handle the “price on request” behavior?
2. If so, would you mind sharing the name of the plugin or copying the exact code snippet here with us?

This will help us understand the implementation details so we can work towards a solution.

Looking forward to your reply!

Best regards,

• This reply was modified 1 month, 1 week ago by Fitri Sinta.

Hi @mkovcu,

Since we haven’t heard back from you for a while, we’ll go ahead and close this thread for now.

If you’re still experiencing the issue, please feel free to reopen the thread and provide the requested details, including your plugin/theme versions and exact steps to replicate the behavior, and we’ll be happy to continue investigating.

Thanks!

Hi @jethrohazelhurst,

That’s great news! I’m glad to hear you were able to get that sorted out so quickly.

It makes perfect sense, if the plugin was reinstalled it likely generated a new page and leaving the system pointed toward the older (now invalid) URL. Selecting the active page with the [saveto_wishlist] shortcode in the plugin settings is exactly the right fix.

Since you’re all set, I’ll go ahead and close this ticket. If you run into anything else or have further questions while setting things up, please don’t hesitate to reach out again.

Cheers,

Hi @peterbohus,

Thank you for reaching out with such a detailed and well-structured report. We greatly appreciate the time you took to troubleshoot and share these findings with us.

Here is an update on both of the issues you reported:

1. Trashed products appearing as available

I have successfully replicated this issue on my end. You are absolutely right; a trashed product should not appear as available or allow the “Add to Cart” action to proceed. I have escalated this to our development team so they can adjust the plugin to treat trashed products as unavailable appropriately.

2. Fatal error when a product is permanently deleted

I attempted to replicate the fatal error Call to a member function is_type() on bool by permanently deleting a product from the trash that was previously saved to a wishlist. However, the wishlist loaded safely on my end without triggering the error. The system automatically removed the product from the wishlist.

To help me reproduce this so I can log it for the developers, could you please provide a bit more context?

• Steps to Reproduce: Could you share the exact steps you took to permanently delete the product? (e.g., deleted manually from the Trash, deleted via a custom script/plugin, or bulk deleted?)

• Error Location: Where exactly is the fatal error appearing? Is it on the main frontend wishlist page, a specific shortcode, or in the WordPress admin dashboard?

• Error Log Stack Trace: If you have access to your PHP debug.log or server error logs, could you share the full stack trace for this fatal error? This will tell us the exact file and line number where is_type() is failing.

Once I have those details, I will try to replicate it again and escalate it defensively to the developers as you suggested.

Looking forward to your reply!

Cheers,

Hi @jpsdi,

Thanks for contacting us and I’m sorry to hear about that.

We’ve tried to replicate this issue on our end, but we weren’t able to reproduce it, the refund to store credit works correctly in our tests, as expected.

To help narrow this down, we recommend checking for a possible plugin conflict:

1. Please temporarily disable all other plugins except WooCommerce and our Advanced Coupons plugin.
2. Test the refund to store credit again.
3. If the issue is resolved, re-enable your plugins one by one, testing each time, until the issue returns. This should help identify the conflicting plugin.

If the issue still occurs even with all other plugins disabled, or once you identify the culprit, please contact us via email at support[at]advancedcouponsplugin.com, so we can assist you directly.

We’ll be happy to take a closer look and help you get this resolved.

Cheers,