Quote:
Originally Posted by chaley
Ahh, another take on the same path problem, and one I should have anticipated. 
For whatever reason you have books in your library that have "invalid" paths (paths with trailing periods in folder names). When CC moves books, it does not regenerate the path from the template but instead uses the existing path. Something in Android is stripping the trailing periods when the folders are created on the SD card, meaning that CC and Android now disagree about the path. Somehow CC is still able to open the book to copy it back to main memory, but it is not able to delete the book because of the folder name mismatch.
I see two ways to fix this: - Regenerate the path using the current template. Although this would guarantee a correct path, it could change the path in very significant ways. It also isn't clear what would happen if a user is depending on calibre templates.
- "Clean" the path and store the cleaned version back with the book. This has the advantage of minimal change, but is slightly more complicated internally.
Both have the consequence that if you move the books back to main memory then the resulting path will be different from the original. The trailing periods will be gone. I prefer choice 2. |
I have "invalid" paths because they were there before you made your changes. I have a lot of these, and I thought my azw3 books were this way too, but I didn't check before. The mobi ones that failed are back in internal storage with the periods - see screenshot with Silva, David B.
I think choice 2 is the better as well.
