-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Can't import rescipes from rezeptsuite #2467
Comments
according to the docs the rezueptsuit export should be an xml file https://docs.tandoor.dev/features/import_export/#rezeptsuitede not sure if that has changed but try if that can be exported. If not i would need a sample of the cml file so i can build another importer for rezeptsuite |
Thank you for your reply. I have generated a new DB with some recipes. File attached. |
I've read in forum and the handbook, but i can't find something to export directly as XML. |
interesting, i will need to investigate this, might be that something changed there |
ok, thank you |
ok so looks like recipesuite zips there exports and renames their xml to .cml for whatever reason. I added to the docs that you need to unzip the export and rename .cml to .xml I also hardened the importer to better handle non available fields and got your import to work very well. |
Very thanks @vabene1111 so i wait for the next relelase (i use docker), right? |
Correct, shouldn't be too long, just waiting for some feedback on the latest beta (which you can test if you want) and will release it afterwards. |
Tandoor Version
1.4.9
Setup
Docker / Docker-Compose
Reverse Proxy
Nginx Proxy Manager (NPM)
Other
No response
Bug description
Hello all,
i have about 600 recipes on my local software from rezeptsuite.de. For import, i exported the DB as xml like rezeptSuite-15-05-2023.cml. But if i import the file, i get success on the importpage with 0 imported recipes. So i enabled debug and get this error message below.
Can anyone help to get importer running with rezeptsuite.de?
Very thanks
Best Regards :)
Relevant logs
The text was updated successfully, but these errors were encountered: