2014-06-15, 09:30
UPDATE: Bugs have been squished.
The advancedsettings.xml files were not being correctly generated in profile b, c, d and e in relation to the music database were being directed to profile a. This has now been fixed.
It appears it was as simple as adding "special://masterprofile/" to every profile directory in profiles.xml
I believe this was because the slave profiles were relying on the master profile for their directory location. So an absolute location should fix this.
From:
To:
This how now been fixed in the new script.
I suggest that you run the xbmc-client-setup script again to generate new files then just copy all of your XBMC_Backup files back except profiles.xml and all 5 advancedsettings.xml files as they were the only files affected.
There should now be no bugs. But if you do find some please report them.
The advancedsettings.xml files were not being correctly generated in profile b, c, d and e in relation to the music database were being directed to profile a. This has now been fixed.
It appears it was as simple as adding "special://masterprofile/" to every profile directory in profiles.xml
I believe this was because the slave profiles were relying on the master profile for their directory location. So an absolute location should fix this.
From:
Code:
special://masterprofile/
profiles/b/
profiles/c/
profiles/d/
profiles/e/
To:
Code:
special://masterprofile/
special://masterprofile/profiles/b/
special://masterprofile/profiles/c/
special://masterprofile/profiles/d/
special://masterprofile/profiles/e/
This how now been fixed in the new script.
I suggest that you run the xbmc-client-setup script again to generate new files then just copy all of your XBMC_Backup files back except profiles.xml and all 5 advancedsettings.xml files as they were the only files affected.
There should now be no bugs. But if you do find some please report them.