nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Shortlist does not show user location

KellyShunn

Even with the "locate button" setting on and viewing the HTTP webpage, it does not display user location on mobile or browser. Using HTTPS brings up an "Unable to create map" error. Are there administrator changes that need to be made or is it a problem with the current beta?

I am beginning the upgrade from the old version (1.4.9) of Shortlist to the Beta, and a large reason for the upgrade is this built in location feature. Also as a side question, is there any projected time that this app will be out of beta?

Kelly

Encontre mais publicações marcadas com

Accepted answers

StephenSylvia

Kelly, It looks like the basemap in your shortlist app is a custom basemap that is hosted on an Amazon server. The server you are using does not have a https certificate. In order to enable location, you app must user a secure connection. However, when you choose to load you story map over https, the browser will block all requests to insecure connections (including your basemap) and as such your map will never load. This is a security restriction the browser puts in place and we cannot override in our apps. If you would like to continue to use your custom basemap, you will need to add a https certificate to your amazon server and replace the layer in the web map with a URL that starts with https.

All comments

KellyShunn

It will take a while to implement, but thank you very much for this idea.

StephenSylvia

KellyShunn

I am using Firefox and Chrome, also I have tried on a mobile webapp (android) to test for it future use by the public. The app is supposed to highlight the current blooming flowers at the Huntington Gardens. Volunteers and public will use it to decide their own personalized tour, so the location must be accurate for the best user experience. The larger image size, faster loading time, and easier editing are other features from the beta that are necessary, which is why just adding the code to 1.4.9 won't be sufficient.

First, the link below is the basic link that loads the app

http://huntingtonbg.maps.arcgis.com/apps/Shortlist/index.html?appid=78fab66df80c467fa6f31785cc61a28d

second, I just added an S to HTTP, if I should have done something else, please let me know.

https://huntingtonbg.maps.arcgis.com/apps/Shortlist/index.html?appid=78fab66df80c467fa6f31785cc61a28d

In case you don't get the same message as I do, below is a screenshot of the message from the HTTPS

Hope that is sufficient information, thank you for any help

RupertEssinger

Hi Kelly

We've not seen that issue you describe before. If your Shortlist is shared publicly, could you post a link to it here so we can take a look? You may want to also create a Story Map Series and turn on the Locate button in that app to see if that works for you too (you can find the option in the Settings > Map Options) because Story Map Series uses the same code as Shortlist for the button.

Note that in Shortlist 1.4.9 you can enable a Locate button. Here's a test example launched via https in which the Locate button has been turned on via a URL parameter (or in your index.html look for the GEOLOCATOR configuration parameter). The Locator button code in 1.4.9 is rather older: For example if a 1.4.9 Shortlist is launched on http the button still appears in the UI, whereas in 2.0 the button is hidden on http.

Rupert

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.