I think this is because of Fusion trying to append script tags (on the
client-side) to the template page from the ApplicationDefinitions (for
Google/Bing/OSM/Stamen) if it finds them and now its ringing security alarm
bells for modern browsers because of this.
Workaround? The simplest solution would be to rework the template entry
point so they all go through a server-side PHP script first.
ie. Instead of
servername/mapguide/fusion/templates/mapguide/slate.html?ApplicatonDefinition=...
We'd run
servername/mapguide/fusion/template.php?name=slate&ApplicationDefinition=...
And then within template.php, we'd output the HTML for the appropriate
template as indicated by {name} and be able to safely append the required
script tags if we find them in the {ApplicationDefinition}
- Jackie
--
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
