Skip to content
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

Open
6 tasks done
schaeffd opened this issue Nov 25, 2024 · 5 comments
Open
6 tasks done

[BUG] - Transfer to Bring! not possible #4612

schaeffd opened this issue Nov 25, 2024 · 5 comments
Labels
bug Something isn't working triage

Comments

@schaeffd
Copy link

First Check

  • This is not a feature request.
  • I added a very descriptive title to this issue (title field is above this).
  • I used the GitHub search to find a similar issue and didn't find it.
  • I searched the Mealie documentation, with the integrated search.
  • I already read the docs and didn't find an answer.
  • This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

image
I can't transfer the ingredients of a recipe to Bring!

Steps to Reproduce

image

Please provide relevant logs

image

Mealie Version

image

Deployment

Docker (Linux)

Additional Deployment Details

No response

@schaeffd schaeffd added bug Something isn't working triage labels Nov 25, 2024
@ianp1
Copy link

ianp1 commented Nov 27, 2024

Could this be related to my issue #4619 ?

@michael-genson
Copy link
Collaborator

@schaeffd can you confirm if this is related to #4619? Is your recipe publicly accessible?

@schaeffd
Copy link
Author

My Mealie server is publicly accessible via Cloudflare, so I think it might be another issue.
But I also tried adding recipe actions in the demo instance, but there too it is not possible to add anything to Bring!.

@michael-genson
Copy link
Collaborator

Not working on the demo makes sense, because of #4619

@ianp1
Copy link

ianp1 commented Nov 28, 2024

My Mealie server is publicly accessible via Cloudflare, so I think it might be another issue.
But I also tried adding recipe actions in the demo instance, but there too it is not possible to add anything to Bring!.

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

3 participants