44ecb0ec9e
This commit changes the condition in the if the statement that decides whether or not to display the "Paid by customer" section in the order admin page. Before it, this section was displayed for all orders that contained one of the following statuses: 'processing', 'completed' or 'refunded'. The problem with this approach is that offline payment gateways, like 'Cash on Delivery', set the order status to processing when the order is placed but before the customer pays for it. So the "Paid by customer" section was being displayed in some cases where the order was not actually paid yet creating a confusing experience to store managers. To fix this, this commit also checks for the presence of the `_date_paid` order meta. If this order meta is present and the order status corresponds to one of the three statuses listed above, it means that the order has been paid and we can display the "Paid by customer" section. If this order meta is not present, we don't display the "Paid by customer" section. |
||
|---|---|---|
| .github | ||
| .wordpress-org | ||
| assets | ||
| bin | ||
| i18n | ||
| includes | ||
| packages | ||
| sample-data | ||
| src | ||
| templates | ||
| tests | ||
| .codeclimate.yml | ||
| .codecov.yml | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitattributes | ||
| .gitignore | ||
| .jshintrc | ||
| .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 | ||
| 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.