Safari pdf plugin requires $60+ fee. What's up?

I can't get my bank's pdf to show in entirety because I've got to buy a $60+ fee for a plugin. Is there a work around? I'm running Mountain Lion Safari in 32 bit. 64 bit doesn't work either.

It is beginning to appear that just about everything that is connected with Adobe (pdf viewer & flash) has been disabled on most macs. I believe this is done on purpose by Apple.
Similar to what's happening with anything connected with Google.
Apple continues to try to control the world.
I don't even have that plug-in listed in my Library, so there's nothing to remove. Using Google Chrome does work, thank goodness.
I do have to print as .pdf file many bank and financial statements for my non-profit. It is becoming more and more difficult.
Fortunately, I still have a Windows 7 computer with which to accomplish many of these tasks that Apple is blocking. Are you listening Apple? do you care?

Similar Messages

Frustration with Safari pdf plugins

I've tried both Shubert and Adobe Reader PDF plugins and find they are both terrible. What I find most annoying is that I can't seem to accurately control scolling. The slightist slide of my finger seems to send the document jumping, often pages at a time.
Any thoughts? At this point, I'm tempted just to uninstall the Reader plugin and just use PDF PenPro.
Thanks

Preview works fine for me.
I used to use PDF pen pro, and at one time I've tried all the PDF addon things, but I haven't bothered with them in a while. Preview does a good job of annotating pdfs these days.
I'm an apple fundamentalist. If there's some PDF function I can't do natively with Safari and Preview, I probably don't need it in the first place.

PDFs/plugin ceased working in Safari

