This plugin remains unfunded, so its future is in some doubt, however, for the time being I have added the following:
https://github.com/merefield/discourse-locations/pull/134
@viddekla that should resolve your issue
https://github.com/merefield/discourse-locations/pull/135
https://github.com/merefield/discourse-locations/pull/136
If you think Locations is awesome and I did a great job here, you can buy me a coffee 
I should add the new quick find current location target button on the location selector works for Topic locations too if you disable location input fields. 
Just needs a tweak to styling …
Important bug fix, please update:
https://github.com/merefield/discourse-locations/pull/138
(only impacts user locations entered since this weekends patch, simply enter them again)
Makes me think this is from the Locations Plugin 🌍.
Yes, you no longer need to run both. In the Locations Plugin, it is trivial to determine the country code, so why not offer a flag to go with it?
You should lowercase the country code @merefield
Country codes out of the box in Locations are lower case. Perhaps it relates to a third party data provider.
I offer paid support if someone needs me to take a closer look or PR welcome.
That is the issue, I changed it to lowercase manually and it loaded. Tried Mapquest and Mapbox with same results. I’ll shoot you a PM Rob.
Hello, thank you for this plugin which is great
I am trying to display the name of my subject on the map because I only have the location
Is there a parameter to activate?
Thank you
Some updates:
@Renato kindly fixed an issue on Category settings:
https://github.com/merefield/discourse-locations/pull/144
We had a contribution for the Russian language, thank you!
https://github.com/merefield/discourse-locations/pull/143
And finally I added an experimental new Topic List filter called Nearby:
https://github.com/merefield/discourse-locations/pull/142
Which lists all the Topics within x km (setting) from the logged in user’s supplied location.
@Barney_Lodge that was inspired by your use case and took up most of my Sunday 
This also fixes the inline location selector for Topics on the modal.
Oh wow!!! I am loving Discourse !!
Regards
Barney Lodge
In a past but recent release there was a bug in the UserLocation population logic. That is now fixed, but there may be some data impact.
This doesn’t currently affect much but may affect the map in the future.
You can identify if you have the problem by running this on the rails console:
array_for_fix = Locations::UserLocation.where(state: "state").pluck(:user_id)
if that’s not empty, simply run this:
array_for_fix.each do |id|
Locations::UserLocationProcess.upsert(id)
end
The other way this can be fixed is manually re-entering the user map location, so basically future user location edits will simply overwrite the bad data.
Apologies for the inconvenience.
If anyone wants to write a migration or rake task, PR welcome.
Is it possible to implement this feature:
After a user publishes a thread or reply, automatically detect the location based on their current IP address and display it below their avatar in the thread/post—instead of requiring users to manually select it or set it in their profile.
I am willing to provide paid support for this.
Just like ZHIHU.
Involuntary update of user location would be a big departure for this plugin as to date it’s been reliant on voluntary submission and therefore individual user buy-in.
But I can see the case for it. It would make gathering user location much more reliable and less dependent on user action.
There’s already a Post label for user location on every Post. So I think this part is already covered.
I think automated update of user location as a site option during posting is feasible and reasonable so long as:
It would be optimal if we could standardise on MaxMind, which is the standard IP Geolocation service native to Discourse core.
I would be happy to consider sponsorship to add back end automation as a site option. I’ll contact you via PM to see if we can reach agreement.
City-level precision is sufficient. Street-level precision would be terrifying.
Having a granularity option as a site default would be brilliant. As would the ability of the users to alter the granularity / opt out.
2 national forums I run would be great for province granularity. A local one would be great for suburb granularity.
I can easily imagine sites using all the options.
Thank you, I ran this and it found something:
discourse(prod)> array_for_fix = Locations::UserLocation.where(state: "state").pluck(:user_id)
=> [175, 12, 578, 1347, 1355, 1, 590]
discourse(prod)* array_for_fix.each do |id|
discourse(prod)* Locations::UserLocationProcess.upsert(id)
discourse(prod)> end
=> [175, 12, 578, 1347, 1355, 1, 590]
Then I ran the first command again and it still found 590, which also did not vanish when I ran the second command:
discourse(prod)> array_for_fix = Locations::UserLocation.where(state: "state").pluck(:user_id)
=> [590]
discourse(prod)* array_for_fix.each do |id|
discourse(prod)* Locations::UserLocationProcess.upsert(id)
discourse(prod)> end
=> [590]
What can I do? 
Delighted to announce that both @祁同伟 and @nathank have stepped up to sponsor 
the work for setting user location via IP
This work will be experimental for a while, but I’m also delighted to tell you the PR is already up here:
https://github.com/merefield/discourse-locations/pull/147
This is not a simple lookup, we do more than that - this will allow you to set a specific granularity (e.g. city) for all automatically determined locations in order to protect user privacy whilst increasing community trust.
(Yes, there will be some issues with VPNs and I’m afraid we can’t easily overcome that).
Once I’m satisfied this is working sufficiently well I will merge it.
It sits behind a feature flag in any case.
I’ll keep you posted, but exciting times, this is potentially one of the best additions to Locations we may have had for a while.
Thanks again to @祁同伟 and @nathank !!
And yes, there will also be a rake task to do this for all existing users …
Is it possible to show notices on Discourse’s backend through a plugin, for cases like this?
I could easily have missed your post