1253773 - Consider upgrading/updating to the latest mapbox.js version, which is 2.3.0

Status: RESOLVED WONTFIX

(Mozilla Reps Graveyard :: reps.mozilla.org, enhancement, P2)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

I'm honestly not sure precisely *which* benefits we'd get, but we should consider upgrading our bundle of mapbox.js to the latest, which is 2.3.0:

https://www.mapbox.com/mapbox.js/api/v2.3.0/

Here's our copy: https://github.com/mozilla/remo/blob/master/remo/base/static/base/js/mapbox.js

Comment 1

[Daniele "Mte90" Scasciafratte]

The last release is 3.1.1 so probably require a check of all the javascript to backport everything.
I have the issue that on local system the map is not showed and I don't understand why (I will attach a screen for that).

Comment 2

[Daniele "Mte90" Scasciafratte]

Attachment: Screenshot_20180316_132006.png

Comment 3

[Michael Kohler [:mkohler]]

(In reply to Daniele "Mte90" Scasciafratte from comment #1)
> The last release is 3.1.1 so probably require a check of all the javascript
> to backport everything.
> I have the issue that on local system the map is not showed and I don't
> understand why (I will attach a screen for that).

https://www.mapbox.com/help/how-access-tokens-work/

There is a Django setting to put it in.

Comment 4

[Daniele "Mte90" Scasciafratte]

That is not documented on the docs of course.
Get ready for a pull request about the documentation 

Comment 5

[Daniele "Mte90" Scasciafratte]

New pr for that https://github.com/mozilla/remo/pull/1450
Require a new access token.

Comment 6

[Michael Kohler [:mkohler]]

As we've moved from reps.mozilla.org to the Community Portal, I'm closing this bug. Filter out these emails by searching for "REPS_PORTAL_BUG_CLOSURE"