help please
3.1.2.1
help please
3.1.2.1
Has anything changed in that installation recently, e.g. an upgrade to OJS?
Regards,
Alec Smecher
Public Knowledge Project Team
Thank you for your reply. I am working on this together with our tech specialist who posted this thread. We have installed a new 3.1.2 install on a new server and then we have manually uploaded back issues. So far, we have not gotten the HTML or PDF galleys to work, something seems to be blocking the frames from showing. The PDFs can be downloaded just fine, but they cannot be opened within the browser, since Chrome just shows the â(host address here) refused to connectâ error.
Hi @Michael_White,
Iâd suggest checking the browserâs debugging tools to see if you can identify what the server is giving the PDF.js client when it attempts to download the PDF.
Regards,
Alec Smecher
Public Knowledge Project Team
Thanks for the advice. I checked the Chrome debugger (Ctrl+Shift+J on Windows in Chrome) on the ârefused to connectâ page, and it showed this:
Refused to display âhttps://[journal URL]/plugins/generic/pdfJsViewer/pdf.js/web/viewer.html?file=https%3A%2F%2F[journal URL]%2Findex.php%2FRICTD%2Farticle%2Fdownload%2F514%2F508%2Fâ in a frame because it set âX-Frame-Optionsâ to âdenyâ.
Right now we are trying the config options outlined here to change the X-Frame-Options header. Iâll edit this comment with an update once we give it a try.
EDIT: We tried adding the X-Frame-Options header to the Apache config, and we still are getting the same error. Any ideas on what else could be causing this âX-Frame-Optionsâ to âdenyâ error?
Hi
I have a same problem, somebody found it the solution?
I do not find the probelma friend
Hi
This problem is of serverâs restrictions for security reasons. However, to disable of âmod_headersâ from Apache solved the problem.
friends please could you help me where can I find that denial please