Can't create new libraries #74801

Closed
opened 2020-03-16 01:42:48 +01:00 by Daniel · 7 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.3 26.20.15003.5016

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: blender/blender@77d23b0bd7
Worked: (optional)

Addon Information
Name: Material Library (0, 6, 0)
Author: Mackraken

Short description of error
I can only create new libraries if I start blender as admin, but if I start as admin, that breaks other things. Could you add an option to specify where libraries are stored. I think this would be a good feature anyway, as I'd rather have my libraries stored where I keep all my other resources.

Moving the add-on manually to C:\Users\UserName\AppData\Roaming\Blender Foundation\Blender\2.82\scripts\addons fixed the issue. However it should obviously go there by default.

Exact steps for others to reproduce the error

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.3 26.20.15003.5016 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `blender/blender@77d23b0bd7` Worked: (optional) **Addon Information** Name: Material Library (0, 6, 0) Author: Mackraken **Short description of error** I can only create new libraries if I start blender as admin, but if I start as admin, that breaks other things. Could you add an option to specify where libraries are stored. I think this would be a good feature anyway, as I'd rather have my libraries stored where I keep all my other resources. Moving the add-on manually to C:\Users\UserName\AppData\Roaming\Blender Foundation\Blender\2.82\scripts\addons fixed the issue. However it should obviously go there by default. **Exact steps for others to reproduce the error**
Author

Added subscriber: @dt192

Added subscriber: @dt192

Added subscriber: @Harvester

Added subscriber: @Harvester

I was reviewing this bug ticket and noticed that:

  1. the library path above mentioned is now available to be set in the add-on's preferences; (DONE)
  2. the add-on is now placed inside the \scripts\addons folder by default; (DONE)

The only thing I still have to verify is the ability to create new libraries with a user account that hasn't administrative privileges. I will check it shortly. One important factor to consider is that I never "install" Blender with the Windows installer since I use only portable versions, which avoids some Windows related problems, like the User Access Control.

I was reviewing this bug ticket and noticed that: 1) the library path above mentioned is now available to be set in the add-on's preferences; (DONE) 2) the add-on is now placed inside the \scripts\addons folder by default; (DONE) The only thing I still have to verify is the ability to create new libraries with a user account that hasn't administrative privileges. I will check it shortly. One important factor to consider is that I never "install" Blender with the Windows installer since I use only portable versions, which avoids some Windows related problems, like the User Access Control.

When the add-on is activated in the Preferences, and if you haven't previously set a path in the add-on's preferences, a new folder will be created inside the Blender's root installation directory, named \matlib, and new libraries will be added there. That might be a reason for the user not being able to create a new library, because probably he has no rights to do it. The user should try to set a path for the materials folder outside of the Windows programs directory and check if he has rights to write inside it. The following is a screenshot from my portable 2.83LTS version where as soon as I activated the add-on the folder \matlib was created and new libraries are stored there.
matlib_no_path_set.jpg

When the add-on is activated in the Preferences, and if you haven't previously set a path in the add-on's preferences, a new folder will be created inside the Blender's root installation directory, named \matlib, and new libraries will be added there. That might be a reason for the user not being able to create a new library, because probably he has no rights to do it. The user should try to set a path for the materials folder outside of the Windows programs directory and check if he has rights to write inside it. The following is a screenshot from my portable 2.83LTS version where as soon as I activated the add-on the folder \matlib was created and new libraries are stored there. ![matlib_no_path_set.jpg](https://archive.blender.org/developer/F8630526/matlib_no_path_set.jpg)

Added subscriber: @rjg

Added subscriber: @rjg

This was fixed by ac8dd9a5fe

This was fixed by ac8dd9a5fe

Closed as duplicate of #73899

Closed as duplicate of #73899
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#74801
No description provided.