Woocommerce fork


#1

Will the woocommerce fork or ClassicCommerce soon see the light of day?


#2

I’m not sure “soon” is quite the right word. I think we have decided on the logo, but there was still some debate about the font. :slightly_smiling_face:

But I’m running one Woocommerce site with CP and it’s doing fine so far. I’m not really expecting any issues with CP version 1.


#3

It works with me on classicpress
There was only information that woocommerc will not support ClassicPress in the future.
What if the woocommerc was adapting to Gutenberg more and more


#4

I guess it all depends how long they keep backward-compatibility to WP4.9 - as long as they do that we should be fine.


#5

I think @parkerj is working on a fork for ClassicPress called ClassicCommerce, but I don’t know the exact status of this project.


#6

That is correct. The status is that I am currently doing some clean up. A holding area for it was created a couple of months ago: https://github.com/ClassicPress-research/classic-commerce


#7

@parkerj can we get access to the latest cleaned up version please?

I’m working on some themes strictly for ClassicPress and would like to create one for eCommerce and don’t fancy starting with WooCommerce to then have to switch over…I’m going to be doing some deep integrations so would rather work in the forward thinking framework than rely on back-compat :slight_smile:


#8

When it is ready, I will let you know.


#9

Please tell me this is a joke, and that implementation is not being held up because of disagreement about a font.


#10

Code can be written whether or not fonts/graphics/logos are complete. I don’t see any issue here.


#11

It was a joke.

[Sorry… I’m an Australian. I can’t help it.]


#12

This is the only discussion I have been part of…

I can’t help with code, so it’s really good to know that you are working away at it, @parkerj. If you need anything tested when you get closer let me know. I have one site with Woocommerce and I can set up a copy to try it with ClassicCommerce.


#13

@parkerj Thank you so much for taking this on!


#14

@parkerj, is there a todo list for CC somewhere?


#15

The worry for me is it so much the fork of Woocommerce which i’m Sure will be great and i’d be happy to help by donating, but my main concern will be the (for me)necessary extensions plugins eg Stripe, mailchimp, name your price etc.


#16

@MrLucky if any of those extensions are GPL then they can forked too. If not then I’m sure there will be plenty of plugin developer waiting to fill the gap :slight_smile:


#17

I’m sure they can be, but will they be?


#18

I’m a themer first and foremost but I’m not afraid of delving into plugins if I need to. So, if there is need in the community and no one is filling that gap I’ll be more than happy to jump in to get us a solution :slight_smile:


#19

Personally, I would not worry. The APIs in ClassicCommerce will still be available and these are what devs depend on to extend the plugin. We can always work on extensions if the ones being used are broken. However, I don’t see how payment gateways have to engage in Gutenberg development for now at least. So I am sure they will work fine.


#20

How can we help? A Repo we can send some PRs to a todo list could be of help. WC is a large project. :slight_smile: