-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recent changes? #4
Comments
There haven't been any changes on this end at all in quite some time. |
Thank you. Will just to set object option and use the browser's native viewer until I figure this out. Maybe I will update and use this newer viewer: |
I can update the version of PDF.js used here, but since you're saying things used to work and now don't, I'm not sure it's likely to make much of a difference. |
I changed nothing on my side. Does it point to a cdn on the cloud? |
There's no CDN or cloud dependency. When you choose the PDF.js option, all the stuff needed for the viewer is served locally. |
What are the server dependencies, if any, that allow PDF.js to run? |
I pushed a new release that has an updated version of PDF.js. |
did not resolve |
F 52.2.1
Windows 10
Using this http://omeka.org/add-ons/plugins/pdf-embed/
https://github.com/zerocrates/PdfEmbed#readme
which uses your library
Suddenly I hate to turn off, because PDFs were not rendering on the site. We have a complicated setup, where PDFs are behind a firewall and proxy tunnels in via htaccess.
Where there any changes that would suddenly not allow for this type of setup?
The text was updated successfully, but these errors were encountered: