(Chrome 42 and later has disabled NPAPI plugins so only their native viewer can be used to view PDF files). Workaround for any user: Google Chrome - Disable Chrome Native PDF Viewer. If you do this, be sure to delete the old file from your website if it is still there after the upload. If you did not rename the file back to the original filename, then you will need to update any links pointing to the old filename.
Update/Upload the fixed file to your website. Rename the file back to the original filename that you have on the website. Verify as you did in step #1 above that the file now says “ Yes” for Fast Web View. and save your PDF to a NEW filename (you can change the name later). Open your PDF in Adobe Reader to view it. Click on the Documents category from the list on the left, then check the box for Save As optimizes for Fast Web View, then click on the OK button. Open Adobe Reader, Click on Edit, and then click on Preferences. Note, saving to PDF using Microsoft Word does not save it with Fast Web View enabled. 
In some cases you can fix this using the free Adobe Reader instead of doing it with the Adobe Acrobat Pro paid version. Click on the Description tab.Įxample of a PDF file that does not work (No) – See if your PDF supports Fast Web View, open the PDF from your desktop computer (not a web browser) using Adobe Reader and click on File=> Properties. You can prevent this problem and the need for your users to use the Workaround for any user steps below by just saving/configuring your PDF’s to enable Fast Web View (Yes) before you upload them to your website. Save all PDF’s with Fast Web View enabled prior to uploading to your website and publishing it for your users. This error will happen for specific PDF’s, yet not others, even on the same website when the browser tries to display the PDF in itself rather than downloading and saving it on your computer. When clicking on a PDF link on a website using the Google Chrome or Microsoft Edge internet browser, you may receive the error below. This Articles applies to: Content/CMS Editors, Content Creators
0 kommentar(er)
