Closed shrouta closed 3 years ago
Hi shrouta,
I'm having trouble replicating this issue. What version of Omeka Classic and Neatline are you currently using? Is it possible to share the particular WMS layer you're trying to get working, and I can see if it loads on my end?
Thanks, Elizabeth
Looking into this issue further, there is a possible chance your WMS layers are not loading due to browser changes in policy regarding mixed content - ie loading unsecure http:// resources on a https:// site. (See here for chrome). This means a WMS address using http:// will automatically update to https://. If the resource does not match, then it will not load. One way to test this in Chrome is to include your WMS resources to your Neatline exhibit as usual, then click on the lock icon to the right of the site url:
Click on Site Settings, and from there, scroll until you find "Insecure Content" in the list. It likely is set to Block(default). Change the setting to "Allow":
In your Neatline editor, refresh the page to update the settings, and see if the WMS map layer loads. If it does, then the browser is blocking the http:// content by default. You should reset the Chrome setting back to Block after testing, for security reasons. I can consult Neatline developers further on this, but it may mean that your resources will need to use secure https.
Elizabeth, Thanks for this recommendation. I’ll give it a try!
AHS
On Oct 27, 2020, at 11:22 AM, eam5 notifications@github.com wrote:
Hi shrouta,
I'm having trouble replicating this issue. What version of Omeka Classic and Neatline are you currently using? Is it possible to share the particular WMS layer you're trying to get working, and I can see if it loads on my end?
Thanks, Elizabeth
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/scholarslab/Neatline/issues/494#issuecomment-717319206, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC4LNSZKZJTYD66QIJ57YN3SM3QTFANCNFSM4S6UQYYA.
It looks like WMS layers aren't loading - and producing a "Failed to load resource: net::ERR_CONNECTION_TIMED_OUT" error. This looks to be true across different wms servers (mapwarper, nypl and self-hosted)