2024-01-14, 01:10 PM
Ok, the problem was because the deleted items before were linked to collections.
Items that are no longer present in the file system for some reason are still present in the metadata for the collections. (*)
Instead of deleting the whole collection and manually re-creating it (what I guess would have worked, too) I edited the config/data/collections/YOUR COLLECTION [boxset]/collection.xml file and removed all <CollectionItem>-Tags that hold a path that does no longer exist.
After a library scan (and I threw in a database and cache cleanup, just to be safe) the error logs are gone and I still have the collections as they were.
* I guess there is a cleanup of the collection xml files missing in the script that removes items while not found on file system during a library scan
Items that are no longer present in the file system for some reason are still present in the metadata for the collections. (*)
Instead of deleting the whole collection and manually re-creating it (what I guess would have worked, too) I edited the config/data/collections/YOUR COLLECTION [boxset]/collection.xml file and removed all <CollectionItem>-Tags that hold a path that does no longer exist.
After a library scan (and I threw in a database and cache cleanup, just to be safe) the error logs are gone and I still have the collections as they were.
* I guess there is a cleanup of the collection xml files missing in the script that removes items while not found on file system during a library scan