[openstreetmap/openstreetmap-website] Allow users to change trace visibility in bulk (PR #7324)

Ruben L. Mendoza notifications at github.com
Mon Aug 24 20:49:32 UTC 2026


@Rub21 commented on this pull request.



> @@ -0,0 +1,70 @@
+<% content_for :heading do %>
+  <h1><%= @title %></h1>
+  <p class="text-body-secondary"><%= t ".description" %></p>
+<% end %>
+
+<%= form_tag({ :action => :change_visibility }, :method => :get, :class => "row g-3 align-items-end mb-3") do %>
+  <div class="col-sm-4">
+    <%= label_tag :visibility, t(".filter.visibility"), :class => "form-label" %>
+    <%= select_tag :visibility,
+                   options_for_select([[t(".filter.any"), ""]] + (Trace::VISIBILITIES + Trace::LEGACY_VISIBILITIES).map { |v| [t("traces.visibility.#{v}"), v] }, params[:visibility]),

@pablobm , yes, you are right, and that is what I had in mind in [#7321](https://github.com/openstreetmap/openstreetmap-website/issues/7321#issuecomment-5301687777). The filter should only list private and public, since the page is there to move traces away from the legacy values. 

currently these dropdown need to be fixed,  only to private an public, 

<img width="656" height="150" alt="image" src="https://github.com/user-attachments/assets/815446c1-b6a1-4682-9817-5fe8ea83b212" />


-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7324#discussion_r3847355041
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/7324/review/5012425931 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20260824/af7d2b36/attachment.htm>


More information about the rails-dev mailing list