Users Momin and cocococosti reported a bug where, after renaming a tag, the next tag’s rename modal incorrectly prepopulates with the previously renamed tag’s new name instead of its own. For example, renaming “wanda-vision” to “WandaVision” causes the next tag “wonder-woman” to show “WandaVision” in the rename field until the page is refreshed. cocococosti confirmed the issue on Discourse 2.7.0.beta7, noting it’s low severity since the system prevents duplicate tag names. They suspect the bug lies in how Ember handles modal state. j.jaffeux identified the fix in commit 6b10ada and thanked the reporters. Momin acknowledged the fix and planned to test it.
I was able to replicate this. Here’s my bug report:
Priority/Severity : not high priority. Even if the user clicks rename tag by accident, it won’t let them change the tag because it’s already taken.
Platform : self hosted discourse instance version 2.7.0.beta7 in safe-mode.
Description : when a user changes the name of a tag, and then goes to rename another tag, the name configured in the previous tag shows up in the rename modal. This happens as long as the page is not refreshed.
For example, I have two tags: “naruto” and “sasuke”. First, I rename “naruto” to “uzumaki”. Before the change, the input field in the rename modal is already populated with “naruto”. Then I go to change “sasuke”, the input field is populated with “uzumaki” instead of “sasuke”.
The expected behavior here is that the input field is populated with the tag name to change.
I’m thinking the issue may be in the way the tag info is being updated in the ember modal?