2018-05-21, 21:38
(2018-05-21, 16:51)meowmoo Wrote:You basically created a situation where the rename function will generate a python error because the variables filename and newfilename don't exist. That error is trapped, so when the rename fails the program does a two step process to rename. It copies the file to the new location then deletes the original. So that works for you (which is great), but I can't for the life of me figure out why the rename function (which is built into the Kodi python stuff) works on my NFS and not yours.(2018-05-11, 02:48)pkscout Wrote:HI, Im using NFS mounts in Kodi, other Addons and Kodi can read write just fine from the NAS.(2018-05-10, 15:15)meowmoo Wrote: Hi there,All I can say in looking at that is that there is something happening with the NFS access. Are you using NFS mounts defined in Kodi or NFS mounts in an FSTAB file with path substitution? If the latter, I've never tested with that, so I have no idea how using that particular hack might affect file system access from the Kodi virtual file system (which I use in AS).
for some reasons AS dont move the extrafanart to the NAS/Artist/extrafanart folder....they all stay in .kodi\userdata\addon_data\script.artistslideshow\temp Folder, the _imgdb.nfo is however found in the NAS/artist/extrafanart folder..
here is a Debug Log
pastebin.xyz/p?q=dUFDQ20
thanks for looking at it
BTW, I use NFS here with mounts defined in Kodi and haven't seen that particular problem.
However I looked at the last changes on your github site, and when I change line 102 in resources/common/fileops.py back toAS works just fine!Code:_rename( filename, newfilename )
try and error + luck ;P
since i still dont know anything about Python, maby you have a idea whats going on.
thanks