• Hello, the link-sharing mechanism is poorly implemented: recipients can constantly track the sender’s actions.
    Take a look at how the link-sharing function is implemented in the WishSuite plugin: the recipient cannot track changes to the sender’s wishlist.
    I lowered the rating to draw attention to a flaw in the link-sharing feature.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thank you so much for your kind words and for rating our plugin,we truly appreciate it! We’re glad to hear that you find MoreConvert Wishlist powerful and useful.

    Regarding the wishlist sharing feature, we’d like to clarify how it currently works and why it was designed this way.

    The current sharing mechanism is built for sharing a live wishlist. Each wishlist has a unique share code, and anyone with that link can see the current contents of that list. This is intentional, because in many use cases such as gift lists, shared shopping lists, or collaborative lists recipients are expected to always see the latest version.

    If you need to share a list that should remain unchanged, one possible workaround is to use the multi-list feature: create a separate wishlist, add the products you want to share, share that list, and then avoid making further changes to it. This is available in the premium version.

    About the alternative approach of generating a share link that only contains product IDs in the URL without storing extra data: technically, this could create a static product list without additional database storage. However, it would not preserve custom fields, selected options, variable product states, or other metadata. So it would only be accurate for simple products or products where a specific variation has been selected. In more complex cases, we could not guarantee that the shared link would exactly match the user’s original wishlist.

    Before deciding whether this behavior should be changed, we’d also like to better understand the real situation behind your request.

    Could you please describe the last specific time this became a problem for you? What were you trying to achieve by sharing the wishlist? Who was the recipient? What changed in the wishlist afterward, and what issue did that create for you or for the recipient?

    Understanding the actual workflow will help us determine whether this is mainly about privacy, keeping a fixed record of a previous version, sharing a shopping plan, sending a quote/order list, or another use case.

    We’ll definitely consider your feedback while planning future updates. Thanks again for taking the time to share your thoughts with us!

    Thread Starter IgorSTB

    (@igorstb)

    For example: I shared a list of my favorite products with a friend but later deleted it. My friend sees an empty list.
    The recipient sees a dynamic list—essentially one that tracks the sender’s actions.
    The recipient can forward the link to anyone or even post it on a forum.
    Anyone with the link can track your activity.
    It turns out this isn’t a link for sharing specific items; it provides dynamic access to your wishlist page.
    As the sender, you have no control over this. (😠😞😒) 
    ⚠️This creates privacy issues.

    Thank you for clarifying your concern.

    The shared link does not track the sender’s general activity. It only displays the current contents of the specific wishlist associated with that link. Because the feature is designed as live wishlist sharing, changes made to that wishlist (such as adding or removing products) are reflected on the shared page.

    We understand that a separate “static snapshot” option could be useful for users who want to share a fixed copy that will not change afterward. However, this would be a different sharing mode and would require additional functionality, such as storing snapshots, managing shared versions, or providing link revocation controls.

    At this time, the free version provides live wishlist sharing as described. More advanced sharing controls or static sharing may be considered for a future feature, but we cannot confirm an implementation or release date.

    We also appreciate your point that the live nature of the link should be communicated more clearly. We will consider improving the wording in the sharing interface so users understand that recipients will see future changes made to that wishlist.

    Thank you for taking the time to explain your use case.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this review.