[wp-trac] [WordPress Trac] #31617: Adding new term is not checking uniqueness of slug
WordPress Trac
noreply at wordpress.org
Fri Mar 13 11:09:24 UTC 2015
#31617: Adding new term is not checking uniqueness of slug
--------------------------+------------------------
Reporter: gjaworek | Owner:
Type: defect (bug) | Status: closed
Priority: normal | Milestone:
Component: Taxonomy | Version: 4.1
Severity: normal | Resolution: duplicate
Keywords: | Focuses:
--------------------------+------------------------
Comment (by boonebgorges):
Replying to [comment:2 gjaworek]:
> Thank you for a quick reply, I understand that it could be a feature,
but I didn't seen it on release notes. I was so used to fact that term
slugs are quique, that I threated is as bug automatically. I will need to
adjust my applications now. As I understand from linked tickets, this also
will be possible to set the same slug for different taxonomies when
editing old term, notonly adding new one? In 4.1 it is still not working
perfectly.
You'll only need to adjust it in your applications if you are using custom
SQL queries to fetch terms, and depending on the uniqueness of slugs to do
so. Everywhere in the WP API (see functions like `get_term()`), a
`$taxonomy` parameter is required, which means that the ability to have
slugs duplicated in different taxonomies should not cause any issues.
There will be some related changes in WP 4.2 that *might* affect your
custom applications - see https://make.wordpress.org/core/2015/02/16
/taxonomy-term-splitting-in-4-2-a-developer-guide/ for more information.
As noted in my previous comment, the ability to set the same slug for
different taxonomies when editing is fixed in 4.1.1, which has already
been released, as well as 4.2.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/31617#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list