Zum Hauptinhalt gehen

Sign-In link for iPhone

Kommentare

10 Kommentare

  • Hi David, as far as I know there is no link for sign-in/sign-out in the smartphone UI. I solved this issue by adding two buttons in the "I want to menu" that run the commands "SignIn" and "SignOut". Jason from LG also suggested that you modify the viewers' JSON files (Desktop.json.js, Tablet.json.js, Handheld.json.js) in order to set visibility of the two buttons only when it make sense:

     

    {

       "text" : "Sign In",

       "command" : "SignIn",  

       "hideOnDisable": true

    },

    {

       "text" : "Sign Out",

       "command" : "SignOut",

       "hideOnDisable": true

    }

     

     
    0
  • David Major

    Thanks, worked like a charm.

    0
  • Permanently deleted user

    I'm trying to disable (i.e. make invisible) the sign-in link for a desktop app.  I've scoured the json files and changed a few visible settings to false that I thought would do the trick but I can't get it to work! Can anyone point me to the right spot?

    0
  • Permanently deleted user

    Look for the view "SignInView" configured inside of the Banner module and set "visible" to false, or just remove it entirely.

    0
  • Permanently deleted user

    I removed this code block from this file: C:\inetpub\wwwroot\Html5Viewer\Resources\Config\Default\Desktop.json with no luck.  Am I editing the wrong file or removing the wrong piece of code?  Setting visible = false didn't do anything.

      "moduleName": "User",

     

                    "moduleType": "geocortex.essentialsHtmlViewer.mapping.modules.User.UserModule",

     

                    "configuration": {},

     

                    "views": [

     

                        {

     

                            "id": "UserInfoView",

     

                            "viewModelId": "UserInfoViewModel",

     

                            "visible": false,

     

                            "type": "geocortex.essentialsHtmlViewer.mapping.modules.User.UserInfoView",

     

                            "markup": "Mapping/modules/User/UserInfoView.html",

     

                            "region": "BannerContentRegion"

     

                        },

     

                        {

     

                            "id": "SignInView",

     

                            "viewModelId": "SignInViewModel",

     

                            "visible": false,

     

                            "markup": "Mapping/modules/User/SignInView.html",

     

                            "type": "geocortex.essentialsHtmlViewer.mapping.modules.User.SignInView",

     

                            "region": "BannerContentRegion",

     

                            "configuration": {}

     

                        }

     

                    ],

     

                    "viewModels": [

     

                        {

     

                            "id": "SignInViewModel",

     

                            "type": "geocortex.essentialsHtmlViewer.mapping.modules.User.SignInViewModel",

     

                            "configuration": {}

     

                        },

     

                        {

     

                            "id": "UserInfoViewModel",

     

                            "type": "geocortex.essentialsHtmlViewer.mapping.modules.User.UserInfoViewModel",

     

                            "configuration": {}

     

     

     

     

     

    0
  • Permanently deleted user

    I removed the same code from C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\Public\Viewers\Public_Mapping\VirtualDirectory\Resources\Config\Default\Desktop.json and that did it!  Yay!

     

    So...why the 2 Desktop.json files in different locations?  It's confusing to say the least!

    0
  • Permanently deleted user

    The configuration file in wwwroot is the absolute default, fallback, no-configuration-specified configuration file. If someone visits /Html5Viewer directly, that file is the one that gets loaded. Any viewers you create using Manager will have their configuration files in the Essentials folder structure, as you've found.

    We're of the opinion that hitting /Html5Viewer should load *something*, rather than nothing, which is partially why a default configuration file is present. The other reason is that some advanced users configure viewers by hand, rather than using Manager. The configuration file in /wwwroot is where they put their custom configuration in this case.

    0
  • Sean McClurkan

    So do I have to remove the code body itself?  Setting visible=false in both files still doesn't seem to get rid of it.

    0
  • Permanently deleted user

    Setting visible = false didn't work for me either.  I removed the entire code block as described above to actually see results! Jason's explanation about the 2 different json files helped too.  At least now I know which one to edit :) 

    0
  • Sean McClurkan

    Yes.  The rhinocerous with the blowtorch did the trick.

    Thanks!

    0

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