-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double sanitization in get_term function #1182
Comments
Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels. |
We've asked for a dev note here: Comment 22 has a good summary it appears |
As certain fields are not available to the docs release group, an additional note providing an overview of performance tickets in the run up to the Field Guide deadline, can be found on this docs sheet: Google sheet to better understand status on the performance labelled tickets. Note performance team is wrangling those tickets for identification, first draft and performance first review. |
Copying from Trac update. https://core.trac.wordpress.org/ticket/58329#comment:28 The following has been added to the Field Guide performance section based on the commit message in comment 22. We could not find this changed reference in the other mixed dev notes relating to performance. Please add any future dev note on this to the documentation tracking ticket so it can be updated in the Field Guide too. Thank you. "Taxonomy: The double sanitization in get_term function has been stopped. This will prevent the unnecessary calls to sanitize_term which was detrimental to performance. #58329." Discussion also raised |
Just to be included in FG, no dev note needed. needs-dev-note keyword removed |
This is in the Field Guide. |
Trac ticket: https://core.trac.wordpress.org/ticket/58329
Reported by and owned by spacedmonkey
Keyword on ticket needs-dev-note
This ticket is likely to be covered by one of the performance dev note clusters.
Note it is not in any of the three dev notes drafts shared by spacedmonkey by 2023/10/23. So check with performance.
This comment by Jonny has a good summary.
The text was updated successfully, but these errors were encountered: