d29ead0e63
In preparation for PHP 7.3, this commit makes the regular expressions used in Emogrifier compatible with PCRE2. It was necessary to escape hyphens used in a few regular expressions. Since the changes were simple and I'm not familiar enough with Emogrifier, I opted to backport the changes that they made in preparation for PHP 7.3 (https://github.com/MyIntervals/emogrifier/pull/588 and https://github.com/MyIntervals/emogrifier/issues/587) instead of updating the library to the yet to be released version 2.1.0. This change removes the following warning when running WC unit tests using PHP 7.3: PHP Warning: preg_replace(): Compilation failed: invalid range in character class at offset 39 in includes/libraries/class-emogrifier.php on line 1504 For more information about the PCRE2 change in PHP 7.3 see the section "PCRE to PCRE2 migration" in the link https://ayesh.me/Upgrade-PHP-7.3 |
||
|---|---|---|
| .github | ||
| .wordpress-org | ||
| apigen | ||
| assets | ||
| i18n | ||
| includes | ||
| sample-data | ||
| templates | ||
| tests | ||
| .babelrc | ||
| .codeclimate.yml | ||
| .codecov.yml | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitattributes | ||
| .gitignore | ||
| .jshintrc | ||
| .scrutinizer.yml | ||
| .stylelintrc | ||
| .travis.yml | ||
| CHANGELOG.txt | ||
| CODE_OF_CONDUCT.md | ||
| Gruntfile.js | ||
| README.md | ||
| apigen.neon | ||
| composer.json | ||
| composer.lock | ||
| license.txt | ||
| package-lock.json | ||
| package.json | ||
| phpcs.xml | ||
| phpunit.xml | ||
| readme.txt | ||
| renovate.json | ||
| uninstall.php | ||
| 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
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:
- The WooCommerce premium support portal for customers who have purchased themes or extensions.
- Our community forum on wp.org which is available for all WooCommerce users.
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.
Contributing new features to the WooCommerce REST API
If you'd like to add a feature to the next version of the REST API, contribute here: https://github.com/woocommerce/wc-api-dev