Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Brecht

    (@brechtvds)

    Unfortunately the button cannot work if the recipe is not public and visible to everyone. When someone clicks on the button, eMeals tries to visit the page where the button got clicked on to retrieve the ingredients. Since they are not authenticated either, they cannot find a recipe on the page.

    Because of the way their technology works, we can’t really offer this feature for recipes that are locked away.

    A different integration with a shoppable button is actually about to release a different technology for retrieving the recipes and we are looking into that. It should allow for the button to work for those types of recipes as well.

    But I cannot give you a deadline for this yet.

    Thread Starter roblesdesigns

    (@roblesdesigns)

    Hi, @brechtvds ,

    That makes a lot of sense. Is there any kind of addition we could put on the button/call triggered with custom code to send that information? Or to always treat the URL of the API as an authenticated account?

    Also, do you know if this is true for the Instacart button, too? That has an optional account number with Instacart that we assumed would help make that connection.

    Plugin Author Brecht

    (@brechtvds)

    Right now all of those integrations only support passing along the URL, which won’t work in your situation.

    One of them is about to release an API that would allow us to pass along the ingredients directly and make the feature work for private recipes as well. We are already working on that on our end and will let you know when I can tell you more.

    Brecht

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Walmart Button Not Working’ is closed to new replies.