[wp-trac] [WordPress Trac] #46010: Auto-generated term slugs can be greater than 200 characters, giving "Could not insert term into the database." error
WordPress Trac
noreply at wordpress.org
Wed Jun 18 10:29:51 UTC 2025
#46010: Auto-generated term slugs can be greater than 200 characters, giving "Could
not insert term into the database." error
-------------------------------------------------+-------------------------
Reporter: mikejolley | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting
| Review
Component: Taxonomy | Version:
Severity: normal | Resolution:
Keywords: needs-patch needs-unit-tests dev- | Focuses:
feedback close |
-------------------------------------------------+-------------------------
Changes (by callumbw95):
* keywords: needs-patch needs-unit-tests dev-feedback => needs-patch
needs-unit-tests dev-feedback close
Comment:
Hi All,
I have taken a look at this now that this with the latest version of
WordPress and It appears there is a string length limit in place now to
stop this from erroring when inserting into the database. It no longer
throughs up an error message as before, but instead just truncates behind
the scenes without any notification that it has done this.
In regards to the string length due to the encoding, this still appears to
be prevalent, but I really cannot think of a solution to get around this
issue, and I am not sure that there will be one.
As the main complaint from this ticket looks to be resolved in the latest
releases, I believe we can close this ticket down?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/46010#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list