-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access Token #5
Comments
I'm not sure about an access token error; the only required key should be your mapbox ID (as an attribute (map-id) on the <mapbox> element) and the effect of leaving that out would be that the map tiles don't load (markers will still display, but just over an empty canvas instead of map tiles). I am going to move away from angular-mapbox-standalone, as that was more an idea of letting complete non-techies use the library. I've changed my thinking on that; I now believe a library of that nature should be written as a web component with Polymer.js, rather than an Angular library. If you feel like gisting your source code, I'd be happy to take a look. |
Here's what I have:
And here are the two errors I get:
|
OK, so if I add The first error about it already being loaded persists however. |
thanks Scott, that worked for me as well |
Hi, this was a compatability issue with Mapbox.js 2.0 (which now requires the API access token). I've updated the set of directives to work with 2.0, but the access token is still required. You can either set it by directly accessing the Mapbox.js library or by injecting This is addressed in v0.1.3 (363b01b) and docs have been updated. |
When I use angular-mapbox.js I get errors saying I need to include the access token, yet when I use angular-mapbox-standalone.js I do not and the map appears (though I'm loading angular more than once). Do I need to include the access token someplace when using angular-mapbox.js?
The text was updated successfully, but these errors were encountered: