-
-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Transfer to Bring! not possible #4612
Comments
Could this be related to my issue #4619 ? |
My Mealie server is publicly accessible via Cloudflare, so I think it might be another issue. |
Not working on the demo makes sense, because of #4619 |
I was not referring to the server being publicly reachable, but the settings of your account and recipes. If you are not able to view the recipe after logging out of your account, the receiver of your recipe action ("bring!" in this case) will also not be able to. It will then instead try to parse the main page (or whatever page your instance views to users that are not logged in), which does not contain a recipe and thus fail. So, can you check what happens if you log out of your account on your own instance and visit the url you tested? |
Ah, ok... Now I understand. Now I have temporarily changed the permissions to public, but the result is the same. I have shared this recipe with everyone, can you access it? |
That's interesting. I can view your recipe, but for me the recipe import on Bring! fails, too. If i test the same with a public recipe of mine, it works. Bring! offers a Testpage for your integration, you can enter an URL and Bring! tests, if there is valid data to be imported: https://www.getbring.com/de/integration-prufen |
I have now published two more recipes, but the result is the same. |
First Check
What is the issue you are experiencing?
I can't transfer the ingredients of a recipe to Bring!
Steps to Reproduce
Please provide relevant logs
Mealie Version
Deployment
Docker (Linux)
Additional Deployment Details
No response
The text was updated successfully, but these errors were encountered: