Custom Module Broke when upgrading to latest release

Permanently deleted user

8. Juni 2017 21:15

We have a custom module Geocortex built for us that is a slider that transitions from an old photo on top to a more recent photo on bottom. You can view it in production here: http://mapitwest.fortworthtexas.gov/historicphotos/ just click on one of the blue dots for the pop-up transitioner to appear.

 

I upgraded our test server to the latest releases and now it's broke. I'm unsure of how to fix this without paying Geocortex more money to upgrade it. Any ideas would be most helpful!

 

Here is what test now looks like: https://testmapitwest.fortworthtexas.gov/Html5Viewer/?viewer=historicphotos

 

The upgrade went from: 

 

Essentials 4.5.1 --> 4.7.1

 

HTML5 2.5.2 --> 2.8.2

 

FYI it's a JS module. I checked and it's still in place after the upgrade, so i'm thinking it's something with upgrade not picking it up somehow? I forgot if I needed to register it via command line. I tried to make notes as Geocortex was deploying it 2 years ago but I could've missed a step, and we didn't get any type of documentation from then on it afterwards.

 

-Laura

0

• 

  Permanently deleted user

  8. Juni 2017 21:35

  Hi Laura,

   

  The new version of the viewer switched to AMD (asynchronous module definition), and it now needs a "require" element for all modules that get loaded.  It sounds to me like you need to add one.  Please take a look at this KBA:

   

  https://support.geocortex.com/essentialsGSCkba?sub-nav=kba&main-nav=essentials&/feedtype=SINGLE_ARTICLE_DETAIL&criteria=BESTANSWERS&id=kA360000000PPcMCAW

   

  For more details on that.  

   

  Thanks!

   

  Danny

  0
• 

  Permanently deleted user

  8. Juni 2017 21:56

  Thanks Danny!

   

  I checked and the code embedded in the Viewers is a little different in that it doesn't reference a GVH namespace. It looks like they created a custom name space for this module, so i'm not sure how to modify it.

   

  In the Libraries section the code looks like this currently:

   

        {

   

          "id": "HistoricalPhotos_Modules",

   

          "uri": "{ViewerConfigUri}../../Compiled/HistoricalPhotos_Modules_out.js"

   

        }

   

   

  In the Modules section the code looks like this currently:

   

        {

   

          "libraryId": "HistoricalPhotos_Modules",

   

          "moduleName": "HistoricPhotosMapTip",

   

          "moduleType": "geocortex.services.fortWorthTexas.historicPhotosMapTip.HistoricPhotosMapTipModule"

   

        }

  0
• 

  Permanently deleted user

  8. Juni 2017 21:57

  And within the Maptips module, which is what this costume Module replaces, it looks like below:

   

        {

   

          "moduleName": "MapTips",

   

          "moduleType": "geocortex.essentialsHtmlViewer.mapping.modules.maptips.MapTipsModule",

   

          "configuration": {

   

            "allowMultiple": false,

   

            "contentField": "longDescription",

   

            "webMapFeaturePresenter": {

   

              "force": true,

   

              "featurePropertyName": "currentFeature",

   

              "view": {

   

                "markup": "Modules/HistoricPhotosMaptip/HistoricPhotosMapTipView.html",

   

                "type": "geocortex.services.fortWorthTexas.historicPhotosMapTip.HistoricPhotosMapTipView",

   

                "libraryId": "HistoricalPhotos_Modules"

   

              },

   

              "viewModel": {

   

                "type": "geocortex.services.fortWorthTexas.historicPhotosMapTip.HistoricPhotosMapTipViewModel",

   

                "libraryId": "HistoricalPhotos_Modules"

   

              }

   

            },

   

   

  0
• 

  Permanently deleted user

  8. Juni 2017 22:22

  Hi Laura,

   

  If it's using a custom namespace, then I'm thinking we may need to create a new AMD namespace for it.  Since that module was created before we migrated to AMD, it's unlikely that one exists.

   

  That being said, since it's replacing the map tips, you might be able to use one of these:

   

  Mapping/modules/MapTips/MapTipContent

   

  Mapping/modules/MapTips/MapTipContentViewModel

   

  I hope that helps!  Please let us know how it goes!

   

  Thanks,

   

  Danny

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.