Geocortex Viewer for HTML5 Site Load Issues

Permanently deleted user

06 December 2017 17:56

On Tuesday, December 5th, some customers began to experience issues with their Geocortex Essentials HTML5 viewers not loading properly. The cause of the issue is double slashes in the URL for requests to some ESRI JavaScript libraries. Calls of this type were previously permitted. To see if you are affected by this issue, check Fiddler or the browser developer tools for 404 responses on calls to the ESRI JavaScript library. An example call would be:

 

 

 

(http://js.arcgis.com/3.21/dojo/parser.js) http://js.arcgis.com/3.21/dojo//parser.js

 

 

 

The response would be '404 Not Found' if you are affected, and '200 OK' if you are not affected.

 

 

 

To resolve this issue:

• On the Geocortex server, look for your inetpub directory and the HTML5 viewer folder. This is typically C:\inetpub\wwwroot\Html5Viewer but you may have elected to change the location or folder name. Inside this folder there should be a \Resources\Scripts\dojo-config.js file.
• Edit the dojo-config.js file and change this:

 

 

       {

 

            location: esriBase,

 

            name: "dojo"

 

        },

 

 

 

to this:

 

 

 

       {

 

            location: esriBase + "../dojo",

 

            name: "dojo"

 

        },

 

 

 

 

• Clear your browser cache and try again

If you need assistance making this change or have any issues or questions with it, please feel free to ask here, or submit a support case to (support@geocortex.com) .

0

• 

  Permanently deleted user

  07 December 2017 00:35

  Hello, all,

   

   

   

  Some great news. Esri will be rolling back the changes that were implemented which led to some viewers not loading properly.

   

   

   

  Their plan is to re-add the restriction at the next release of ArcGIS Online which is targeted around the March 2018 timeframe.  This will give us plenty of time to correctly fix this issue in our upcoming maintenance release, slated for the next week or two.

   

   

   

  Please note that Esri have confirmed that the workaround and the rolled back changes will work together, so there is no reason to remove the workaround if it is already in place.

   

   

   

  Best wishes,

   

  Pandora

  0

Du måste logga in om du vill lämna en kommentar.