@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.
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?
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?
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.
I am curious- what will it take, engineering-wise and monetary-wise to have an API endpoint to write/ retrieve the location for a topic? High level, I am thinking about a workflow such as this, with the API being used in the last step:
User start a new topic with information about a business establishment: name, city, and sometimes neighborhood
Use a workflow automation tool such as n8n to retrieve the topic name and content and feed it into an LLM model to return a street address
Standardize the address format with e.g. Google Maps API.
Send the street address to the location plugin API to POST the address for the topic.
We enabled the location functionality for the users, but adoption varies. Some users always include locations, some never. So I am trying to solve for the users who donāt add locations.
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.
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.
Its actually not user location that we are after, but the location of the businesses (restaurants) they are writing about, hence why we still need an LLM to analyze the content of the post, e.g. The French Laundry, Yountville, and find the address of the restaurant:
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.
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: