Moin
April 15, 2026, 1:27pm
1
I am a little confused by the new feature which explains why I cannot use certain tags. Depending on the search term, it sometimes says I can use the tag in this category and sometimes it says I can’t. If I was not allowed to use it in this category, shouldn’t that be conststent? Though I think I am allowed to use theme component tags in support, so I wonder why the autocomplete says I am not
4 Likes
Ahah, my bad feature needed to be a tad bit “smarter” when it comes to limits
main ← fix-disabled-tags-mislabeled
merged 07:01AM - 16 Apr 26 UTC
When searching tags in the composer, `filter_allowed_tags` applies a LIMIT (`max… _tag_search_results`, default 5). If more allowed tags match the query than fit under the limit, the overflow is silently dropped.
`append_disabled_tags` then ran a naive substring query for visible tags matching the term, assumed any tag not in the allowed list must be excluded by filter rules, and asked `explain_exclusion` to fabricate a reason. Allowed-but-cut-off tags leaked into the disabled list and showed the vague fallback "\"X\" cannot be used in this category".
Because `filter_allowed_tags` orders by term (`DISTINCT ON (lower(name) = lower(term), ...)`), the same tag could appear allowed under one search term (prefix match, ranks high, fits in the limit) and disabled under another (mid-string match, ranks lower, gets cut off) — producing inconsistent verdicts for the same tag in the same category.
Before labeling any tag as disabled or forbidden, re-run `filter_allowed_tags` scoped to the candidate names (no limit) and drop any that come back allowed. Extracted to `reject_allowed_tags` so both `append_disabled_tags` and `detect_forbidden_tag` go through the same verification. The probe is skipped when the allowed result didn't saturate its limit, since no cutoff is possible in that case.
https://meta.discourse.org/t/400696
3 Likes
The 