That is pretty simple. Just add this to your theme CSS:
.topic-list-item span.location-after-title {
display: block;
}
I have a different approach, which you can see here. So I just alter the font size and added this to my theme CSS:
.topic-list-item span.location-after-title {
font-size: .7em;
}
Perfect! Thanks @Roi 
I’ve decided to hide these now but I’m seeing some strange alignment issues, have I missed something with my implementation? 
.topic-list-item span.location-after-title {
visibility: hidden;
}The space is still being occupied, I think I need to collapse it left somehow?
You have to use display: none instead of visibility: hidden
D’oh 
Of course, thank you @RGJ 
Hello
The geolocation of a city or an address no longer works.
5 days ago everything was fine ( I was in an early May version of Discourse. )
I updated a few hours ago to the latest versions. The problem came after that I think…
After testing:
It works in “MAP LOCATION” in preferences/profile.
The error only occurs in localization within a topic.
My location geocoding provider is locationiq .
Their services are announced operational on their website.
Does anyone have this problem too?
Or an explanation?
Thanks for your help !
Stéphane
My forum: Carte festivals/conventions JdR - Forums FFJdR
I too am facing the same. While pin-pointing a new location in a new topic creation window, it doesn’t search any geo location:
While it was ok a couple of days back.
A fix is in progress guys, though this being a free plugin it is not prioritized.
I see reactions have arrived at meta
Thanks for the pending fix Robert 
Thank you for this info. At least we’re no longer in dark now.
PR pending review:
btw, if anyone is desperate for the fix or wants to help test this PR, you can, if you are brave enough, repoint your forum to this branch and provide me any feedback. Please read the comments at the top of the PR.
I’m not sure when it will be merged but at that point you will have to point back and rebuild. Just bear that disruption in mind.
NB: I have it running in Production and it seems fine.
There is a new experimental setting. I’ll let you find it.
I have the habit of breaking my forum in one way or another, but if help is needed here, I’d be glad to try the branch soon as I use this plugin and find it very useful. 
Thanks for this huge update Robert 
this going to be really great. 
I’ve noticed one thing in this PR or the previous one.
It seems this is not translatable.
Yes, naughty naughty of us, we let this one slip through without a thorough enough review @angus @nathank ! 
A very useful feature and gratefully received, but can I please have another PR which localises this?
With the lack of any negative feedback I’ve merged this big PR, so if you were on the PR branch, please rebuild to main to get all future updates.
https://github.com/paviliondev/discourse-locations/pull/81
Updates which now include:
I’ve also added localisation to @nathank’s helpful new user preferences link from the User Map page:
https://github.com/paviliondev/discourse-locations/pull/83
Let me know of any issues and I’ll follow up.
Thanks!
Didn’t find the time to try the fork 
I’ve deployed an urgent fix that resolves an issue with Topic location entry when location input fields are not enabled and adds corresponding tests:
Due to the historical lack of front-end tests on this repo (which we are in the process of rectifying) it’s sometimes hard to be absolutely sure of desired behaviour, so please let me know if you come across any issues and I will look into it.
