8a7d955253
- Add methods to temporarily disable and reenable the code hacker. The code hacker is causing issues in some tests that perform write operations to the local filesystem. Since this happens only in a few cases, the easiest fix is to temporarily disable the code hacker when that happens. This commit adds two new methods for that in `WC_Unit_Test_Case`: `disable_code_hacker` and `reenable_code_hacker`. These methods use a disabling requests count so that the hacker isn't enabled before it should. E.g. you call `disable`, then a helper method that does `disable` and `enable`, then `enable` - then only the last `enable` will have effect. - `CodeHacker::add_hack` has now a boolean `persistent` parameter. Persistent hacks won't be cleared by `clear_hacks`. - `CodeHackerTestHook::executeAfterTest` will now disable the hacker only if no persistent hacks are registered. - The existing `file_copy` method is made static for consistency. - `CodeHacker::restore` method renamed to `disable` for clarity. |
||
|---|---|---|
| .github | ||
| .wordpress-org | ||
| assets | ||
| bin | ||
| i18n | ||
| includes | ||
| packages | ||
| sample-data | ||
| src | ||
| templates | ||
| tests | ||
| .codeclimate.yml | ||
| .codecov.yml | ||
| .distignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .scrutinizer.yml | ||
| .stylelintrc | ||
| .travis.yml | ||
| CHANGELOG.txt | ||
| CODE_OF_CONDUCT.md | ||
| Dockerfile | ||
| Gruntfile.js | ||
| README.md | ||
| babel.config.js | ||
| composer.json | ||
| composer.lock | ||
| docker-compose.yaml | ||
| license.txt | ||
| package-lock.json | ||
| package.json | ||
| phpcs.xml | ||
| phpunit.xml | ||
| readme.txt | ||
| renovate.json | ||
| uninstall.php | ||
| webpack.config.js | ||
| woocommerce.php | ||
README.md
Welcome to the WooCommerce repository on GitHub. Here you can browse the source, look at open issues and keep track of 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.
If you are not a developer, please use the WooCommerce plugin page on WordPress.org.
Documentation
- WooCommerce Documentation
- WooCommerce Developer Documentation
- WooCommerce Code Reference
- WooCommerce REST API Docs
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 WooCommerce Help and Share Facebook group.
- For customizations, you may want to check our list of WooExperts or Codeable.
Support requests in issues on this repository will be closed on sight.
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 how you can do this.