Hi! Safari doesn't wanna display PDFs directly in the browser window any more. Some PDFs open, but use the Adobe Acrobat plugin rather than Schubertit's PDF plugin (which is set as the default and the Adobe plugin is actually disabled, at least that's what I see in the Acrobat preferences). Other PDFs don't open at all any more. Safari opens a new page when I click a link to a PDF and pretends it's opening it (progress bar and rotating little wheel), but the page stays just white when it's done. The PDF plugin used to work fine until recently. I'm not sure if a recent security update or the Safari update 2.0.1 broke it, but it started misbehaving at around the same time. Anybody else with a similar issue? Any fixes? Camino opens the same PDFs perfectly fine using PDF plugin.

William,
There is at least one other thread about this problem, which I also have as of 2.0.1, but I haven't done the latest security update or new iTunes 5 or java, etc., so I'm pretty sure it's a safari issue. Nothing that involves audio streaming (maybe video content also) works, including Flash. I've tried everything here short of re-installing Safari 2.0 (trying to figure out how to do that right now) or totally re-installing the OS, which I just did last month. I've stripped out all CMs, Prefs, Bundles, Startup Items and run all the normal maint routines, with no help.
Retrospect is also crashing now, out of the blue, so I can't even get to my older version of Safari on there. :/
I really hope someone figures this out. Here's what my crash reporter says:
Host Name: greyling
Date/Time: 2005-09-28 20:24:56.851 -0700
OS Version: 10.4.2 (Build 8C46)
Report Version: 3
Command: Safari
Path: /Applications/Safari.app/Contents/MacOS/Safari
Parent: WindowServer [75]
Version: 2.0.1 (412.5)
Build Version: 7
Project Name: WebBrowser
Source Version: 4120500
PID: 234
Thread: 0
Exception: EXCBADINSTRUCTION (0x0002)
Code[0]: 0x00000002
Code[1]: 0x913afdb4
Thread 0 Crashed:
0 com.apple.audio.CoreAudio      0x913afdb4 HP_Stream::IsPropertySettable(AudioObjectPropertyAddress const&) const + 320
1 com.apple.audio.CoreAudio      0x913afb20 IOA_Stream::IsPropertySettable(AudioObjectPropertyAddress const&) const + 112
2 com.apple.audio.CoreAudio      0x913afa94 HP_DeviceFormatList::IsPropertySettable(AudioObjectPropertyAddress const&) const + 312
3 com.apple.audio.CoreAudio      0x913a4690 HP_Object::IsPropertySettable(AudioObjectPropertyAddress const&) const + 104
4 com.apple.audio.CoreAudio      0x913a45bc HP_Device::IsPropertySettable(AudioObjectPropertyAddress const&) const + 692
5 com.apple.audio.CoreAudio      0x913a429c IOA_Device::IsPropertySettable(AudioObjectPropertyAddress const&) const + 120
6 com.apple.audio.CoreAudio      0x913a40c0 IOA_SingleDevice::IsPropertySettable(AudioObjectPropertyAddress const&) const + 196
7 com.apple.audio.CoreAudio      0x913aa62c HPPlugInObjectIsPropertySettable(AudioHardwarePlugInInterface**, unsigned long, AudioObjectPropertyAddress const*, unsigned char*) + 156
8 com.apple.audio.CoreAudio      0x913aa4a0 HALPlugIn::ObjectIsPropertySettable(HALObject const&, AudioObjectPropertyAddress const&) const + 72
9 com.apple.audio.CoreAudio      0x913a6968 HALObject::IsPropertySettable(AudioObjectPropertyAddress const&) const + 232
10 com.apple.audio.CoreAudio      0x913a97b0 AudioDeviceGetPropertyInfo + 340
11 ...dio.SoundManager.Components      0x0861bf78 HALHardwareDispatch + 1952
12 ...dio.SoundManager.Components      0x0861bdcc HALHardwareDispatch + 1524
13 ...dio.SoundManager.Components      0x0861bbdc HALHardwareDispatch + 1028
14 ...dio.SoundManager.Components      0x0861bac0 HALHardwareDispatch + 744
15 ...dio.SoundManager.Components      0x0861b8b4 HALHardwareDispatch + 220
16 ...ple.CoreServices.CarbonCore      0x90b51ff0 CallComponent + 260
17 ...ple.CoreServices.CarbonCore      0x90b51ec8 CallComponentOpen + 40
18 ...ple.CoreServices.CarbonCore      0x90b51144 OpenAComponent + 520
19 ...ple.CoreServices.CarbonCore      0x90b5cd50 OpenComponent + 20
20 com.apple.audio.SoundManager      0x930e50c4 InitHALComponents + 104
21 com.apple.audio.SoundManager      0x930dd2ac SndNewChannel + 48
22 ...romedia.Flash Player.plugin      0x0701a5e4 Flash_EnforceLocalSecurity + 73644
23 ...romedia.Flash Player.plugin      0x070a15a4 Flash_EnforceLocalSecurity + 626540
24 ...romedia.Flash Player.plugin      0x070a25b4 Flash_EnforceLocalSecurity + 630652
25 ...romedia.Flash Player.plugin      0x070bc290 Flash_EnforceLocalSecurity + 736344
26 ...romedia.Flash Player.plugin      0x070bc6c0 Flash_EnforceLocalSecurity + 737416
27 ...romedia.Flash Player.plugin      0x070bc7a8 Flash_EnforceLocalSecurity + 737648
28 ...ro

Why does the Safari PDF viewer plugin show up in mission control?

Whenever I swipe to activate mission control the PDF viewer plugin of Safari shows. This obviously doesn't happen if I do not have a tab with a PDF active in the browser, but why does it show anyway? I have tested Firefox and Chrome and their PDF plugins do not show in the mission control view, so why does Safari's? How can I get rid of this? It makes loading expose' view a little choppy (compared to when I dont have to use a PDF in Safari) and looks weird. I have attached an image of how this looks.

deleting the adobe plugins in Library worked for me:
http://forums.macworld.com/index.php?/topic/146648-hide-adobepdfviewernpapi-in-m ission-control-how/

Firefox PDF Plugin for Mac OS X shows as an unknown plugin, yet I got it through mozilla! What's its latest version?

Firefox Plugin check says:
Firefox PDF Plugin for Mac OS X
Displays PDF documents in the browser. Unknown plugin
yet I got it via Mozilla plugins.
So it's in the Firefox data base. What's the latest version?

Sorry for the delay in getting an answer, but there don't seem to be any advanced level Mac-users helping do support in this forum. <br />
1. Mozilla didn't supply that Firefox PDF Plugin for Mac OSX, it is probably part of your PDF reader program, or maybe it came with your Mac operating system.
2. Lack of Plugin version information is something Mozilla has been working on for that Plugin Check page. The problem with fixing it is that there is no standard among Plugin developers for making the version number of their Mozilla Plugin available for Mozilla to locate and display. If you look at your own '''''More system details...''''' in your original posting, you can see the problems Mozilla faces when trying to fix the Plugin Check service. Eight Plugins recognized by this forums software and only the last 2 in the listing reveal the plugin version number to a website - Silverlight and Flash.<br />
* Displays PDF documents in the browser.
* Gecko default plugin
* Runs Java applets using the latest installed versions of Java. For more information: Java Embedding Plugin. Run version test: Java Information.
* RealPlayer Plugin
* The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.
* The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
* 4.0.50917.0
* Shockwave Flash 10.1 r102

When will Firefox update the pdf plugin for version 4? This is a major technical oversight which required me to downgrade back to 3.

The PDF plugin which worked great prior to v 4 of FF needs to be updated. I am sure people are aware of this but doesn't seem to be any comments on when this can be resolved.

I don't think you will see that in Firefox 5.
There has been an enhancement request for this since 2006, it has received some attention earlier this year but there is no sign of it being implemented just yet.

The destination plugin required for this action is disabled.

Dear all, I am using Infoviewer first time and for testing purposes I uploaded our Lab rework report. The viewing side is absolutely fine however if I try to send the file via email, ftp etc it gives me the following error:
The destination plugin required for this action is disabled. If you require this functionality, please contact your system administrator.
I have looked on one of the forums where one user mentioned to restart the destination job server. I have tried that but it didn't work. It somehow looks like I haven't installed the plugins onto the server or maybe somewhere it has been disabled.
Could you please help.
Many thanks
Kind Regards
Jehanzeb
Error given below:
============
Title:         LabRework
Description:
Created:      01/07/2008 16:57
Last Modified:      01/07/2008 16:57
Last Run:      01/07/2008 17:07
The destination plugin required for this action is disabled. If you require this functionality, please contact your system administrator.

OK. From CMC, I can use do the following:
1. Go to Home>All Objects>
2. Select the object
3. Hit the History tab
4. Click Send to... and select FTP
This is explained on xir2_bip_Admin.pdf.
However, I can't do this via Infoview.
i.e.
When I try to send a file from the History it doesn't end up in the FTP location.
But what does work is if I select the report itself, the RPT format is sent to the FTP location.
This makes sense from a perspective that if you don't schedule a Crystal Report, you will not have a PDF version of it. On the other hand, whay wouldn't I be able to send it from the History selection on Infoview.

Why won't Adobe reader no longer let me view previously download (from Safari) pdf's? I am running OSX 10.8.5 and have uninstalled and reinstalled latest version of Reader?

Why won't Adobe reader no longer let me view previously download (from Safari) pdf's? I am running OSX 10.8.5 and have uninstalled and reinstalled latest version of Reader. I get this error message "Adobe Reader could not open 'OD Test Bed Proposals_0.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded)." I have tried changing the 'open with' options too. Thanks

Try this:
Go to: Mac HD/Library/Internet Plug-ins
Trash the AdobePDFViewer.plugin and AdobePDFViewerNPAPI.plugin files
Empty the trash
Relaunch Safari. You can now download undamaged PDFs.

Wrong warning? to open with Reader (9.3.x or higher) "This PDF form requires a newer version of ..."

Hello
I have a problem with my form, when opened with Adobe Reader Version 9.3.0.148 (included) or higher Reader systematically shows the annoying message "This PDF form requires a newer version of Adobe Reader ...".
I work with 3 versions of each form:
1) Dynamic PDF Form XDP: Generated with Adobe Designer ES 8.2, (target version "Acrobat and Adobe Reader 8.0 or later. "
XDP form has no "Warings"
XFA-Template:
2) PDF Form, generated from the XDP form of point 1), using Adobe LC Forms ES2 "renderXDPForm" method.
3) Flatten PDF, generated from the PDF form, resulting in point 2) value, using Adobe LC Assembler ES2.
DDX:
I have generated 3 different PDF rendering, changing only the "target version":
a.1 PDFFormRenderSpec.setAcrobatVersion (AcrobatVersion.Acrobat_6): MyForm-ES-AcroVersion6.pdf.
b.1 PDFFormRenderSpec.setAcrobatVersion (AcrobatVersion.Acrobat_7_0_5): MyForm-ES-AcroVersion7.pdf
c.1 PDFFormRenderSpec.setAcrobatVersion (AcrobatVersion.Acrobat_8): MyForm-ES-AcroVersion8.pdf
Of all that I've created a flat version using Assembler:
a.2: MyForm-ES-AcroVersion6-flatten.pdf
b.2: MyForm-ES-AcroVersion7-flatten.pdf
c.2: MyForm-ES-AcroVersion8-flatten.pdf
Attach all forms of work[zip 4 download].
Well ... I tried to open all forms generated (six) with versions of Adobe Reader from 8.1.0 to 10.0.1.434 X and the findings are that the annoying warning message is displayed only with the flattened forms and from version 9.3 .0.148 (included) or higher.
Table of test, where
OK= No message at open.
Err= Message displayed.
I do not understand or just logical that the most current versions (and higher) Reader is precisely this message to appear at what may be due? What's happening?
Why the message is taught only in the flattened forms?
How I can solve this problem?
Thanks.

