ticket Milestone type summary workflow component version severity priority modified _description 26195 new enhancement Deleting users asks for reassigning posts even when there is no post/comment dev-feedback Users 3.7.1 normal normal 2019-06-05T06:39:36Z "When deleting a single user or bulk deleting users, the confirmation page asks what should be done with the posts of the user. However, this question should not be displayed, if the sum of the posts of these user(s) is 0. Then, the delete button should become immediately active. This change would make deletion safer, as ""real"" users would be less likely to be deleted in error. Recommended user interface: - No posts present: ""This user/these users have no post"", followed by an active ""delete users"" button - Posts present: ""This user/theses users have a total of [number] posts"", followed by the current delete/assign query. " 39639 Awaiting Review new enhancement Increase cache time on wp_get_available_translations() needs-patch I18N 4.8 normal normal 2017-01-19T20:11:20Z "Currently there's no nice way of retrieving a full list of supported languages / locale codes from WordPress. The closest seems to be: {{{ require_once( ABSPATH . 'wp-admin/includes/translation-install.php' ); $languages = wp_get_available_translations(); }}} This calls the WordPress.org API to retrieve the list, making this approach not wholly suitable outside of its original intended use during WordPress install. The results are currently cached for 3 hours so it's not that the API will be called every time this function is called, however it seems that the 3 hours could be extended reasonably safely without causing any detriment. Patch attached that extends the cache time to 24hrs. " 28618 Future new enhancement Allow PHPMailer class to be reliably overriden has-patch Mail 4.0 normal normal 2020-10-08T11:43:22Z "The WordPress unit test suite currently overrides the global $phpmailer variable with its own MockMailer class. (See https://core.trac.wordpress.org/browser/trunk/tests/phpunit/includes/bootstrap.php#L48) This achieves the desired effect, but is potentially unreliable. If the global $phpmailer object gets unset, or overridden (For example by a buggy, or otherwise badly behaving plugin), then the code in wp-includes/pluggable.php will create a new instance of PHPMailer without any way for code to override that - see https://core.trac.wordpress.org/browser/trunk/src/wp-includes/pluggable.php#L264 The end result would be that a site that shouldn't be sending emails will potentially become one that will. Potential patch attached. This includes the change to pluggable.php to filter the object after creation, and addition to the test suite to use it. " 25840 Future new enhancement Feature Request: WP_ACCESSIBLE_HOSTS as option needs-testing HTTP API 3.7.1 normal normal 2020-09-16T17:40:10Z "Currently WP_ACCESSIBLE_HOSTS is defined as a constant. It would be great if this is a wordpress option (or something equivalent) so you can change it at runtime. If you have a multisite installation and need to add domains to the whitelist you must reload the whole installation to enable them. Writing a simple plugin for this is also not possible since constants can not be redefined. My suggestion: 1) Store a site_option for mutlisites. This should contain a general whitelist for all blogs 2) Store a option per blog to contain additional whitelists for this single blog 3) Make it configurable via the admin interface (single textbox to enter the domains) 4) In the block_request function (https://github.com/WordPress/WordPress/blob/master/wp-includes/class-http.php#L507) the 2 options should be merged and handled like the constant This way you could manage the whitelist at runtime. What do you think about this? Chris"