089485b3bf
* Add new save_subscription_meta() method to allow us to save customer ID both in Subscriptions 1.n on the original order and in 2.0 on the subscription/s created for the order) * Use the new 'woocommerce_scheduled_subscription_payment_simplify' hook and deprecate use of the old 'scheduled_subscription_payment_simplify' hook by moving it to the WC_Addons_Gateway_Simplify_Commerce_Deprecated class * Use core WC methods on the renewal order passed to scheduled_subscription_payment() to process the payment rather than having to call special Subscriptions API methods like WC_Subscriptions_Manager::process_subscription_payments_on_order() and WC_Subscriptions_Manager::process_subscription_payment_failure_on_order() * Use the original order's total to determine the amount to charge up-front to save having to call WC_Subscriptions_Order::get_total_initial_payment() * Use a description for recurring payments that is consistent with standard orders, i.e. "{Site Name} - Order {order_id}" instead of a description that does not include the renewal order's ID. This helps link payments to orders (which can then be traced to subscription/s). |
||
---|---|---|
apigen | ||
assets | ||
dummy-data | ||
i18n | ||
includes | ||
templates | ||
tests | ||
.coveralls.yml | ||
.editorconfig | ||
.gitignore | ||
.jshintrc | ||
.scrutinizer.yml | ||
.travis.yml | ||
CONTRIBUTING.md | ||
Gruntfile.js | ||
README.md | ||
apigen.neon | ||
license.txt | ||
package.json | ||
phpunit.xml | ||
phpunit.xml.dist | ||
readme.txt | ||
uninstall.php | ||
woocommerce.php |
README.md
WooCommerce
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
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 in the appropriate channels:
- The WooThemes premium support portal for customers who have purchased themes or extensions.
- Our public HelpDesk 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 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.
If you have an idea for WooCommerce, see the Roadmap Trello board.