bingle-admin wrote:

Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/cdbrsLSf

Andre, a couple of questions:

1. Why the component is General/Unknown if the problem occurs on the special page Nearby?
2. Considering that the problem is also on desktop view, is it correct to set the product to MobileFrontend? Have I to open another bug for the desktop one?

The Nearby page is part of the MobileFrontend extension. The fact it appears on desktop is just a confusing side effect :) So no need to create another bug.

I've set to the correct component, we use General/Unknown when not sure :).

Jon thanks for the explanation. Just a curiosity: when "stable" component is used?

Please see the component descriptions: https://bugzilla.wikimedia.org/describecomponents.cgi?product=MobileFrontend

@Andyrom75 the mobile site has 3 modes available via Special:MobileOptions - stable, beta and alpha. It simply helps make clear to developers to know where to fix the problem.

Thanks to both Andre and Jon :-)

You need to set up your coordinate templates to save coordinate data, e.g. {{#coordinates}} part in https://en.wikivoyage.org/w/index.php?title=Template:Geo&action=edit (this particular code is suitable only for page's main coordinates). If you need help setting these up, ask us on #wikimedia-mobile, we're happy to help.

Thanks a lot Max I think at least I've improved the situation, if not fixed :-)

Feel free to make some test on https://it.m.wikivoyage.org and let me know if you agree that is working properly.