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
Moving a model from one library to another fails if libraries are on different devices #1937
Comments
Thanks for reporting! I'll check this out immediately. |
Interesting, it works here in dev. I note that you're running v0.57.1? I released .2 yesterday with a few bug fixes; I don't think any of them are related to this, but could you update and give it a go? In the meantime, I'll carry on trying to replicate. There may be relevant info in the logs tab of the Advanced Admin area, too. |
Same deal when I try with .2 version. This is what I found in the logs:
My volumes are linked like this with Docker: volumes:
- /mnt/nas_data/3d-print/manyfold/inbox:/libraries/inbox
- /mnt/nas_data/3d-print/manyfold/printed:/libraries/printed |
Whoa, So, to solve it straight away, you could change your docker mapping so that both libraries are in the same volume - as they're both in the same place on your NAS you don't actually need to map them separately. You shouldn't need to make any changes inside Manyfold either as the paths will stay exactly the same.
Then in the longer term, I should change to move rather than rename, because having the different libraries on different devices is totally a valid thing to do! |
Thanks this indeed worked by only mapping the volume once! |
Gonna reopen this to remind me to make it handle the situation properly; glad you got it working! |
Describe the bug
A model added in one library that you edit and try to move into another existing library displays an application error
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The model moves succesfully between libraries in UI, database and folder structure
Screenshots
Screen.Recording.2024-03-06.at.13.03.35.mov
Desktop (please complete the following information):
Additional context
The logs (
docker compose logs -f
) do not show any relevant info:The text was updated successfully, but these errors were encountered: