Locations Plugin 🌍

[merefield (Robert)]

Release 6.8.11

IMPROVE: align User Map permissions with User Directory permissions

@Roi you got your wish … this was admittedly quite an important one.

User Map will no longer serve data if any of following is true:

• User is not logged in and hide_user_profiles_from_public is active.
• Plugin setting location_user_map is OFF
• Site’s enable_user_directory is OFF

User Map link in community section should no longer show in those circumstances either.

---

If you think Locations is awesome and I did a great job, you can buy me a coffee , and if Locations is important to your business or organisation, please consider sponsoring me on one of the higher tiers . This will all help to guarantee timely updates to Locations and its future.

[Roi]

@merefield

@Roi you got your wish … this was admittedly quite an important one.

Oh wow great, thank you so much! I cannot believe that this never popped up before and was asked.

I will try tonight and update the addon.

Don’t get me wrong and think that I am greedy and inappropriate: But is it also possible to hide the Location user post if activated along with the user map as well for guests and search engines?

[merefield (Robert)]

I don’t think it shows for search engines? Check the crawler view.

In any case I’m afraid I’m going to have to stop making any changes for a bit and get on with some paid work.

[dsims (Daniel)]

@jamesmarkcook

I was also wondering what the Enable location topic status icons for topic lists in this category setting does.

@dsims

Also location_topic_status doesn’t appear to be used anywhere.

For anyone else wondering, it looks like the TopicStatus map-marker icon was removed, but the settings remain.

[merefield (Robert)]

@dsims

location_topic_status

Here’s the original commit:

add topic status icon && improve serialization && fix spec

I think this means it was just a setting to add an icon to the Topic List (via “TopicStatus”) … I’m not sure why you wouldn’t just handle this via the new Topic List location label and handle its visibility via CSS?

Therefore I think it’s redundant and probably all related code should be removed?

Any thoughts/objections?

[dsims (Daniel)]

I just started using this plugin so I can’t speak to others who might have been using that setting, but I could see why one might want a more subtle indicator that there is location rather than the whole location label. But I was able to get the same thing after tinkering with some CSS (hint float: left) so yeah, likely redundant.

[Jagster (Jakke Lehtonen)]

Fresh upgrade of Discourse (and everything) and the plugin broke:

But it works when starting a topic, but the issue pops up when trying to edit that post.

Affects only if a category has location enabled.

At least iPad with newest OS.

[merefield (Robert)]

Bedankt voor het rapport.

Ik kijk er misschien binnenkort naar.

[merefield (Robert)]

I elected to fix the current deprecations:

FIX: several deprecations

I’ve removed the broken tag

[ckshen]

Ik ben benieuwd - wat is er technisch en financieel nodig om een API-endpoint te hebben om de locatie voor een onderwerp te schrijven/ophalen? Globaal denk ik aan een workflow zoals deze, waarbij de API in de laatste stap wordt gebruikt:

1. Gebruiker start een nieuw onderwerp met informatie over een bedrijf: naam, stad en soms wijk.
2. Gebruik een workflow-automatiseringstool zoals n8n om de onderwerpnaam en inhoud op te halen en deze in een LLM-model te voeren om een straatadres terug te geven.
3. Standaardiseer het adresformaat met bijvoorbeeld de Google Maps API.
4. Stuur het straatadres naar de locatie-plugin-API om het adres voor het onderwerp te POSTen.

We hebben de locatiefunctionaliteit voor de gebruikers ingeschakeld, maar de adoptie varieert. Sommige gebruikers voegen altijd locaties toe, sommige nooit. Dus ik probeer een oplossing te vinden voor de gebruikers die geen locaties toevoegen.

[merefield (Robert)]

The Geocoder gem that ships with the plugin already does a lot of cool searching (and could be used to do more e.g. IP lookup). The data formats used by the plugin are standard already.

You can probably reverse engineer the API using the browser requests as a guide.

@ckshen

We enabled the location functionality for the users, but adoption varies.

Yes, my experience too. If someone wanted to support an option for mandatory IP based defaulting of user location I’d be up for a PR (though this would need to be an opt in tick or something as a bit of a privacy leak!)

There is also a current in-flight PR here (which adds a simple button to the UI for topic locations) but the author seems to have abandoned it? (which would be a shame) … could be extended for User location theoretically … lowering the barrier further.

FEATURE: add button to fetch current location from browser

[ckshen]

Het gaat ons eigenlijk niet om de locatie van de gebruiker, maar om de locatie van de bedrijven (restaurants) waarover ze schrijven. Daarom hebben we nog steeds een LLM nodig om de inhoud te analyseren van wie ze schrijven, bijv. The French Laundry, Yountville, en het adres van het restaurant te vinden:

6640 Washington St, Yountville, CA 94599-1301

en het vervolgens terug te voeren naar de locatie-plugin.

[merefield (Robert)]

Begrepen, vrijwel zeker te doen met de huidige plugin.

Uit interesse, benaderen ze de site vanuit het restaurant? U zou dit kunnen vergelijken met IP-gebaseerde locatie voor een sanity check.

[ckshen]

Nee, meestal daarna.

[Roi]

Today after updating Discourse this great plugin shows some deprecations, one also on the page itself for admins:

[Admin-Hinweis] Plug-in ‘discourse-locations’ enthält Code, der aktualisiert werden muss. (ID:discourse.jquery-autocomplete) (mehr erfahren)

Others in the developer console of the browser:

DEPRECATION: [PLUGIN discourse-locations] The user property path was used in the discourse/plugins/discourse-locations/discourse/templates/connectors/user-card-location-and-website/replace-location.hbs template without using this. This fallback behavior has been deprecated, all properties must be looked up on this when used in the template: {{this.user}} [deprecation id: ember-this-fallback.this-property-fallback] This will be removed in ember-this-fallback n/a. See Resolving the `this-property-fallback` deprecation for more details.

DEPRECATION: [PLUGIN discourse-locations] The showUserLocation property path was used in the discourse/plugins/discourse-locations/discourse/templates/connectors/user-card-location-and-website/replace-location.hbs template without using this. This fallback behavior has been deprecated, all properties must be looked up on this when used in the template: {{this.showUserLocation}} [deprecation id: ember-this-fallback.this-property-fallback] This will be removed in ember-this-fallback n/a. See Resolving the `this-property-fallback` deprecation for more details.

DEPRECATION: [PLUGIN discourse-locations] The linkWebsite property path was used in the discourse/plugins/discourse-locations/discourse/templates/connectors/user-card-location-and-website/replace-location.hbs template without using this. This fallback behavior has been deprecated, all properties must be looked up on this when used in the template: {{this.linkWebsite}} [deprecation id: ember-this-fallback.this-property-fallback] This will be removed in ember-this-fallback n/a. See Resolving the `this-property-fallback` deprecation for more details.

DEPRECATION: [PLUGIN discourse-locations] The removeNoFollow property path was used in the discourse/plugins/discourse-locations/discourse/templates/connectors/user-card-location-and-website/replace-location.hbs template without using this. This fallback behavior has been deprecated, all properties must be looked up on this when used in the template: {{this.removeNoFollow}} [deprecation id: ember-this-fallback.this-property-fallback] This will be removed in ember-this-fallback n/a. See Resolving the `this-property-fallback` deprecation for more details.

[merefield (Robert)]

@kelv kindly updated the code to remove potentially the last piece of jquery and modernise the Location Selector!

DEV: refactor LocationSelector to glimmer component and use DMultiSelect

Thanks very much @kelv !

[Canapin (Coin-coin le Canapin)]

Hi,

I have a “Users Map” link in the side menu:

Which leads to https://unicyclist.com/locations/users_map

I couldn’t find any setting related to this link.

The only setting I’ve found is Location sidebar menu map link, disabled by default, which adds this “Map” (leading to https://unicyclist.com/map) link when enabled:

Can I have only the “Map” link without relying on custom CSS? Am I missing something?

[Viddekla (Julian Müller)]

I integrated that plugin in my discourse - but how can a user delete his location? Everytime if i am deleting it in a profile, it occurs again and again.

[sshen]

i have used the plugin for a few years. it always worked. recently after i updated discourse and the plugin, when i try to enter the location of a topic, it asks me to Select Options. When I selected the dropdown, it doesn’t display any choices. Question: how can our users avoid this dropdown and go back to entering the address? Thanks.