Open File Plugin Adobe

0 views

Skip to first unread message

Edward

unread,

Aug 3, 2024, 5:44:30 PM8/3/24

to silkturpipel

When I try to open a pdf with fileopen drm on it, instead of opening the pdf it will open a browser page prompting me to install the fileopen plugin. I have installed and tried to open the pdf again with the same result. I have tried multiple fresh installs of acrobat reader and the plugin, tried using the fileopen plugin remover provided on the website, running as administrator and various compatibility settings. I have contacted tech support of the company that provided the pdfs and they have no idea.

I remember I had this issue a couple of years ago and it drove me crazy and unfortunately I can't remember how I solved it. Iirc is was a relatively simple fix too. Unfortunely this seems to be a fairly obscure plugin and there isn't a whole lot of information availible out there. Any advice would be greatly appreciated.

Thanks for replying, I will certainly try, however I am not holding out much hope as on thier support page it says they only offer support to thier direct customers. I am a customer of another organisation who use thier product, and when I contacted the orgnisation that provides the pdf they had no idea how to resolve the problem. I was on the phone with them for over an hour today and they couldn't figure it out. Was hoping someone here would have some idea as I don't want to wait weeks while I go through a lengthy process involving several different parties.

That was my idea. Contact the maker. However, here is one more thing to try. Go to Edit > Preferences and look under General. Find the option "Use only certified plug-ins". Make sure there is NO CHECK MARK next to this option - the option must be OFF in your Reader.

I keep getting this in every browser. The document you are trying to load requires Adobe Reader 8 or Higher. You may not have Adobe Reader installed on your viewing environment may not be properly configured to use adobe reader.

The form you are attempting to open is a dynamic XFA form. These forms can only be opened in an XFA aware reader, which basically means Adobe Acrobat. You must download it and open it with acrobat/reader in order to view it.

You can use the Acrobat core API to create application logic that opens a PDF in Acrobat or Adobe Reader. The method that opens a PDF file is AVDocOpenFromFile. Before you invoke this method, you must create an ASPathName object, which is a platform-independent path value that specifies the PDF file to open.

You can create an ASPathName object by using different techniques. This section describes how to create an ASPathName object by invoking the ASFileSysCreatePathName method to convert a platform specific path name to an ASPathName object. This method requires the following arguments:

An ASAtom object that specifies the data type of the third argument. You can specify Cstring, which is accepted by the default file system on all platforms. In Windows, the path can be absolute (C:folderfile.pdf ) or relative (...folderfile.pdf ). In Mac OS, it must be an absolute path separated by colons (VolumeName:Folder:file.pdf ). For information about additional supported values, see the ASFileSysCreatePathName method in the Acrobat and PDF Library API Reference.

A null- terminated character that specifies additional data that you can use. You can pass NULL. For more information, see the ASFileSysCreatePathName method in the Acrobat and PDF Library API Reference.

You can use the Acrobat core API to open a PDF in an external window. For example, from within Adobe Reader or Acrobat, you can let a user select a PDF file and then display the PDF in an external window. This lets a user view two separate PDFs at the same time.

You must programmatic-ally create the external window in which to display a PDF. To create a window, you invoke standard platform C functions and not the Acrobat core API. For example, if you are creating your plugin in Windows, you can use the Win32 API to create a window. In this situation, part of the process of creating a window is to register the window class and define the window procedure. After you perform these tasks, you can obtain a handle to the window by invoking the CreateWindow function. For information about this function, see the MSDN online help at

You must create an AVDocOpenParamsRec object in order to open and display a PDF in an external window. This object defines required parameters for opening a PDF within an external window. After you create an AVDocOpenParamsRec object, allocate its buffer size and set the following attributes:

useFrame: If true, the frame attribute specifies the size and location of the window in which the PDF is displayed. If false, the frame attribute is ignored and a default frame is used.

frame: An AVRect object specifying the size and location of the window in which the PDF is displayed. In the Windows operating system, the coordinates are MDI client coordinates. In Mac OS, the coordinates are global screen coordinates. This attribute is ignored if the useFrame attribute is false.

