After the test you should set the type attribute back to the default of builtin.
I want to see if using the external layout makes a difference because that's what I've been using. Although the built-in one also worked for me. Make sure you completely remove the relevant files from the database (i.e. removed from PC Directory container as well), restart MediaTomb and then import them again.
If the result is the same, could you add the following to /usr/share/mediatomb/js/import.js (location might differ on your system) just after line 154 in the addVideo function. Make a backup first so you can restore it later.
print("location: '" + obj.location + "'");
print("rootpath: '" + object_root_path + "'");
print("dir: '" + dir + "'");
You will again need to remove the relevant files from the database, restart and then import. This time check MediaTomb log file (usually /var/log/mediatomb.log) for the location, rootpath and dir values. Post these values for one of the files that had it's parent directory moved out of nested order.
The most important value is rootpath. In your case it should be /var/hda/files/movies/TV. If it's empty then that's why some directories are not where they should be. MediaTomb defines the rootpath value and although it's used extensively it's considered experimental and is undocumented. This could explain why it might be empty for some files.
If you don't get this issue with the external layout then it's an error somewhere with the internal layout which means the MediaTomb devs would need to track this down. In the meantime you can continue to use symbolic links as a workaround.
< Previous |
Add a Reply
This forum does not allow anonymous participation.
Log in to add a reply. Not registered? Create an account to participate and receive email updates when replies are posted to this topic.