This plugin remains unfunded, so its future is in some doubt, however, for the time being I have added the following:
@viddekla that should resolve your issue
If you think Locations is awesome and I did a great job here, you can buy me a coffee 
4 Likes
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 β¦
3 Likes
Important bug fix, please update:
(only impacts user locations entered since this weekends patch, simply enter them again)
3 Likes
2 Likes
Makes me think this is from the Locations Plugin π.
4 Likes
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?
3 Likes
You should lowercase the country code @merefield
2 Likes
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.
2 Likes
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
1 Like
Some updates:
@Renato kindly fixed an issue on Category settings:
We had a contribution for the Russian language, thank you!
And finally I added an experimental new Topic List filter called Nearby:
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.
6 Likes
Oh wow!!! I am loving Discourse !!
Regards
Barney Lodge
3 Likes
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.
4 Likes