HTML5 V1.3 viewer upgrade
Good day,
Recently started the upgrade process on a site with both a SL & HTML viewer on a DEV instance and ran into this issue. We've previously used Malcolm's recommended method numerous times for doing upgrades by using a standard name (e.g. 'SilverlightViewer') during VTE deployment, after renaming the old version to be replaced to a unique version name.
This time we successfully upgraded the GE core instance & Silverlight Viewer with the aforementioned method. After upgrading the viewer, the new SL version is displayed in the viewers list and the viewer functions as expected.
Tried the same process on the HTML5 viewer - renamed the old directory & specified the 'common name' for the new VTE deployment. It ran, but didn't appear to recognize the viewer as needing to upgrade (when you edit the viewer the first time after the upgrade). The old version (V1.2) is displayed is the viewer list. Editing the viewer definitely shows it's configured different (per the launch links for browser or GCX app vs. the older 3 links for PC, tablet, handheld), so the new codebase is running.
The biggest issue is that the new viewer doesn't appear to function correctly. The map servcies(s) display & the 'I Want Menu' has the configured workflows in it and appear to launch and accept value inputs. But they don't display any results because the left pane is always blank, even if attempting to display the layer list.
Has anyone else encountered this and have any guidance?
Thanks!
-
The upgrader is broken
I had to redo our Html app...
If you left them alone it should work.
0 -
Todd - I'm having the same issue - exactly as you described. The 1.3 template is loaded, but i never get an opportunity to upgrade the site configuration. Have you had any luck?
0 -
Forgot to add that I skipped 1.2.1 and am attempting to upgrade from 1.2 to 1.3. Not sure if skipping a version is playing a part, but I wanted to add that piece of information.
0 -
You cannot just leave them alone, if you want the new features. Until LG comes out with a patch, you will need to add a new viewer to your sites if you want to go to 1.3
0 -
As this is a Dev instance, I've dropped & recreated the viewer. Does get me back to a functional state, but I do seem to be hitting some issues with re-adding my workflows to the I Want To... menu.
0 -
Hi guys,
We've discovered a problem with the 1.2 to 1.3 upgrader not being run on some versions of Essentials. Unfortunately that includes the latest one. The fix has already been coded and we're just finishing testing a couple other fixes before we release a 1.3.1 version of the viewer. I expect it to be released later today or tomorrow.
If you've created a new 1.3 viewer this bug doesn't affect you. If you've opened up a 1.2 configured viewer as 1.3 you'll still be asked to upgrade it to 1.3 after installing the update.
0 -
Any news to provide on the progress of the 1.3.1 release? We are trying to plan the timing of our upgrade and it would be great to have a real schedule for the patch release.
Thanks.
-Tim
0 -
Hi Tim,
We're just doing final testing on the 1.3.1 viewer. It should be out Monday or Tuesday at the latest.
Cheers,
Jordan
0 -
Quick follow-up note: the 1.3.1 viewer is now available for download.
0 -
Just downloaded & attempted upgrade with the new 1.3.1 VTE file.
The VTE file is still called "Geocortex.Essentials.Html5Viewer.Template.1.3.vte". Is this as intended?
Once again using the procedure I originaly posted, I upgraded the viewer using the 1.3.1 download. Post install templates now list 2- HMTL5 1.3 entries (and can't tell which is 1.3 & 1.3.1). And opening the viewer in REST Manager, I was not prompted to upgrade.
Am I misunderstanding something or doing something wrong?
0 -
PS - the downloaded ZIP file is indeed "Geocortex+Viewer+for+HTML5+SDK+1.3.1.zip"
0 -
Hi Todd,
The recommended approach is to remove old templates with the same major/minor release numbers. For example 1.3 proper should be removed to install 1.3.1.
The reason 1.3.1 shows up as 1.3 is because it technically still is 1.3 and we are moving towards simplifying version numbers for users across the board.
You will not be prompted to upgrade 1.3 viewers to 1.3.1 - no upgrades happen for maintenance versions, as configuration is typically exactly the same.
-Jason
0 -
I am having an issue with GCE 3.15.1 and SLV 1.3.1 where when I create a new viewer it seems to create OK, but inside manager, all of the tools to change the viewer (i.e. Look and Feel, I Want To menu, etc.), are not correctly showing. (See attached.) Manager handles the Silverlight Viewer creation fine, it's just with HTML5 Viewers. This was happening inside of 3.15/1.3, so I upgraded to 3.15.1/1.3.1 and it's still not correctly displaying tools inside of manager. /customer/servlet/servlet.FileDownload?file=00P6000000elzRmEAI
0 -
Hi Jim,
The first place to start is http://support.geocortex.com/cannot-manage-viewer-for-html5-due-to-missing-content
If this doesn't work, ensure that your server can hit the ESRI Javascript libraries at //js.arcgis.com/3.6/ and //js.arcgis.com/3.6/js/esri/css/esri.css plus the Jquery library at //ajax.googleapis.com/ajax/libs/jquery/1.8/jquery.min.js
If your system cannot hit these resources because it isn't connected to the internet, you can get a copy of these files, place them on your server and update the URLs in the index.html for the HTML5 viewer.
Finally, you can use Fiddler as a proxy with Manager and see if there are other issues preventing the management pack from functioning. See http://support.geocortex.com/use-fiddler-as-a-proxy
regards,
Edmond
0 -
Edmond, the http redirection suggestion worked immediately. Thanks for the link and the quick response.
Jim
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
15 Kommentare