Tandhruil 1 Posted October 2, 2020 Share Posted October 2, 2020 Hi, When I installed the 4.5.0.50 release it removed all the others users rights in the [emby] folder, I had to add them back manually. But when I upgraded to th 4.5.1.0 version it removed them a second time. Personnaly I created a dedicated user to map emby directory in my windows workstation. First I thought it was because of the massive changes from 4.4.3.0 release to the 4.5.x. For the next release could you let the rights to the other users declared in the emby directory ? Link to post Share on other sites
Luke 26171 Posted October 2, 2020 Share Posted October 2, 2020 Hi there, what other users do you mean? Link to post Share on other sites
Tandhruil 1 Posted October 2, 2020 Author Share Posted October 2, 2020 (edited) 9 minutes ago, Luke said: Hi there, what other users do you mean? Users who's got rights read and write. Sorry, I think I wasn't clear. Installation didn't remove users from DSM but removed other users rights for emby directory Edited October 2, 2020 by Tandhruil Link to post Share on other sites
Luke 26171 Posted October 3, 2020 Share Posted October 3, 2020 Ok I've sent this to our package developer to review. Thanks. Link to post Share on other sites
alucryd 83 Posted October 5, 2020 Share Posted October 5, 2020 (edited) We were planning to do this down the line indeed. Right now we seem to have a lot of unidentified permission issues on some setups so they're reset on each install/upgrade, but once we figure this out they will be set on installation but left as is on upgrade. Apologies for the inconvenience. Edited October 5, 2020 by alucryd 1 Link to post Share on other sites
Tandhruil 1 Posted October 5, 2020 Author Share Posted October 5, 2020 @alucryd To be honest, it was not a big problem, I just spent 10 minutes searching why I couldn't map the Emby directory, it's only a feedback for the next versions. Link to post Share on other sites
Solution Luke 26171 Posted January 13 Solution Share Posted January 13 @Tandhruil this is resolved in our DSM 7 package that we're currently testing. Thanks. 2 Link to post Share on other sites
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now