36d1c318cb
This PR introduces a check on the permission_id FK to ensure that it is not added multiple times on upgrades. It also names the key specifically to ensure future changes to the key can be targeted properly and removes old keys that were added since 3.4.0. * Add FK check before adding the FK. Also give the FK a name to avoid auto generated names and duplicate keys. * Remove additional OR * Remove additional OR * Final FK check query * Add foreign key cleanup routine to 3.4.3 db version * Only check on named foreign key now that we have a cleanup routine in place, use specific phpcignore * Rework formatting of SQL query * Change way to fetch and add FK, can't use procedural SQL, needs to be done via statements. * Add table name to lookup * Only clean up FK on the wc_download_log table * Remove erenouse bracket |
||
|---|---|---|
| .github | ||
| .wordpress-org | ||
| apigen | ||
| assets | ||
| i18n | ||
| includes | ||
| sample-data | ||
| templates | ||
| tests | ||
| .babelrc | ||
| .codeclimate.yml | ||
| .codecov.yml | ||
| .editorconfig | ||
| .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 | ||
| 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