Make WordPress Core

06/22/2020 05:24:34 PM (4 years ago)

General: Remove “whitelist” and “blacklist” in favor of more clear and inclusive language.

“The WordPress open source community cares about diversity. We strive to maintain a welcoming environment where everyone can feel included.”

With this commit, all occurrences of “whitelist” and “blacklist” (with the single exception of the $new_whitelist_options global variable) are removed. A new ticket has been opened to explore renaming the $new_whitelist_options variable (#50434).

Changing to more specific names or rewording sentences containing these terms not only makes the code more inclusive, but also helps provide clarity. These terms are often ambiguous. What is being blocked or allowed is not always immediately clear. This can make it more difficult for non-native English speakers to read through the codebase.

Words matter. If one contributor feels more welcome because these terms are removed, this was worth the effort.

Props strangerstudios, jorbin, desrosj, joemcgill, timothyblynjacobs, ocean90, ayeshrajans, davidbaumwald, earnjam.
See #48900, #50434.
Fixes #50413.

1 edited


  • trunk/src/wp-includes/formatting.php

    r48109 r48121  
    20492049    /*
    20502050     * Loop over any intermediate extensions. Postfix them with a trailing underscore
    2051      * if they are a 2 - 5 character long alpha string not in the extension whitelist.
     2051     * if they are a 2 - 5 character long alpha string not in the allowed extension list.
    20522052     */
    20532053    foreach ( (array) $parts as $part ) {
    48544854        case 'moderation_keys':
    4855         case 'blacklist_keys':
     4855        case 'blocklist_keys':
    48564856            $value = $wpdb->strip_invalid_text_for_column( $wpdb->options, 'option_value', $value );
    48574857            if ( is_wp_error( $value ) ) {
Note: See TracChangeset for help on using the changeset viewer.