I do not use the method "renderPDFForm" (at least not explicitly), instead use the "renderXDPForm (...)".
I added the XDP form the zip (I forgot): download from here!
And the only parameter that you can tell this method over the "target" of the resulting PDF is "com.adobe.idp.services.PDFFormRenderSpec. "
/* Common to all generated PDF */
com.adobe.idp.services.PDFFormRenderSpec renderSpec= new com.adobe.idp.services.PDFFormRenderSpec();
renderSpec.setLinearizedPDF(true);
renderSpec.setLocale("es_ES");
renderSpec.setRenderAtClient(RenderAtClient.No);
renderSpec.setCacheEnabled(false);
renderSpec.setStandAlone(true);
/* Target version 8 o superior: Usede ONLY to generate "MyForm-ES-AcroVersion8.pdf" */
renderSpec.setAcrobatVersion(AcrobatVersion.Acrobat_8);
/* Target version 7.0.5 o superior: Usede ONLY to generate "MyForm-ES-AcroVersion7.pdf" */
renderSpec.setAcrobatVersion(AcrobatVersion.Acrobat_7_0_5);
/* Target version 6 o superior: Usede ONLY to generate "MyForm-ES-AcroVersion6.pdf" */
renderSpec.setAcrobatVersion(AcrobatVersion.Acrobat_6);
After this, process PDF forms resulting in Assembler.
I tried also NO explicitly assign the "AcroVersion" ... and in such cases, the resulting AcroVersion indicated corresponds to the time of design (Adobe Designer, File / Form Properties / Default / Target Version), and in such cases the resulting PDF, also displays the warning message.
I do not know if I answered your question.
Any idea?

