Overview:
This article is a summary of known issues reported or discovered when upgrading to version 2.8 of the HTML5 Viewer, and their suggested fixes.
This article is no longer being maintained and is for information only.
VertiGIS recommends upgrading to the latest version of software available to you.
Solution:
Query/Filter tools show all layers from all layer themes upon site load
Bug ID: GVH-10465
Symptom: After a site loads with a default layer theme other than 'All Layers', if the query/filter tool is opened prior to a change in layer theme, all layers from all layer themes will be selectable on the dropdown menu.
Fix: There is currently no fix or workaround for this issue.
Workflow form item does not validate in IE11
Bug ID: GVH-10510
Symptom: If a form item has validation and is not the first input item on the form, the form does not pass the 'Required Value' validation if you enter data in a text field and press a button which validates the form.
Fix: There is currently no fix for this issue. You can work around it by disabling autofocus in the Accessibility module. This must be done by editing the viewer's configuration files and setting automaticElementFocusing to false.
Visibility of layer added via layer catalog is not preserved when saving project
Bug ID: GVH-11626
Symptom: If a layer is added via a layer catalog, toggled to not be visible, and a project saved, when that project is loaded, that added layer will be visible, despite having been turned off prior to saving.
Fix: There is currently no fix or workaround for this issue.
JQuery library used in the viewer has a security vulnerability issue
Bug ID: GVH-12114
Symptom: Geocortex Viewer for HTML5 uses jQuery 1.8.3. According to insecurelabs.org, jQuery 1.8.3 has two known security concerns:
- Bug 11920: selector interpreted as HTML
- Issue 2432: Inadequate/dangerous jQuery behavior for 3rd party text/javascript responses
Fix: Bug 11920 is not an issue for the viewer because it doesn't have any jQuery selectors that set the HTML content of any page elements that can be changed by a user or an untrusted data source. Issue 2432 is also not a concern because the viewer doesn't use $.get() to access untrusted content. We will likely move to a newer version of jQuery in a subsequent release, but these issues are not a concern and we won't be upgrading specifically to address them. If desired, administrators can upgrade their installations to jQuery 1.9.0 to address Bug 11920 and jQuery 3.0 to address Issue 2432, but we recommend that you test your application comprehensively before deploying an upgraded viewer to production.
Geolocation doesn't work over HTTP in iOS 10
Bug ID: GVH-12177
Symptom: When attempting to use geolocation on a site that does not use SSL (i.e., over HTTP) or that has mixed content (using content served over both HTTP and HTTPS), the operation fails with an error: "There was an error in geolocation: insufficient permission for geolocation".
Fix: As of iOS 10, Apple requires HTTPS for geolocation. See this announcement for more information.
Feature clustering and heatmaps don't work with layer catalog
Bug ID: GVH-12926
Symptom: Layers added via a layer catalog do not work with feature clustering or heatmaps.
Fix: There is currently no fix or workaround for this issue.
IE9 stops responding after performing several large identify operations
Bug ID: GVH-13470
Symptom: While using the HTML5 viewer with Internet Explorer 9, the browser will stop responding after performing several large identify operations.
Fix: There is currently no fix or workaround for this issue.
Viewer's sharing links does not preserve base map layers
Bug ID: GVH-13734
Symptom: When launched via a shared link, the viewer application displays the default visible state of its base maps, rather than the visible state of the base maps when the link was created.
Fix: There is currently no fix or workaround for this issue.
Layer themes broken when including nested base map folders
Bug ID: GVH-13743
Symptom: When a base map folder whose sub-item visibility is set to "Only one visible at a time" is placed within another base map folder, and the default layer theme uses that nested base map, but another layer theme does not, when the user switches to the non-default layer theme, no base maps are displayed.
Fix: There is currently no fix or workaround for this issue.
Unable to create related spatial features
Bug ID: GVH-14279
Symptom: Users are unable to create related spatial features for a given layer. No errors appear in the browser console or viewer log.
Workaround: For the given layer, change the relationship name to be the same as the name of the related spatial service.
Fix: This issue is fixed in version 2.8.1.
Text halo configuration does not appear in IE 11
Bug ID: GVH-14249/GVH-14643
Symptom: When configuring text markup in the viewer, text halo width does not appear in the Select Drawing Style panel in IE 11. It appears in IE 10, as well as Edge, Firefox and Chrome.
Cause: Esri's JavaScript API versions 3.19 and 3.20 have a bug that can cause IE 11 to crash when drawing text markup with a halo. To avoid this, the option to configure a halo effect on markup text is removed in IE11. This limitation is mentioned in the documentation for the viewer's Markup Module.
Geolocation immediately returns a time-out error on iOS 10.3 and 10.3.1
Bug ID: GVH-14519
Symptom: When running the viewer on iOS 10.3 or 10.3.1 device, attempting to use geolocation will immediately result in an error: "There was an error in Geolocation. Geolocation has timed out."
Fix: This issue is fixed in the 2.8.1 viewer. In prior versions, this can be worked around by editing the viewer's configuration files (Desktop.json.js, Tablet.json.js, and Handheld.json.js), searching for "GeolocateViewModel", going to its configuration object, and adding "timeout": 100000000000 to the list:
],
"viewModels": [
{
"id": "GeolocateViewModel",
"type": "geocortex.essentialsHtmlViewer.mapping.modules.geolocate.GeolocateViewModel",
"configuration": {
"geolocateEnabled": true,
"trackingEnabled": true,
"followingEnabled": true,
"enableHighAccuracy": true,
"timeout": 100000000000,
"singleGeolocationProfiles": {
"default": {
"accuracyThreshold": 10,
"timeLimit": 30000
},
"coarse": {
"accuracyThreshold": 250,
"timeLimit": 10000
},
"fine": {
"accuracyThreshold": 3,
"timeLimit": 60000
}
},
"geolocateAccuracyCircleEnabled": true,
"adjustExtentZoomOnGeolocate": true,
"geolocateExtentZoomLevel": 50000,
"geolocationIndicator": "Resources/Images/Icons/geolocate-position-32.png"
}
},
Geocortex Collaboration does not function properly after upgrading from Essentials 4.3 or 4.4 to 4.7
Bug ID: GVH-14888
Symptom: After upgrading from Essentials 4.3 or 4.4 to 4.7, Geocortex Collaboration will not function properly. If you attempt to create new rooms in the viewer, the room may display, but its name is unreadable.
Fix: This scenario can be avoided by upgrading Essentials 4.3 or 4.4 to 4.5 prior to upgrading to 4.7. If you encounter this issue, please contact our Technical Support team.
Changing the coordinate system after plotting coordinates on the map makes the browser temporarily unresponsive
Bug ID: GVH-14891
Symptom: If, after plotting coordinates in the map, you change the coordinate system via the drop down menu, the browser may temporarily freeze up or stop responding.
Fix: This issue is addressed in the 2.8.1 viewer.
Microsoft discontinuing AJAX access for Bing maps on June 30th 2017
Bug ID: GVH-14980
Symptom: On June 30th, Microsoft is disabling access to Bing maps via AJAX calls. We have updated GVH 2.9 to use v8 of the Bing maps API. More information about this change can be found here. Bing services added via Manager are rendered using the Esri API rather than the Bing AJAX Control so they should not be affected.
Fix: Upgrade to GVH 2.9. If you are unable to upgrade, you can download the fixed version of the BingMaps.html file from here, and install it in the following folder: C:\inetpub\wwwroot\<YourViewer>\Resources\3rdPartyMaps
Missing "require" element breaks footer, feature details, and toolbar tools
Bug ID: GVH-14988
Symptom: After upgrading to GVH 2.8 you may find that some of your elements are missing or disabled. This includes, but is not limited to:
- Bottom panel (footer) missing from viewer UI
- Zoom in / out tools greyed out
- Feature details not appearing after clicking More Info from Map Tips
This issue is caused by missing Require elements in your json.js files.
Fix: Please see this KBA for details about this issue
Setting results list to use Feature Description has no effect - Feature Long Description is always used
Bug ID: GVH-15014
Symptom: When editing a viewer in Manager, in the "Look and Feel" section there is a setting for the content field that will be shown in the results list. Regardless of whether "Feature Description" or "Feature Long Description" is selected, the Feature Long Description is used in the viewer for the results list. The configuration for the Map Tips and Feature Details content still work as expected when set to show the "Feature Description"
Fix: This issue is fixed in the 2.8.1 viewer. In prior versions, you can manually edit your viewer configuration file to change the Feature long Description to the Feature description:
- Edit your Desktop.json.js file
- Search for the following string: "id": "FeatureSetResultsView"
- Look for the line in the element that reads: "contentField": "longDescription",
- Change it to read: "contentField": "description",
It should look like this:
{
"id": "FeatureSetResultsView",
"viewModelId": "FeatureSetResultsViewModel",
"libraryId": "Mapping.Infrastructure",
"iconUri": "Resources/Images/Icons/Toolbar/search-24.png",
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.FeatureSetResultsView",
"markup": "Mapping/infrastructure/results/FeatureSetResultsView.html",
"region": "DataFrameResultsContainerRegion",
"visible": false,
"title": "@language-common-results",
"description": "@language-common-query-results",
"configuration": {
"contentField": "description",
"isPaged": true,
"pageSize": 50,
"showBackButton": true,
"highlightMode": "default"
}
},
Images not displayed in Display Form
Bug ID: GVH-15081
Symptom: Images are not being displayed in workflow display forms in GVH 2.8
Fix: Upgrade to GVH 2.8.1
Unable to load site when signed in, with Analytics Integration module turned on
Bug ID: GVH-15385
Symptom: Your sites fail to load when the following conditions are met:
- You are running GVH 2.8.1
- You have authentication configured on your site
- You have the Analytics Integration module (client relay) configured
Fix: Upgrade to GVH 2.8.2
Sites share saved projects and collaboration rooms when other instances on the server use the same site name
Bug ID: GVH-15444
Symptom: Collaboration rooms and saved projects are available on a site with the same name on a different instance of Geocortex Essentials. This occurs when the second instance is on the same server as the first.
Fix: Change your site ID (by modifying the site.xml file) to ensure that your site IDs are unique across all your instances.
ConfigDomain issues after 2.8.x Viewer Upgrade
Bug ID: GVH-15570
Symptom: If you are using the Geocortex._configDomains option in your viewer config to pass the allowed configuration domain to your application, your viewer may fail to load due to a CORS error. This issue should only impact customers that are embedding viewers into third party applications.
Fix: Upgrade to GVH 2.9.
"Layers in Visible Scale Range Only" identify tool setting not honored when layers are children of a group layer
Bug ID: GVH-15720
Symptom: When you viewer is set to return results from the visible scale range only, layers that are children of a group layer that inherit their min and max scale are not defined. The child layers use the Effective min and max parameter instead. This results in the layers not being returned by the identify operation.
Fix: As a workaround, you can set the Min and Max scale override on the service in Essentials.
When "Highlight All Features" is selected, the highlight layer is not cleared when a new identify operation is run
Bug ID: GVH-15822
Symptom: When performing two back-to-back identify operations, the first highlighted feature set is not cleared.
Workaround: Modify the Desktop.json.js file to include the ClearDefaultHighlights command:
{
"name": "AllResultsPageChangedBehavior",
"event": "FeatureSetClickedEvent",
"commands": [
"ClearDefaultHighlights",
"HighlightFeatureSet"
]
}
Collaboration not supported in Internet Explorer 9
Bug ID: Not a bug
Symptom: You cannot load your collaboration rooms on Internet Explorer 9. If you look at the developer tools, you can see an error that states "Warning: Browser does not support web sockets. Collaboration cannot function."
Fix: Upgrade to IE 10 or newer.
Icons/Content missing from the Viewer Management Pack following the upgrade
Bug ID: Not a bug
Symptom: After upgrading to GVH 2.8 you may find that some of the icons or content in the management pack are missing/not displaying correctly.
Fix: Clear your browser cache, and refresh your browser.
For Internet Explorer, if clearing your cache doesn't resolve the issue, try this:
- In your browser, edit the viewer in Essentials Manager and navigate to the Toolbar page.
- Hit 'F12' to launch the browser's developer tools.
- Switch to the Network tab and ensure that 'Always refresh from server' is set to 'On' (for IE 11) or click on the 'Cache' menu and select 'Always refresh from server' (IE 10).
- Refresh the browser window displaying Manager.
Comments
0 comments
Article is closed for comments.