PDFG Support

Hi @wattsyourwebsite,

The issue is with your Pagespeed caching. There are two possible solutions—if the first one does not work for you, then try the second. After each change, make sure that you flush the cache to reload the scripts.

1. You should take a look at the hosting configuration for Web Optimisation options that you can activate to optimise the site. I have had other customer that had activated their “One Click Optimisation” which “applies the most popular optimisation filters that should help improve page loading times without risking functionality”. By deactivating the option to Combine JavaScript which “Seeks to reduce the number of HTTP requests made by a browser during page refresh by replacing multiple distinct JavaScript files with a single one” the issue is resolved.
2. If you do not have the above interface, you can add “ModPagespeedJsPreserveURLs on” in the config file for PageSpeed to inform the cache not to combine and rewrite the script paths which is causing this error

• This reply was modified 1 year, 11 months ago by PDFG Support. Reason: typo

Hi @rjfpedro,

The Premium version of the plugin does allow you to embed a PDF that has fillable fields for the user to download. The fields will still be intact for the user to fill offline but no version of the plugin allows forms to be edited online*. If you want to permit the users to be able to upload the completed PDF back to your site, you would need to use another plugin such as Contact Form 7 with file upload enabled.

* please note that we are currently working on a new feature that will allow fields to be filled online; however, you would still need to provide a way for the user to upload the completed form such as the mentioned Contact Form 7 plugin.

Hi @redrockbob,

Did you get the plugin installed and activated on your site? If you are still encountering an issue, can you please drop us an email to [email protected] and we’d be happy to help you out.

Hi @rowhouse,

I’m not sure if you still require help with this. There isn’t an instance of the PDF Embedder code on that page but there are image files of the the PDFs. Perhaps the wrong module was used (i.e. an image module instead of a text-based module). For step by step instructions, please see https://wp-pdf.com/kb/drag-and-drop-layout-builders/

If you have any other questions, please do not hesitate to send us an email to [email protected] as we may not see the forum posts in a timely fashion.

Hi @jvalks,

There was a temporary issue on the checkout that has been since resolved. If you still encounter an issue, please do not hesitate to send us an email to [email protected] as we may not see the forum posts in a timely fashion.

Hi @vadim-s-sabinich,

Autoptimize and other caching plugins can cause issues with the rendering of the viewer by making the required scripts unavailable. To rectify this error, you will need to exclude the plugin URIs for the plugin scripts from the Autoptimize (and any other caching tools): https://wp-pdf.com/kb/using-caching-or-minifying-plugins/

The plugin scripts are already minified so you will not be losing any efficiency or load speed by excluding them. Be sure to flush any caches after you exclude the scripts so that they can be loaded by the site again and the embed viewer should be displayed correctly once this has been done.`

Hi @tschabs21,

The PDF Embedder will not remove or otherwise alter the original document; however, if there are multiple image layers and/or unflattened transparencies, the script may not recognize these and fail to render them as a result. It is possible that that the documents were created the same way but the final output step was different resulting in the missing elements.

For best results, ensure that when the document is exported to PDF for web publishing, that the options to flatten layers and transparencies is selected.

If you have any other questions, please do not hesitate to send us an email to [email protected] as we may not see the forum posts in a timely fashion.

Hi @clarenancy,

I’m not able to see anything on the WP site you are referring to. It looks like your DNS for the domain name hasn’t resolved yet which may be contributing to the issue you are having.

I’ve noticed that you have also sent an email to our support team so will continue following up there.

Hi @rwalsh456,

You can contact them through their website: https://wp-rocket.me/support/

Hi @rwalsh456,

The “player” error is what showed up in the console tab when viewing the page.

Have you reached out to WP Rocket support since the issue has to do with caching. They may have some additioanl suggestions for their plugin settings that we are not aware of which could be helpful in your case.

Thanks for sharing your findings @doughall222. I will get this passed on to the developers for further investigation.

Hi Ryan,

There is another error showing up in the console related to a “player” (Vimeo player API?). I would recommend resolving that error as well as errors in one JS-dependent element can cause cascading errors to other JS-dependent elements.

Hi @tubywubygmailcom,

Spotted your support inquiries in our email so replied there. Will close this ticket and continue via email.

Hi Ryan,

You may not have the query strings settings, but your test to disable the combine JS files confirms that the scripts are being cached.

While it is not normally needed to exclude the scripts, I would recommend that you exclude those. Once you click the Minify box and see the Combine checkbox, below that is a field to Exclude JS files from the minification/concatenation processes. Depending on which version of the PDF Embedder plugin you are using (free vs. Premium vs. Secure), the file path will differ for what you enter here. Please see:

• File paths for versions of PDF Embedder
• Excluding external javscripts from WP Rocket

Hi @rwalsh456,

The scripts are still being cached and are not loading on the page. I noticed that you are using WP Rocket. There is a specific setting for that caching plugin provided in our FAQ: https://wp-pdf.com/kb/setting-up-fake-worker-failed-error-message/