Acrobat hijacked Safari PDF's

All PDF's are shown by the Acrobat Reader plug-in. There is a preference in Acrobat Reader 7.0.5 (Prefs/Internet/Dispay PDF is browser using). Unchecking this does NOT stick. Next time I open Acrobat or even enter Preferences, the checkbox is set again. Is there a way to stop Acrobat from taking over Safari PDF's?
best regards
Lars

Lars,
Quit Safari.
Find and remove the AdobePDFViewer.plugin and archive it into a different folder. It will be located in either: Macintosh HD/Library/Internet Plug-Ins or ~Library/Internet Plug-Ins.
Restart Safari.
;~)

Safari pdf does not open

safari pdf files does not open

In the Finder, select Go ▹ Go to Folder... from the menu bar. Copy the line of text below into the box that opens, and press return:
/Library/Internet Plug-ins/AdobePDFViewer.plugin
If a Finder window open with that item selected, delete it, then quit and relaunch Safari. Otherwise post again.

Can the Adobe PDF plugin carry exact phrase search criteria through from source system into Reader?

In SharePoint 2013 if you search for an exact phrase and then view a PDF that is returned by the search (in Reader via the PDF plugin) then the Reader will treat the complete phrase as individual words.
For example, search for "High Court" in SharePoint, get returned a set of PDF documents, and when you view one of them through the Reader the hit highlighting will be for each instance of "High" or "Court".
What is wanted is hit highlighting only of instances of "High Court".
I get the same behavior if the Adobe PDF plugin is installed with the Filesite DMS. So it seems to be standard behavior for the Adobe PDF plugin
Is there a way to make the Adobe PDF plugin carry exact phrase search criteria through from source system into Reader? And then hit highlight the exact phrase only.

Hi Sam,
You can opt for 'Advance Search' option in Reader to match the whole words to get to the specific documents.
Regards,
Rave

Adobe PDF writer has taken over my computer for documents, how do I change it back to Safari PDF ?

How do I change back to Safari PDF viewer and get rid of Adobe?

Find a PDF file in the Finder, select it and go File > Get Info. Find the Open With section and change the application from Adobe Reader (?) to whatever other PDF viewing app you prefer (Safari.app?). Click on the button that activates in that section (Change All...) and say Yes to making every PDF open with the new option your choose.
In my opinion, viewing PDFs posted on websites in Safari is fine, but viewing PDFs downloaded or that reside on your iMac are better suited to being viewed using Adobe Reader (though you might not be used to what it does), or Preview. You should explore what they have to offer.
Hope this helps.

PDF plugin on Mac

The "official" (or at least, recommended by your FAQ) PDF plugin on Mac isn't supported on FF4 (well, you can compile it to be ran on FF4, but it needs to be ran in 32 bit). Since development on this plugin has stalled, what will you do about it? Chrome has a built-in plugin, and since Core Image provides support for PDF reading, it wouldn't be that hard to implement either... (please note that I have no coding knowledge, so I work on that, but I'd love to :) )
For the record, I uninstalled it since it wasn't supported and I now use Preview to open PDFs. But it's very annoying.

The following link may help, it has a version of the add-on that works in 32 bit mode - http://code.google.com/p/firefox-mac-pdf/issues/detail?id=189

Adobe PDF Plugin not working FireFox and SeaMonkey

Just updated to Acrobat XI. I find that the plugin to view PDF's doesn't work. just receive a Blank Screen when I try to view a Plugin.
I also notice in addons when you go to plugins it shows two acrobat Pdf Plugins:
Adobe Acrobat NPAI Plugin
Adobe AAMDetect Adobe AAMDetect 1.0.0.0
and the one called 1.0 I have no idea what that is.
I see no sign of the Adobe PDF Plugin (which is in the Internet Plugins Folder)
I can use a Plugin from Schubert from Germany but it doesn't work with buttons to swich to a web page.
I can use Acrobat Reader. However in order to work it has to download the page from a website first. Who wants to do that.
Can't you get this fixed???

Adobe Acrobat NPAPI Plugin is not supported in Firefox or SeaMonkey. Try disabling this plug-in from Firefox/SeaMonkey > Tools > Add-ons, then quit and restart your brwosers.
This should let you save/downlaod the PDFs locally.

Safari pdf plugin requires $60+ fee. What's up?

Similar Messages

Maybe you are looking for