3e704473e7
When querying for terms in hierarchical categories using `hide_empty=true`, results have historically included parent terms which are themselves unattached to any objects (are "empty") but which have non-empty descendent terms. Because this process involves walking the descendant tree, we avoid it when we detect that the queried taxonomies are not hierarchical. (This behavior was introduced in [5525].) When the `taxonomy` parameter of `get_terms()` was made optional - see #35495, [36614] - it affected the mechanism for avoiding unneccessary tree walks, since there may not be any explicitly declared taxonomies to run through `is_taxonomy_hierarchical()`. As a result, term queries excluding `taxonomy` did not check descendants, and empty parents with non-empty children were not included in `hide_empty` results. We correct the behavior by crawling term descendants when the `taxonomy` argument is absent, which means that we're querying for terms in all taxonomies. Props smerriman. Fixes #37728. git-svn-id: https://develop.svn.wordpress.org/trunk@45888 602fd350-edb4-49c9-b593-d223f7449a82 |
||
|---|---|---|
| src | ||
| tests | ||
| tools | ||
| .editorconfig | ||
| .env | ||
| .gitignore | ||
| .jshintrc | ||
| .npmrc | ||
| .nvmrc | ||
| .travis.yml | ||
| appveyor.yml | ||
| composer.json | ||
| composer.lock | ||
| docker-compose.yml | ||
| Gruntfile.js | ||
| jsdoc.conf.json | ||
| package-lock.json | ||
| package.json | ||
| phpcs.xml.dist | ||
| phpunit.xml.dist | ||
| README.md | ||
| webpack.config.js | ||
| wp-cli.yml | ||
| wp-config-sample.php | ||
| wp-tests-config-sample.php | ||
WordPress
Welcome to the WordPress development repository! Please check out our contributor handbook for information about how to open bug reports, contribute patches, test, documention, or get involved in any way you can.
Getting Started
WordPress is a PHP/MySQL-based project. We have a basic development environment that you can quickly get up and running with a few commands. First off, you will need to download and install Docker, if you don't have it already. After that, there are a few commands to run:
Development Environment Commands
Running these commands will start the development environment:
npm install
npm run build:dev
npm run env:start
npm run env:install
Additionally, npm run env:stop will stop the environment.
npm run env:cli runs the WP-CLI tool. WP-CLI has a lot of useful commands you can use to work on your WordPress site. Where the documentation mentions running wp, run npm run env:cli instead. For example, npm run env:cli help.
npm run test:php and npm run test:e2e run the PHP and E2E test suites, respectively.