A customizable, open-source ecommerce platform built on WordPress. Build any commerce solution you can imagine.
Go to file
Mike Jolley ded4b7404d Admin changes for #5046
- Removed post type classes. Since they were always loaded, there was
no benefit having them split up. Combined meaning less hooked in
methods.
- Stopped loading some function files and sessions in the admin area.
They are not needed there.
- Made a few admin page classes static as they are stateless
2014-06-04 11:16:19 +01:00
apigen Fix apigen search 2014-03-26 09:43:14 +00:00
assets Get rid of anything shop_order_status related 2014-05-30 17:45:11 +01:00
dummy-data Get rid of anything shop_order_status related 2014-05-30 17:45:11 +01:00
i18n Merge branch 'post-statuses-for-orders' 2014-06-04 05:54:15 +01:00
includes Admin changes for #5046 2014-06-04 11:16:19 +01:00
templates Merge branch 'post-statuses-for-orders' 2014-06-04 05:54:15 +01:00
.editorconfig added editorconfig 2013-08-25 16:11:19 -03:00
.gitignore ApiGen + woodocs template + grunt task 2014-02-14 14:29:40 +00:00
CONTRIBUTING.md Updated available customisation services list in contributing docs 2014-02-13 12:20:13 +01:00
Gruntfile.js Remove TX from grunt file #5485 2014-05-29 16:52:56 +01:00
README.md Added Twitter account link to README.md 2014-02-13 12:22:55 +01:00
license.txt Line endings. Closes #1065. 2012-05-26 17:25:07 +01:00
package.json Remove TX from grunt file #5485 2014-05-29 16:52:56 +01:00
readme.txt Explain #3064 in the read me. 2014-06-04 05:59:29 +01:00
uninstall.php Trash in the uninstaller too 2014-02-14 11:22:00 +00:00
woocommerce.php Admin changes for #5046 2014-06-04 11:16:19 +01:00

README.md

WooCommerce - excelling eCommerce

Built with Grunt

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.

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:

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.