-
-
Notifications
You must be signed in to change notification settings - Fork 550
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
Problem with some imports from chefkoch.de #1787
Comments
oh i am sorry, i did not run the imports trough competently because in my rush to get this release trough i did not read your issue correctly. I will review this hopefully tomorrow :) |
don't worry about it and take your time. the world won't end when I can't import every recipe for some days ;) |
I also thought that I resolved this with my PR but today I tested it and discovered that this is a separate issue. That's why I removed the "fixes" line in my pr |
Yea this must be something purely tandoor internal and likely just a small thing, if the preview works All the main psrsing is already done |
i just noticed that the ingredient list is also shown to me under step 1. is this related or is this another problem? |
this does not sound like an issue, ingredients are added to step one by default. |
super. thanks for the explanation |
ok fixed it, the issue was related to ingredients with leading spaces before commas, added a test to catch this case |
Tandoor Version
1.2.4
Setup
Docker / Docker-Compose
Reverse Proxy
No reverse proxy
Other
No response
Bug description
Some recipes cannot be imported from chefkoch.de.
The preview looks correct (as if you can import it), but when you click on Import & Restart you get the error message "Failure There was an error creating a resource!".
Examples of a working recipe:
https://www.chefkoch.de/rezepte/286071107217209/Tamagoyaki-japanisches-Omelett.html
Example of a recipe where the error occurs:
https://www.chefkoch.de/rezepte/2537801397537249/Japanische-Nudeln-mit-Pilzen.html
When I look at the request, it looks like a part of the payload is empty.
Relevant logs
No response
The text was updated successfully, but these errors were encountered: