-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error due to creating folders without permission #30
Comments
Issue also referenced here, will be updating documentation / tutorial to address the issue. |
In a studio setting it's not desirable that users update their software or plug-ins, as this would quickly cause issues with multiple users using different versions of software while working on the same project. This is why sysadmins at studios generally install software as read-only and don't give users admin/root access. So the workaround suggested won't really work in this situation. A better solution would be to have the addon-updater fail gracefully if it can't create folders, and allow the plug-in that's using it to load even if the updater can't run. Also note that many medium to large studios have to follow strict security requirements under TPN, which, in addition to not giving users local admin rights, includes that workstations should not have internet access. |
As referenced in this issue on CrowdMaster, it seems sometimes windows users run into an issue if they don't have the right permissions and if the updater path doesn't already exist.
Recommendation: Developers should always pre-include/pre-create the updater folder or perhaps look into a different method to create folders that doesn't do absolute paths.
johnroper100/CrowdMaster#57 (comment)
The text was updated successfully, but these errors were encountered: