Chris, Since you are getting a CORS (Cross-Origin Request) Error, I suspect this has something to do with your configuration. It looks like it says it's not allowing you to access http://localhost:8182/... which means that origin is possibly missing from your "rest.cors.allowed-origins" setting in your local.cfg? https://github.com/DSpace/DSpace/blob/main/dspace/config/local.cfg.EXAMPLE#L227
That's my best guess. It doesn't sound like it's related to the 7.2.1 patch... instead, it sounds like perhaps your update accidentally *removed* a setting you had in place previously. I'd recommend double checking your configs...and moving *all* your custom configurations (in any *.cfg files) into your local.cfg (as that file will never be overwritten during an upgrade/update). Tim On Wednesday, April 6, 2022 at 9:30:24 AM UTC-5 Chris Clawson wrote: > Follow-up - *Still not seeing images in viewer*, but the image > metadata/etc now correctly shows up in the left bar of the viewer. The > viewer now knows there are 9 images but the screen error says ' TypeError: > NetworkError when attempting to fetch resource' . > My earlier installation omitted an entry in > /opt/dspace/config/modules/iiif.cfg, where I had "iiif.enabled = false". > This somehow didn't seem to matter then but it does now. The current > iiif.cfg file has the entry iiif.enabled = true. > > As of this writing, the console messages are saying things, like: > ERROR Error: unsafe value used in a resource URL context (see > https://g.co/ng/security#xss) > ERROR TypeError: this.vcr is undefined > Uncaught TypeError: Jc.viewer(...) is not a function > and > Cross-Origin Request Blocked: The Same Origin Policy disallows reading the > remote resource at > http://localhost:8182/iiif/2/d884028d-4d4f-4b96-9568-59fb0533cef8/info.json. > (Reason: CORS request did not succeed). Status code: (null). > (help?) > > On Tuesday, April 5, 2022 at 6:56:38 PM UTC-4 Chris Clawson wrote: > >> I am not sure what happened or where to investigate. I thought I had >> correctly applied the 7.2.1 patch for the backend security update. >> Everything seemed okay, except now I see that none of the >> dspace.iiif.enabled items will display images in the Mirador viewer. >> The following item had been setup as a series of slides... >> https://meloware.org:8443/handle/123456789/6475 >> There were 9 images, each with an edited description in the individual >> bitstreams metadata. Now the viewer says "1 of 0". >> >> Before I begin to tear things apart, is there an issue here? First >> suggestions? >> > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/34528a7e-9fdc-44d7-aafa-604f7d3c08f6n%40googlegroups.com.
