Ah, okay, thanks. I wonder if that’s a neccessity, or an oversight.
Let me run another one past you…
Occasionally a flag leads me to check a user’s history. The activity of Lxk520 above is an example where that’s all untranslated. Is this normal too?
I think the post list is currently not supported. The topic activity appears translated for me, just like /latest. I am not sure if there is a feature request where this is tracked.
Yeah. I’ve manually updated the topic title to English, so it should be ok now.
It’s super tricky because I knew we’d have some case of “topic title in LanguageA and first post in LanguageB”. But the composer for the first post/topic is only wired up to set the same language for both topic title and first post.
I’ll bring it up internally to see how we can deal with the UX around this.
Should a feature request addressed by an unofficial TC be closed as completed?
I believe the GitHub link was changed to https://github.com/discourse/discourse/blob/main/frontend/pretty-text/addon/allow-lister.js, in which case the link should be edited in the post.
No, I think it’s good to still keep that one open.
Sorry! Since I knew that adding the fixed tag would reopen the topic I avoided adding it on closed topics. But I didn’t expect the topic to also reopen the topic if I add a different tag and the fixed tag had already been there before. Endless loading of post history when latest revision is hidden/inaccessible
I’ve closed it, but interesting that any tag edit re-opens it… might be worth fixing
Thank you!
I think it only happens if the fixed tag is used, not any tag. But I expected the problem to be limited to the fixed tag being added, not any tag edit while the topic is also tagged fixed
Yeah, should have clarified I meant when fixed is applied already. I’ve seen topics get reopened when fixed is retroactively applied (and have been fixing them as I go) but you added revisions which has nothing to do with fixed. Re-opening fixed topics is only a small annoyance but having it automatically open when you add any tag seems unintended (albeit an edge case).
For me fixed is for fixed issues and they were (mostly) issues 
But I guess in some cases those tags can indeed overlap and that’s no big deal if one or the other is used.
Should there be a localization tag put on Emoji picker search now works in your language?
I mentioned a while back that editing older posts can easily cause category mentions to break because the structure has changed. The syntax for subcategories is different, so each category that has become a subcategory is affected by this.
Now it’s not just a few category mentions that are broken in posts that were recently edited - it’s most of them, in many posts. I guess posts were rebaked recently.
For example:
I know we’re supposed to only report things we can’t fix ourselves, but it didn’t seem practical to go through all the wiki posts now and update them manually. I can’t fix the other posts anyway. So maybe a bulk replace for all categories that are now subcategories is the better solution.
I think the broken tag on the custom wizard plugin topic could be removed.
I am not a member of @plugin_authors [1] so I cannot edit tags on topics in Customization > Plugin even though I am TL3
I am not allowed to @mention the group, so no users were harmed by notifications ↩︎
We’re looking into fixing the category links! Thanks for mentioning it
Yeah, if it’s not practical, I think it’s certainly worth bringing it up as you did here instead. Thank you.