[OJS 3.1.2.1] Pdfs problem

Software Support
1

Captura 2019-08-14

help please

3.1.2.1

2

Hi @DGI_Investigacion,

Has anything changed in that installation recently, e.g. an upgrade to OJS?

Regards,
Alec Smecher
Public Knowledge Project Team

3

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.

4

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

5

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?

6

Hi

I have a same problem, somebody found it the solution?

1 Like
7

I do not find the probelma friend

8

Hi

This problem is of server’s restrictions for security reasons. However, to disable of “mod_headers” from Apache solved the problem.

9

friends please could you help me where can I find that denial please