-
Notifications
You must be signed in to change notification settings - Fork 93
ReferenceError: google is not defined #20
Comments
Check out that you have no ng-app defined in you .html because angular it's going to load the module before you call you load it in the angular.bootstrap() method |
Thanx, got it working now. BTW the zoom-in-out panel is crippled. I fixed this with
Maybe you can add this to your introduction? As I use the map in a bootstrap-accordion for presenting some locations (around 30) loading the page takes its time I wonder what concepts I could use to make it more performant. Maybe use a map service? Have you any experiences/sample code that you could share? |
I've didn't use the zoom panel with this. And for the performance maybe you could put the libraries in your project and user requirejs optimization ? |
I am trying to set a marker. The HTML-code is: <section id="map"> <div ui-map="myMap" ui-options="$parent.getMapOptions(location.latitude, location.longitude)" ui-map-marker="$parent.getMarker(location.latitude, location.longitude, location.name)" class="map-canvas-locations"></div> </section> But I get an error "Converting circular structure to JSON" when adding the "ui-map-marker"-attribute. The code of the marker function is: $scope.getMarker = function(latitude, longitude, name) { return { position: new google.maps.LatLng(latitude, longitude), map: $scope.myMap, title: name }; }; Is the way I do it correct? |
hi getting the same error, because of the internet issue i guess.... but because of this issue my app is getting crash sometime.... |
I get the error "ReferenceError: google is not defined" before the function onGoogleReady() is called. I load your module like this:
If I do not use the attribute async when loading the GoogleAPI I get:
which is called in the line
of Google's js-script.
If I take the following Google-API-script:
and the controller
... then the maps is displayed but I don't have a callback function registered. Is there any demo-page I could use to solve this?
The text was updated successfully, but these errors were encountered: