Skip to main content
N
navnathk23503600
Known Participant
February 15, 2017
Question

Third party acrobat plugin is not loading in Acrobat DC

  • February 15, 2017
  • 5 replies
  • 32890 views

Hello,

I developed a plugin for PDF manipulation functions by adding a new menu item under Edit menu.

It is working fine in Acrobat Pro XI but it is not loading in Acrobat pro DC.

I am using:

1. Acrobat Pro DC(2015-Classic)

2. Operating System - Windows 7

NOTE: According to my observation, first time when I installed Acrobat DC, my plugin was working fine. But when my trial version completed, I reinstalled it now and it is not working now.

For the case, If I did something wrong in the code, to check this, I placed a BasicPlugin from Acrobat Plugin SDK. It is also not working for Acrobat Pro DC.

But both are working fine for Acrobat Pro XI.

Please help!

Thanks.

This topic has been closed for replies.

5 replies

F
Fabian34135298ty9p
Participant
December 8, 2023

Hello, did you find a solution to this? I tried everything mentionned in this discussion, including that the plugin build matches. Thanks!

B
Brandon31117459cfkf
Participating Frequently
December 8, 2023
Sadly no, I tried all suggested actions from Thom and others in this thread and I am still experiencing the issues. I have elevated this issue to adobe customer support in hopes of getting a definitive answer to what is going on here. I will update this again when I have an answer.
    Thom Parker
    Community Expert
    Thom ParkerCommunity Expert
    Community Expert
    December 8, 2023

    I'd suggest you contact the "FileOpen" customer service, since it is their plug-in.  

     

    Thom Parker - Software Developer at PDFScriptingUse the Acrobat JavaScript Reference early and often
    M
    Maulik23221902udep
    Participant
    May 27, 2022

    Hi, Finally were you able to install/import the plugin. I am getting the same issue not sure what is the reason? 

    Does it required license as well? 

    T
    Test Screen Name
    Legend
    May 27, 2022

    If you have the same issue in 2022, check also whether Acrobat is 64 bit or 32 bit, and whether the plugin build matches. This was not an issue in 2017. 

    T
    Test Screen Name
    Legend
    February 15, 2017

    Your "currently in certified mode" is what I'd expect. It says YES if no plug-ins loaded. I've made my recommendations for the next steps in troubleshooting. By a third party plug-in I meant a fully compiled one, because the chances are the problem is in building or deployment rather than code; building another plug-in from code seems to confirm that.

    T
    Test Screen Name
    Legend
    February 15, 2017

    Ok at this point I suggest testing the Acrobst installation. Get a commercial third party plugin (or free or demo) and see if it loads. If it loads you have a specific issue with your builds. At that point I would be using depends.exe.

    N
    navnathk23503600Author
    Known Participant
    February 15, 2017

    As I said, I tried your BasicPlugin in the Acrobat plugin SDK itself.

    It is working fine with XI but not with Acrobat Pro DC.

    And If it is working fine with Acrobat XI, How can it be the code issue?.

    And as per your product description plugin compatibility issue is only with Mac and not with Windows.

    Acrobat DC removes Acrobat XI and plug-ins compatibility issue

    Above link says:

    "Note: This issue is specific to Mac OS only, and does not occur on Windows. On Windows, the existing third-party plug-ins can continue to be installed to the Adobe\Acrobat DC\Acrobat\plug_ins subfolder of the installation location for the subscription license and Adobe\Acrobat 2015\Acrobat\plug_ins for the Classic (Perpetual) license."

    B
    Brandon31117459cfkf
    Participating Frequently
    December 5, 2023

    Hi Karl, so are you saying that adobe reader cannot use third party plug-ins, specifically FileOpen?

     

    I just recently had a large group of users migrate from a 2017 version to current release and they are telling me that it used to work on the 2017 reader version, but now they can no longer even access the third party plug in option in the help menu.

     

    I tested this myself on my own machine and I could indeed not use FileOpen when using reader current release, but only when using a paid standard DC or Pro DC license. Do these users now need to hold a license to use third party plug-ins?

     

    Thanks for your help.


    For reference, this is my plugin option menu. Even when "Use only certified plugins" is unchecked I still am unable to use FileOpen while it is installed. I am on version 23.006.20380 on acrobat reader. 

    Current as of 12/5/23

     

    N
    navnathk23503600Author
    Known Participant
    February 15, 2017

    For your more information, when I try to delete those plugin from the path C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\plug_ins keeping Acrobat open, then It says "The action can't be completed because the file is open in Adobe Acrobat DC"

    This logically means that plugin is loaded somewhere.

    BasicPlugin from Acrobat SDK also adds one menu to acrobat in Acrobat Pro XI. Both plugin does not show Anything in Acrobat Pro DC.

    I don't understand what went wrong. Please help!

    T
    Test Screen Name
    Legend
    February 15, 2017

    First thing to check: what are your preference settings for "verified plugins only" and "protected mode"?

    N
    navnathk23503600Author
    Known Participant
    February 15, 2017

    Where can I check that?

    I checked in Edit > Preferences > General, I don't see any such option there. Where can I get those options?

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