• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Data Sources Does Not Appear

    User help
    7
    17
    4.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Jared WiltshireJ
      Jared Wiltshire
      last edited by

      @phildunlap said in Data Sources Does Not Appear:

      Uncaught ReferenceError: normal is not defined

      Also further references -
      https://stackoverflow.com/questions/50672599/dojo-uncaught-referenceerror-normal-is-not-defined
      https://github.com/kriszyp/xstyle/issues/44#issuecomment-76512785

      Developer at Radix IoT

      1 Reply Last reply Reply Quote 0
      • L
        leoboeng
        last edited by

        Ah ok, thank you !! It worked, was testing on 2 different PCs and all 2 were with Google Chrome.

        1 Reply Last reply Reply Quote 0
        • P
          Phillip Weeks
          last edited by

          Guys that is wonderful news and I have updated the all our V3 servers. However this same chrome error exists on our 2.8.8 systems as well. Will you be updating the code for 2.8.8 to fix this ?

          Jared WiltshireJ 1 Reply Last reply Reply Quote 0
          • O
            ordosays
            last edited by ordosays

            Here for the same problem.

            EDIT - the update seems to have fixed it. Now to the next issue. Memory leak/cpu usage.

            phildunlapP 1 Reply Last reply Reply Quote 0
            • phildunlapP
              phildunlap @ordosays
              last edited by

              @ordosays said in Data Sources Does Not Appear:

              Here for the same problem.

              EDIT - the update seems to have fixed it. Now to the next issue. Memory leak/cpu usage.

              Sounds like it would belong in its own thread if you want to ask us anything about what's going on.

              1 Reply Last reply Reply Quote 0
              • Jared WiltshireJ
                Jared Wiltshire @Phillip Weeks
                last edited by

                @phillip-weeks said in Data Sources Does Not Appear:

                Guys that is wonderful news and I have updated the all our V3 servers. However this same chrome error exists on our 2.8.8 systems as well. Will you be updating the code for 2.8.8 to fix this ?

                Probably not. You can however easily fix it by downloading xstyle from here - https://github.com/kriszyp/xstyle/archive/master.zip

                You will need to extract it to ${MA_HOME}/overrides/web/resources/xstyle

                Developer at Radix IoT

                P 1 Reply Last reply Reply Quote 0
                • P
                  Phillip Weeks @Jared Wiltshire
                  last edited by

                  @jared-wiltshire Thank-you millions Jared

                  1 Reply Last reply Reply Quote 0
                  • danD
                    dan
                    last edited by

                    Now I remember this fixed my other 2.8.8 systems. I couldn't find it for the life of me.

                    Comment for searchability for next time :-P
                    Cheers

                    1 Reply Last reply Reply Quote 0
                    • danD
                      dan
                      last edited by

                      Had this come up again on an instance of v3.4.0
                      Found putting the xstyle into the /overrides/web/resources folder it didn't take it, so ended up replacing the xstyle folder in /web/resources folder

                      N 1 Reply Last reply Reply Quote 1
                      • N
                        NinoK @dan
                        last edited by NinoK

                        @dan I have the same issue after updating Mango to the core v3.7.7
                        Chrome version is 92.0.4515.131 (Official Build) (64-bit)

                        When I switch to the old interface and switch to the Datasources tab, the list of data sources does not appear, just the empty white space. The data point tab works well. In the new interface, everything is alright.

                        When checking the browser's console I found there a bunch of errors like this ones:

                        Note: The actual IP address is removed and changed with <IP_address> tag.

                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/TabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/StackController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/Menu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/DropDownMenu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_MenuBase.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavContainer.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/ScrollingTabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/PopupMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_WidgetsInTemplateMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/CheckedMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
                        DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuSeparator.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

                        1 Reply Last reply Reply Quote 0
                        • Jared WiltshireJ Jared Wiltshire referenced this topic on
                        • Jared WiltshireJ Jared Wiltshire referenced this topic on
                        • First post
                          Last post