La categoría principal no debería tener la insignia "read-only" si la subcategoría es de solo lectura

awesomerobot · 3 Febrero, 2026 17:42

¡Gracias por reportarlo, tengo una solución en camino!

github.com/discourse/discourse

UX: ensure read-only only appears once, on the relevant category (#37492)

main ← ux-read-only-one

opened 05:41PM - 03 Feb 26 UTC

awesomerobot

+7 -4

Reported here: https://meta.discourse.org/t/parent-category-should-not-have-read…-only-badge-if-subcategory-is-read-only/394943 We don't need to double-render this badge, especially because doing so is sometimes inaccurate (possible to have a read-only subcategory and a parent you can post in). This only passes read-only to the actual category, not all ancestors. I've also taken the opportunity to reduce the badge height slightly. Before: <img width="400" alt="image" src="https://github.com/user-attachments/assets/30e902ba-91e5-46f1-afec-fee48f32101e" /> After: <img width="400" alt="image" src="https://github.com/user-attachments/assets/0d28e980-1b79-4d74-b198-a78d30605c9e" />

Tema		Respuestas	Vistas
Ensure read-only categories remain read-only (even for admins) Feature	3	115	5 Julio 2025
Category badge missing on group permission and user summary page UX	4	119	4 Agosto 2025
Horizon Theme New Theme Info Button Layout UX horizon-theme	4	95	14 Agosto 2025
Category badges go missing at random Support	15	1044	23 Mayo 2022
Feature Req: ActivityPub notifications from read-only categiories Feature activitypub	0	39	29 Julio 2025

La categoría principal no debería tener la insignia "read-only" si la subcategoría es de solo lectura

Temas relacionados