Skip to main content
raphaelmatto14
raphaelmatto14
Inspiring
January 20, 2016
Answered

Premiere not following extension symlinks to network drives

  • January 20, 2016
  • 1 reply
  • 1332 views

hey Adobe folk,

I'm developing an extension for Premiere that I like to locate on a shared network folder. If I place a symlink in the extensions folder that points to a path on my local disk, everything works great. So, for example, from this directory:

/Users/[user]/Library/Application Support/Adobe/CEP/extensions

I create this symlink:

my-extension -> /some/LOCAL/path/library/premiere/my-extension

... everything works great. But if I change that symlink to point to a network location:

my-extension -> /some/NETWORK/path/library/premiere/my-extension

Then the extension is not available in Premiere. Is there any reason you guys can think of that Premiere would prefer symlinks to local locations over symlinks to network locations?

Cheers,

Raphael

This topic has been closed for replies.
Correct answer Bruce Bullis

I can think of loads of security-related reasons to not following re-directs.

Extensions are to be installed by Add-Ons, or ExManCmd; both place files in the correct location.

1 reply

Bruce Bullis
Bruce BullisCorrect answer
Legend
January 21, 2016

I can think of loads of security-related reasons to not following re-directs.

Extensions are to be installed by Add-Ons, or ExManCmd; both place files in the correct location.

raphaelmatto14
raphaelmatto14Author
Inspiring
January 21, 2016

Thanks bbb_999. Yes, I worked with my client's IT guy & he believes are no network security issues on their end preventing the redirect -- & other code is being located and triggered across the symlink. I was hoping there was some setting local to Premiere like "Allow redirects to mounted disks" that I could turn on. I recall a setting somewhere in either PS or AE that had to be enabled to allow that dcc to write to disk.

I'll explore ExManCmd, thanks!

The use-case here, you can imagine, is the ability to push updates to an extension without users needing to install anything -- this is useful for active development where I'd like to reduce install-fatigue. My workaround in this case is to wrap Premiere in a launcher (it's wrapped for other reasons anyway), and on launch delete my extensions from /Users/[user]/Library/Application Support/Adobe/CEP/extensions and copy in fresh versions, if the date is newer. If you have suggestions for a better way to do this (like maybe adding my network extensions path to an optimistic by likely imaginary AdobeExtensions path env variable).

Thanks for all your help across these issues, bbb_999! I see more Premiere integration projects que'd up for me in the months to come & your guidance and suggestions have been incredibly valuable.

Cheers,

Raphael

Bruce Bullis
Bruce Bullis
Legend
January 21, 2016

[my client's IT guy] believes are no network security issues on their end preventing the redirect -- & other code is being located and triggered across the symlink.


You don't find many such trusting and optimistic people, in IT!


Updating extensions without user needing to install: Your panel can download stuff from anywhere it likes, and use that instead of what's installed...

I'm curious why you'd wrap PPro in a launcher, at all...? Manually deleting and replacing panels may work if all your users have set PPro to load debug panels, but any change to what's in your extension's directory will break the signature, and PPro won't load them.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices