File origin does not match the viewer's

farling42 / fvtt-pdf-pager

PDF Pager for Foundry

MIT License

6 stars 4 forks source link

File origin does not match the viewer's #106

Closed Babayushki closed 2 months ago

Babayushki commented 2 months ago

Foundry Version 11 (build 315 | stable) World System: Custom System Builder 3.2.5 Browser: Google Chrome Version 126.0.6478.127 (Official Build) (64-bit)

No installed modules are conflicting with PDFpager.

I get the following console errors when trying to view PDFs while the module is enabled: Screenshot 2024-07-14 022018

I do not have any problems with viewing PDFs when the module is disabled. I saw in the releases "Use legacy-dist version of pdfjs to support older Foundry/Browsers", but I do not know how to do so.

farling42 commented 2 months ago

Which specific version of the module are you using?

Babayushki commented 2 months ago

I'm using version 1.1.1

farling42 commented 2 months ago

What is the "PDF Source" you've set for the PDF file?

It seems that this error is being reported because there is a difference between the URL of the PDF browser window address and the URL of the PDF document itself.

Babayushki commented 2 months ago

I'm not sure to be honest. I'm not tech-literate. How would I go about checking? I only know how to look at the Document Properties in Adobe Acrobat.

To give some additional details/context:

The PDF is a character sheet which was created using PDFium. I edited the PDF in Adobe Acrobat to make it form fillable.
- In Adobe Acrobat's document properties, it says the PDF has no base URL.
I'm using The Forge to host. I uploaded the document to a folder in my asset library.
I can view PDFs in Journals; I cannot view them when using them as character sheets for actors. When attempting to open an actor, the sheet doesn't load.

Screenshot 2024-07-14 032427 Actor is on the Left; Journal is on the Right.

farling42 commented 2 months ago

Could you try version 1.1.2?

I checked what changes the Foundry team made in the PDF.JS library, and they specifically removed the check that would generate the error that you saw. I have made a similar change in the PDFJS library in PDF Pager, so hopefully it will be working properly.

Babayushki commented 2 months ago

That seems to have worked. Thank you very much! I don't have much to give, but I'll drop a tip for you.

Cheers!

farling42 commented 2 months ago

Many thanks for the donation! :-)