c83253c7f8
When an attempt is made to update an active plugin automatically, there is the potential currently for two negative scenarios: - The plugin can be deactivated if the Plugins admin screen is loaded when the plugin update is incomplete, causing a PHP error. - The WSOD protection could be triggered, sending a false alarm email to the site administrator. By enabling maintenance mode before an active plugin update is attempted, these scenarios can be avoided. This change implements the same approach as the `Theme_Upgrader` class of using the `upgrader_pre_install` and `upgrader_post_install` hooks to toggle maintenance mode. Props desrosj, SergeyBiryukov. Fixes #49400. git-svn-id: https://develop.svn.wordpress.org/trunk@47275 602fd350-edb4-49c9-b593-d223f7449a82
WordPress
Welcome to the WordPress development repository! Please check out our contributor handbook for information about how to open bug reports, contribute patches, test, documentation, 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.