Skip to content
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

Open
TheDuckCow opened this issue Aug 2, 2017 · 3 comments
Open

Error due to creating folders without permission #30

TheDuckCow opened this issue Aug 2, 2017 · 3 comments

Comments

@TheDuckCow
Copy link
Collaborator

TheDuckCow commented Aug 2, 2017

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)

@TheDuckCow
Copy link
Collaborator Author

Issue also referenced here, will be updating documentation / tutorial to address the issue.
ndee85/coa_tools#81

@ragtag
Copy link

ragtag commented Aug 17, 2020

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.

@TheDuckCow
Copy link
Collaborator Author

Thanks for the comment. As I would interpret it, I would say the addon updater indeed fails gracefully - if an error occurs, the already installed version of the addon is still useable. On TPN, if there is no internet activity, the updater will by design not work (unless you developed an extension to include a "local" engine which pulls updates from say a shared network folder or something).

no internet
Sample no internet message; the rest of the addon remains useable.

Based on what you describe, it sounds like no addon self-updaters would be able to work (by design) with TPN anyways, but if you are a studio admin and have some ideas, I would be open to hearing how we could better accommodate. It sounds like something you would rather manage centrally rather via within individual addons though. Let me know if you are seeing something different from the above!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants