However, for some users, PDF links from within document libraries opened separately in Acrobat Reader 11. This was only affecting PDF links automatically generated within a document library view - if a link was placed directly to a PDF file in the left-hand navigation or a content editor web part, the PDF would always open in the browser.
I've tried the usual things - change Browser File Handling Policy from Strict to Permissive, added "application/pdf" to allowed MIME extensions, etc. I knew the issue was related more specifically to the browser because Google Chrome was able to consistently open PDFs in the browser.
This is occurring because (from what I can tell) Adobe Acrobat Reader 11 is hijacking SharePoint 2010 PDF links in an effort to integrate better with SharePoint. This is why document library links are acting differently to direct PDF links. (It's possible to temporarily subvert this "feature" by holding down Ctrl when clicking on the link to the PDF document, which will open in a new tab, but will be in the browser.)
The reason Chrome and other non-IE browsers aren't affected by this is because Chrome et al have their own PDF rendering techniques, whereas IE relies on ActiveX plugins by Adobe or others.
It seems the only way to permanently fix this is a registry hack (from page 124 of the Acrobat Enterprise Administration Guide):
- Open the registry.
- Go to HKLM\SOFTWARE\Policies\Adobe\<ProductName>\<version>\FeatureLockDown.
- Create a key called cSharePoint.
- Create a DWORD value called bDisableSharePointFeatures.
- Set its value to 1.
Unfortunately, I have to now persuade our IT department to roll out this registry hack to all users...
No comments:
Post a Comment