If you are using the Windows operating system and this attribute is true, the PDF is opened in a visible window. If this attribute is false, the PDF is opened in a minimized window. This attribute is ignored if the useVisible attribute is false.

serverCreationData: Platform-dependent server data to associate with the AVDoc server. If the serverType attribute is EXTERNAL, this attribute must be assigned the address of the ExternalDocServerCreationData object.

AVPageView: Displays only the page view of the document. User interface components such as display scrollbars, toolbars, bookmarks, and thumbnails panes are not displayed. Annotations, such as links, are active.

AVEmbeddedView: Embeds the PDF file in an external document such as an HTML file. The first page of the PDF is displayed; however, user-interface component such as scroll bars, toolbars, bookmarks, and the thumbnails pane are not displayed. Annotations, such as links, are not displayed or active.

You must create an ExternalDocServerCreationDataRec object in order to open a PDF in an external window. This object contains callback functions that implement a window handler. After you create an ExternalDocServerCreationDataRec object, allocate its buffer size and set the following attributes:

You can display an open dialog box that enables a user to select a PDF to open. In addition to describing how to create an open dialog box, this section also describes how to use a dialog box to create an ASPathName object and an ASFileSys object, which are both used to open a PDF.

The Acrobat core API has a typedef named AVOpenSaveDialogParamsRec that you use to display an open dialog box. The AVOpenSaveDialogParamsRec typedef contains the following attributes that you programmatic-ally set:

kAVOpenSaveAllowForeignFileSystems: Allows file systems other than the default to be used to open the files. You need to select this value to open Unicode-named files. This value is only applicable for an open dialog box.

Set attributes that belong to the AVOpenSaveDialogParamsRec object. In this example, the size, fileFilters, and numFileFilters attributes are set. Assign the fileFilters attribute with the address of the pointer that points to AVFileFilterRec.

The address of an ASFileSys object. This method will populate the ASFileSys object with the file system in which the file that the user selects is located. This argument can be NULL if kAVOpenSaveAllowForeignFileSystems is not set as the flags value.

The following code example opens a PDF in an external window. The application logic that is located within the OpenExternalWindow user-defined function creates the window and displays a PDF within the window. A structure named gDocInfo that stores information such as the file to open is also defined.

This code example contains a user-defined method named AVWndProc that acts as a window procedure and another user-defined function named InitializeWindowHandler that registers the windows class that is specified as an argument to CreateWindow.

Also shown in this code example is application logic that displays an open dialog box that enables a user to select a PDF file to open. This application logic is located within a user-defined function named OpenPDFFile. (See Displaying an open dialog box.)

The OpenExternalWindow function can be invoked from an Adobe Reader or Acrobat user interface component, such as a toolbar button or a menu command. Ensure that the InitializeWindowHandler method is invoked before the OpenExternalWindow method; otherwise, the window class is not registered and the PDF file is not displayed in the external window.

All PDFs contain PDF version information in the header, such as 1.7. Additionally, PDF files that conform to ISO 32000 can include PDF version extension information that indicates that the PDF may contain PDF extensions added by third-party developers.

Acrobat 8.1 and later add extensions to the PDF specification. These extensions are specified in the Adobe Supplement to ISO 32000. Each extension in that supplement is associated with a base version and an extension level. The Extensions dictionary located in the Catalog dictionary specifies PDF extensions added by Adobe or others.

When you add PDF extensions specified by Adobe or others, you must ensure that the Catalog dictionary contains an Extensions dictionary that describes the greatest extension level that can appear in the PDF. The Extensions dictionary can contain one dictionary for each company or other entity that adds PDF extensions.

To operate on the contents of a PDF, and not just manipulate its representation in Adobe Reader or Acrobat, you must use a PDDoc object. For example, to create an annotation for a PDF, you must create a PDDoc object. (See Creating Annotations.)

You can create a PDDoc object by using an AVDoc object. To get a PDDoc object that corresponds to an AVDoc object, invoke the AVDocGetPDDoc method. This method is referred to as a bridge method because it allows your plugin to access other layers from the AV layer. There are several bridge methods which connect the different API layers (AV, PD, and Cos).