Expansion Installation Issue

[Casey Kolb]

@DanH Yes, we figured out that you need to install the samples to the default Expansions folder within the AppData folder to ensure your plugin has the right permissions for unpacking the samples. Basically, your plugin won't be able to write to a lot of directories on the OS because the folders may be read-only for the plugin. I'd recommend not even giving the user a choice for where to install the samples, and if they need to move the samples, they can always move them to their samples folder manually.

[DanH]

@Casey-Kolb great, thanks for letting me know! Did you run the install within the plugin or with a .pkg?

And no problems on Windows then?

[Casey Kolb]

@DanH It's currently installed within the plugin, but honestly a .pkg makes a lot more sense. We do have license keys for expansions though, so it's a bit tricky. It would certainly be faster with a .pkg file

[d.healey]

Might be relevant to this thread...

I've just added a File.hasWriteAccess() script wrapper function so you can verify if a directory selected by the user is writable and prompt them for another location if it isn't.