23a605c14c
This includes the following: - Fix the "upshifting" that was implemented in 36218 so that it only applies when the post type of the order being deleted is hierarchical (this conforms to the WordPress behavior when deleting a post). - Now when an order is deleted while sync is off a record will be created in wp_wc_orders_meta (regardless of which table is the authoritative one) with 'deleted_from' as the key and the authoritative table name (from where the order has been deleted) as the value... - ...then DataSynchronizer will detect the presence of these 'deleted_from' records and delete them from the backup table as part of the batch processing procedure. - Exception to the above: when an order is deleted from the orders table and the corresponding records in the posts table are placeholders, these are deleted immediately too, even if sync is off. - Add an "order_exists" method in both order data stores (Abstract_WC_Order_Data_Store_CPT and OrdersTableDataStore). - Add a pair of get/set_verify_parent_id methods in WC_Abstract_Order (turning off the check in set_parent_id is necessary when deleting an order using the backup data store during synchronization). - Placeholder records are now created with the appropriate parent id for child orders (e.g. refund), this is necessary in order to properly find which records need to be deleted. |
||
|---|---|---|
| .github | ||
| .husky | ||
| bin | ||
| packages | ||
| plugins | ||
| tools | ||
| .codecov.yml | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierrc.js | ||
| .stylelintrc | ||
| .syncpackrc | ||
| CODEOWNERS | ||
| CODE_OF_CONDUCT.md | ||
| DEVELOPMENT.md | ||
| README.md | ||
| SECURITY.md | ||
| changelog.txt | ||
| package.json | ||
| phpcs.xml | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| renovate.json | ||
| tsconfig.base.json | ||
| turbo.json | ||
README.md
Welcome to the WooCommerce Monorepo on GitHub. Here you can find all of the plugins, packages, and tools used in the development of the core WooCommerce plugin as well as WooCommerce extensions. You can browse the source, look at open issues, contribute code, and keep tracking of ongoing development.
We recommend all developers to follow the WooCommerce development blog to stay up to date about everything happening in the project. You can also follow @DevelopWC on Twitter for the latest development updates.
Getting Started
To get up and running within the WooCommerce Monorepo, you will need to make sure that you have installed all of the prerequisites.
Prerequisites
- NVM: While you can always install Node through other means, we recommend using NVM to ensure you're aligned with the version used by our development teams. Our repository contains an
.nvmrcfile which helps ensure you are using the correct version of Node. - PNPM: Our repository utilizes PNPM to manage project dependencies and run various scripts involved in building and testing projects.
- PHP 7.2+: WooCommerce Core currently features a minimum PHP version of 7.2. It is also needed to run Composer and various project build scripts.
- Composer: We use Composer to manage all of the dependencies for PHP packages and plugins.
Once you've installed all of the prerequisites, you can run the following commands to get everything working.
# Ensure that you're using the correct version of Node
nvm use
# Install the PHP and Composer dependencies for all of the plugins, packages, and tools
pnpm install
# Build all of the plugins, packages, and tools in the monorepo
pnpm run build
At this point you are now ready to begin developing and testing. All of the build outputs are cached running pnpm run build again will only build the plugins, packages, and tools that have changed since the last time you ran the command.
Check out our development guide if you would like a more comprehensive look at working in our repository.
Repository Structure
- Plugins: Our repository contains plugins that relate to or otherwise aid in the development of WooCommerce.
- WooCommerce Core: The core WooCommerce plugin is available in the plugins directory.
- Packages: Contained within the packages directory are all of the PHP and JavaScript provided for the community. Some of these are internal dependencies and are marked with an
internal-prefix. - Tools: We also have a growing number of tools within our repository. Many of these are intended to be utilities and scripts for use in the monorepo, but, this directory may also contain external tools.
Reporting Security Issues
To disclose a security issue to our team, please submit a report via HackerOne here.
Support
This repository is not suitable for support. Please don't use our issue tracker for support requests, but for core WooCommerce issues only. Support can take place through the appropriate channels:
- If you have a problem, you may want to start with the self help guide.
- The WooCommerce.com premium support portal for customers who have purchased themes or extensions.
- Our community forum on wp.org which is available for all WooCommerce users.
- The Official WooCommerce Facebook Group.
- For customizations, you may want to check our list of WooExperts or Codeable.
NOTE: Unfortunately, we are unable to honor support requests in issues on this repository; as a result, any requests submitted in this manner will be closed.
Community
For peer to peer support, real-time announcements, and office hours, please join our slack community!
Contributing to WooCommerce
If you have a patch or have stumbled upon an issue with WooCommerce core, you can contribute this back to the code. Please read our contributor guidelines for more information on how you can do this.