Feature Hyperlinks in Chrome and Firefox
I am trying to set up feature hyperlinks to a file on disk (pdf or tif). It is working fine in Internet Explorer, but when I click on the link in the SL Viewer in Chrome or Firefox, nothing happens.
Here is the syntax: file:///T:/edms/Record drawings/{RECORD1}.pdf
If I type that into Chrome or Firefox (replacing {RECORD 1} with the unique id for the file) it also works, so I don't think there's anything wrong with the syntax.
Is there a setting I have to adjust in GE or in my browsers so that the feature hyperlink will open a new window or tab when clicked?
Thanks,
John Nerge
-
The Chrome and Firefox browsers do not allow plugins to access the filesystem in this manner due to security considerations. We are sorry, but there is nothing that we can do about this -- if these links are required you must use IE to access them.
0 -
No problem, Jonathan. Just happy to have an answer, thanks!
0 -
I'm getting the same behavior with Chrome in the HTML5 viewer, and there is no plugin there...
0 -
I am having somewhat of a similar issue. I have multiple pdfs stored on the server's Geocortex/Essentials/REST/virtualdirectory which are accessed through a feature hyperlink {RestVirtualDirectoryUrl}/ParcelCards/{Map}{SubMap}.pdf. Whenever I click the parcel feature to identify it, the hyperlinks works as expected. However, whenever I use a workflow to search for a parcel, click the result in the results window, and then click the feature hyperlink, it doesn't work at all. I can then identify the parcel right next to it with the identify tool or map tip and the hyperlink works again. This just seems to be the behavior for links to files on the server because feature hyperlinks I have set up for the same feature that go to an actual website work just fine with the identify tool or workflow.
0 -
I just figured out that the workflow wasn't returning the values I needed for the replacement tokens in the feature hyperlink. I fixed that and I can now see that when I click the link from the workflow results, the values are now showing up in the URL. However, for some reason, a space is getting encoded in the URL for features that don't have a {SubMap} when I click the link from the workflow results but not when I just identify the feature. Everything works fine for parcel features that have data in both {Map} and {SubMap} fields.
0
Please sign in to leave a comment.
Comments
5 comments