Hello there,
I don’t think this is related to WordPress 6.8 release.
I just checked your site, and I noticed that your site is loading on https://www.jkandsons.com/ but the PDF is embedded on a page with https://jkandsons.com/. From a browser point of view, those are 2 different domains.
Citing our docs:
For security reasons, browsers are not allowed to load the PDF from a different domain.
Let’s say your site is available via both www.example.com and example.com. Then that’s an inconsistency that is also confusing to search engines and users.
To fix this, ask your web hosting company to make it consistent – for example, to redirect users directly from www.example.com to example.com, so everyone is using the same domain.
Then, you will need to ensure all your PDF Embedder shortcodes refer to the PDF’s URL in the new preferred manner. Various “search and replace” plugins (or the appropriate wp-cli command) may help you to make those changes all over your content.
So I would recommend to sync the domain (with or without www. part) you use and the URL you use to embed PDF files – they should be the same.
I hope this helps!
Thread Starter
gopar3
(@gopar3)
Thank you – this got me further but… now I’m getting an Invalid or corrupted PDF file error. I deleted and re-uploaded the file but I’m still getting an error. I can see the file normally and fill it out using a PDF editor, but PDF Embedder isn’t recognizing the file. What can be wrong now???
I think there are 2 issues on your site:
jQueryParam variable is not defined which breaks something on your site. We don’t have and don’t use this global variable, so I assume there is some other plugin that generates this error in the console of the browser. It may affect the PDF Viewer after the point 2 (below) is fixed.- Compatibility with plugins – which we tried to address in the just released 5.3.1.
So I would recommend to update to 5.3.1 – we introduced a lot of fixes around compatibility with other plugins.
Please let me know how it goes after the upgrade.
Thread Starter
gopar3
(@gopar3)
Updating to Release 5.3.1 didn’t fix this. I disabled the Siteground Optimizer plug-in and that fixed the issue. I went back and re-enabled it, then disabled all the Javascript optimization tools in the Frontend Optimization tab. That didn’t help so I next disabled all the CSS optimization tools. That fixed it!
Thanks for your help figuring this out.
Oh, that’s great that you figured it out!
We do have a somewhat relevant doc on using site optimization plugins, but it’s more relevant to JS. I haven’t seen yet that CSS optimizations caused issues. Thank you for providing feedback.
Have a nice rest of the week.
