(2012-04-05 09:16)amet Wrote: we have said that centralizing the addon_data is not a good idea and that it might fail, and you still want to do it, you are on your own I am afraid ...
I don't understand. Who are "we"? I thought that XBMC supported centralizing addon_data, is that not correct?
And then I saw an error (a bug?) in your (extremely nice) addon. And the bug is probably very easy to fix because you already read and write settings.xml to the centralized directory so why cant you read/write the subtitles also. And that is not even the problem. It is the settings.xml that needs to be centralized, and for your addon it already is. Where the add-on puts the temp-files doesn't matter if the program just saves and then opens the zip from the same place(!)
This is from row 1154- in the OSX debug log.
If I am not mistaken the add-on saves the zip locally (row 1) and then in row 2 uses the substituted (centralized) directory when it tries to open the newly saved zip-file :
GetZipList - Processing zip://%2fUsers%2fMacMini%2fLibrary%2fApplication%20Support%2fXBMC%2fuserdata%2faddon%5fdata%2fscript%2exbmc%2esubtitles%2fsub%5ftmp%2fzipsubs%2ezip/
CFileSMB::Open - opened /Video/XBMC/Userdata/addon_data/script.xbmc.subtitles/sub_tmp/zipsubs.zip, fd=10000
CFileSMB::Close closing fd 10000
Probably that is an easy thing to fix, dont you think? It looks like one of the rows are hardcoded and the other row uses the substitution from advancedsettings.xml (or maybe I have misunderstood the debug log, it is not always easy to read new logs that you are not used to).
And I think more and more do want to use the substitution of addon_data because it helps so much when you dont need to set everything up on every client for every add-on.
I would be happy to help you to test these bugs