Topic: Antecedent Name Has Already Been Taken/More Detailed Error Message?

Posted under Site Bug Reports & Feature Requests

I want to create a BUR in which I suggest the removal of an existing tag alias (sukumizu -> one-piece_swimsuit) and re-alias it to another tag (sukumizu -> school_swimsuit), but I cannot do so because the tag being aliased "has already been taken", which, as far as I understand, means it is part of a pending request (please correct me if I'm wrong).
I am, however, unable to find any pending requests that contain the tag "sukumizu", so I am unsure as to how to proceed.
Is there no other way except for waiting for the pending request (which I'm not sure even exists (again, please correct me if I'm wrong)) to be processed?

While I'm on this subject, and though it is incredibly presumptuous of me to say so, I'd like to suggest adding a little more text to error messages to make it easier for users who might not be as familiar with the script system to determine what they've done wrong.
If one makes a request and sees that it hasn't gone through because "the antecedent name has already been taken", they might not have any idea what that means.
Adding a one or two sentence explanation to the error message on how they might remedy their mistake will not only make it easier for newer, inexperienced users to engage with and help to improve the site, but it will also reduce the number of future forum posts similar to this one asking what on earth an antecedent is.
Again, it is incredibly pretentious of me to suggest such a big change when the only real problem is my lack of experience, but I cannot help but think that this would make things just a little bit more accessible.

bitWolfy

Former Staff

You can't both remove an alias from a tag and re-alias it to another tag in a single BUR.
That's one of the disadvantages of that format.

Just split it into two parts, and put the second part in a [code][/code] block in the description.

bitWolfy

Former Staff

garfieldfromgarfield said:
got it. thank you. sorry for making such a big deal out of it lmao

Don't worry about it. I understand being confused about that message.
It's just a weird limitation that's not documented anywhere.

  • 1