Skip to main content
D
defaultvzdu9ysiduh3
Participant
April 18, 2022
Answered

Problem with CEF/CEP Extension on another machine - buttons not responding, etc

  • April 18, 2022
  • 1 reply
  • 517 views

I have an Adobe Premiere CEF extension I've written that works fine on my machine (and has been packaged and signed) but when run on someone else's machine (same version of adobe premiere, both on windows), it loads but doesn't respond at all to any buttons, and the extension panel is virtually unreadable and appears to be basically black text on dark gray background.

 

Anyone have any idea what's wrong and what these symptoms might mean?

This topic has been closed for replies.
Correct answer defaultvzdu9ysiduh3

Hi Bruce,

Thanks for the quick reply.

To answer your questions, the extension was installed on the second machine using a signed vxp file.

I have solved the mystery, and it was my fault.

When testing the extensions on my local machine, I use hard links from the adobe extensions directory to my local development directory.

The unresponsiveness of the extensions in the 2nd machine was due to javascript error on the extension page (it would be wonderful if adobe premiere could give us a log of such errors instead of silent error).

The ultimate cause turned out to be that when installing the extensions using vxp extension package, adobe was creating directory names based on the extension manifest file, which is very sensible, but my extensions were looking for each other (I know this is a weird thing to do but they do this for shared code purposes) using different directory names.

I should have tested it myself on my development machine and I would have caught the problem -- totally my fault.

All working well now (if anyone is curious here are the extensions on github: https://github.com/dcmouser/jrPremiere )

 

Thanks,

-jesse

1 reply

Bruce Bullis
Bruce Bullis
Legend
April 18, 2022

How was the extension installed, onto the second machine? 


D
defaultvzdu9ysiduh3AuthorCorrect answer
Participant
April 19, 2022

Hi Bruce,

Thanks for the quick reply.

To answer your questions, the extension was installed on the second machine using a signed vxp file.

I have solved the mystery, and it was my fault.

When testing the extensions on my local machine, I use hard links from the adobe extensions directory to my local development directory.

The unresponsiveness of the extensions in the 2nd machine was due to javascript error on the extension page (it would be wonderful if adobe premiere could give us a log of such errors instead of silent error).

The ultimate cause turned out to be that when installing the extensions using vxp extension package, adobe was creating directory names based on the extension manifest file, which is very sensible, but my extensions were looking for each other (I know this is a weird thing to do but they do this for shared code purposes) using different directory names.

I should have tested it myself on my development machine and I would have caught the problem -- totally my fault.

All working well now (if anyone is curious here are the extensions on github: https://github.com/dcmouser/jrPremiere )

 

Thanks,

-jesse

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