You'll want to switch to using fusion.js instead of fusionSF-compressed.js as outlined here and other places:
https://adndevblog.typepad.com/infrastructure/2012/04/debugging-fusion-viewer-or-mobile-viewer-of-aims-in-firebug.html Doing this will provide a clearer tracelog on which Javascript file the problem is originating from. Personally I use a separate index.html (index-test.html, for example) which references fusion.js instead of fusionSF-compressed.js so I can readily examine any such client-side errors. -Kyel -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html _______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
