Make WordPress Core

Opened 3 years ago

Last modified 2 years ago

#53756 new defect (bug)

Can’t Change Tags’ Letter Case

Reported by: pugs's profile pugs Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.8
Component: Taxonomy Keywords:
Focuses: Cc:

Description

Dear WordPress.org:

I love using your CMS, but I think I found my first bug tonight. Here it is: Once I create a tag for a post, I can’t change its letter case — even if I delete the tag and add it again. For example, I want my site to use a standard where the tags of proper nouns and the like have the first letter capitalized or are all capitalized (e.g., Denmark, COVID-19). All other tags can be all lowercase (e.g., coronavirus, gray matter). The problem is once I create a tag, it seems that tag and its case are permanently in the system and they can’t be changed.

I hope you fix this bug, because the little stuff like this matters to English majors like myself and probably many other writers and bloggers.

Please reply to this ticket if you fix this bug or are planning to fix it.

Sincerely,

Nicholas

Change History (2)

#2 @Presskopp
2 years ago

You can create a tag directly editing a post or you can create/edit them in Posts/Tags. For every tag a slug is created, which will be all lowercase by design. So for a tag "Denmark" the slug would be "denmark", and if you then add a lowercase tag "denmark" the slug would be the same and the tag won't be created therefore. In the post view, after a reload newly created tags vanish (fail silently), which would be identical in slug. In the tags view, an error will be given "A term with the name provided already exists in this taxonomy." in this case.

So the tag will "survive" which was created at first, the name can then be lower or uppercase.

In other words: Only the name can be uppercase, but not the slug. Tags with the same slug will be dropped.

We could consider to throw the error mentioned above also in the post edit screen instead of just silenty fail.

Still for me this is no bug, but a "wontfix" and/or "worksforme"

Note: See TracTickets for help on using tickets.