Go to file
Andrea Fercia aba005be39 Accessibility: Make sortable meta boxes non sortable when there are no locations they can be dragged to.
Depending on the amount of meta boxes and the layout settings under Screen Options, sortable meta boxes may not be actually sortable.
In these cases, jQuery UI sortable needs to be disabled and the user interface shouldn't use a CSS `cursor: move`.

The use of consistent and relevant cursors may be important for users who have a cognitive disability, since cursors give a visual clue as to an element's functionality. Using the move cursor for elements which cannot be moved may be confusing or counter-intuitive for users.

Props adamsilverstein, antpb, anevins.
Fixes #47131.


git-svn-id: https://develop.svn.wordpress.org/trunk@46250 602fd350-edb4-49c9-b593-d223f7449a82
2019-09-23 17:29:46 +00:00
src Accessibility: Make sortable meta boxes non sortable when there are no locations they can be dragged to. 2019-09-23 17:29:46 +00:00
tests REST API: Pass "null" as the post date property to reset post to initial "floating" date value. 2019-09-23 17:24:58 +00:00
tools Block Editor: Update the WordPress Packages to the ones used in the Gutenberg 6.5 release 2019-09-19 15:17:39 +00:00
.editorconfig
.env Build Tools: Miscellaneous `local-env` improvements. 2019-08-12 08:28:33 +00:00
.gitignore Build Tools: Miscellaneous `local-env` improvements. 2019-08-12 08:28:33 +00:00
.jshintrc Build tools: Fix the `travis:js` build. 2018-12-24 13:53:11 +00:00
.npmrc
.nvmrc
.travis.yml Build/Test Tools: add php info to travis output 2019-09-14 19:27:46 +00:00
Gruntfile.js Accessibility: Replace wp-a11y.js with @wordpress/a11y package 2019-09-18 17:40:35 +00:00
README.md Build Tools: Add a WordPress Development Environment. 2019-08-05 07:09:14 +00:00
appveyor.yml Build/Test Tools: Remove the dependency on a globally installed Grunt. 2019-05-26 19:34:24 +00:00
composer.json Build/Test Tools: Specify PHP 5.6 as the required version of PHP in Composer. 2019-09-20 17:32:23 +00:00
composer.lock Build/Test Tools: Specify PHP 5.6 as the required version of PHP in Composer. 2019-09-20 17:32:23 +00:00
docker-compose.yml Build Tools: Pass the LOCAL_DIR environment variable through to the phpunit Docker container. 2019-08-23 01:55:28 +00:00
jsdoc.conf.json
package-lock.json Block Editor: Update the WordPress Packages to the ones used in the Gutenberg 6.5 release 2019-09-19 15:17:39 +00:00
package.json Block Editor: Update the WordPress Packages to the ones used in the Gutenberg 6.5 release 2019-09-19 15:17:39 +00:00
phpcs.xml.dist Coding Standards: Move the remaining PHPCS errors to report as warnings, and add Travis tests. 2019-07-19 07:47:16 +00:00
phpunit.xml.dist Code Modernization: Remove all code using a `version_compare()` with a PHP version older than PHP 5.6. 2019-09-20 22:01:36 +00:00
webpack.config.js
wp-cli.yml Build/Tests: Default to running unit tests from `src`. 2019-01-09 10:09:02 +00:00
wp-config-sample.php General: Replace "Happy blogging" with "Happy publishing". 2019-01-08 04:29:06 +00:00
wp-tests-config-sample.php Tests: Revert [44509]. 2019-01-09 11:13:03 +00:00

README.md

WordPress

Build Status

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.