Forum update deleted or hid the Patron badge due to it being miscategorized as a voice badge before

סיכום מבוסס בינה מלאכותית

twofoursixeight reports a bug where the Patron badge disappeared from the Dark Gaming forum after a recent update, resulting in a 404 Not Found error when accessing the badge URL or viewing user profiles that previously held it. The issue stems from a previous discussion where Voice badges overwrote a custom badge, and it appears the Patron badge was miscategorized as a voice badge, causing it to be deleted or hidden during the update. The user confirmed the badge existed before but is now missing, though they lack staff access to determine if it was fully deleted or simply hidden. sam clarifies that the badge should still exist but explains the root cause: Discourse currently seeds this badge by name rather than by a stable ID, leading to conflicts when updates or seed processes run. A fix is being developed by @awesomerobot, though it remains unmerged. The core solution proposed is to change the seeding mechanism to use strong, unique IDs to prevent such

Continuing the discussion from Voice badges overwrote a custom badge:

After another forum update to Dark Gaming, I am no longer able to find the Patron Badge on the Dark Gaming Forum. A 404 not found error occurs when going to the badge: https://forum.dark-gaming.com/badges/108/patron It was there before, but kinda glitched. Now, it is just completely gone. If you take a look at a user that once had this badge, like Profile - Dian - Dark Gaming, the Patron badge is no longer able to be found.

I opened the inspect console and the version of the forum is :information_source: Discourse v2026.11.0-latest — Commits · discourse/discourse · GitHub — Ember v7.3.0

I am still not a staff of the Dark Gaming forum, so I am unsure if it was fully deleted or just hidden.

לייק 1

Badge should still be there, but we seed this badge by name instead of by id so this gets very confusing on seed @awesomerobot has a candidate fix it is unmerged… but ideally we figure out a way of seeding badges using a strong id that way we will not end up having confusing “key is name” situations.