Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Testing: Basemap fixes and provider credentials

Chiusa
#82 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

@aviannamiller ci sta già lavorando.

Dal 4/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Branch: fix/basemap-providers. This covers #76, #80 and #81.

Most of our basemaps were broken. All six CARTO ones were watermarked without an API key, including Voyager, which was our default, so most sites have been showing a watermarked map. The six Stamen ones fail on any real domain, and Esri DeLorme was retired.

What changed:

  • The default basemap is now OpenStreetMap Standard instead of CARTO Voyager. Existing sites on Voyager will see their maps change unless they add a CARTO key.
  • There is a new CARTO API key setting.
  • If a CARTO or Mapbox basemap is missing its key, the map falls back to the default instead of breaking.
  • Stamen is the exception. It needs this site's domain registered with a Stadia account, there is no key to enter for it, and without the registration the map stays blank.
  • Base Map settings are now their own section on the config page, and each basemap option names its provider.
  • For #80, the Base Map description now recommends two basemaps with high contrast between map features. I explained the reasoning in a comment on that issue.

What to test:

  • Each basemap, everywhere a map appears: the browse map, item pages, exhibit pages, the Map tab when editing an item, and the admin side.
  • That the config settings still save. I moved fields around on that page, so it is worth checking a few unrelated to basemaps too.
  • CARTO with a real API key, Mapbox with a real access token, and Stamen with this site's domain registered with Stadia. Those three need accounts.
Lingua principale
JavaScript
Stelle
12
Fork
22
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di omeka/plugin-Geolocation

Tutte le issue di omeka/plugin-Geolocation

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.