Right, and this is already an existing problem specifically for the WooCommerce ecosystem.

The WooCommerce 2.7 release introduced new CRUD classes for all major data operations. This was a huge breaking change, enough that the team eventually decided to release it as version 3.0.0 to make it clearer.

Even sticking with WordPress, there is a lot that needs to be done to successfully upgrade from WooCommerce 2.6 to 2.7/3.0. See this guide for some examples, and that is definitely not an exhaustive list (here’s another more specific issue that can cause breakage during that particular WooCommerce upgrade).

So, as long as WooCommerce remains compatible with WordPress 4.9.x, ClassicPress doesn’t change anything here. A bigger issue for WooCommerce site owners is compatibility between WooCommerce and other plugins.

1 Like

Very good points.

1 Like

But this is a big worry for me, with three or four WooCommerce sites. How can we know that updates in Woocommerce (even in the near future) won’t force WP version 5?

This is currently stopping me form jumping over to CP, much as I’d like to.

1 Like

I’d suggest asking the WooCommerce team (via a GitHub issue) if they are going to keep support for WordPress 4.9.x in new versions, as many people will not be upgrading. If they can do that, then that makes our part much easier.

1 Like

Thanks, I will ask them via a ticket, I don’t know what a GitHub issue is.

However whatever they say may not actually be what happens of course.


2 posts were split to a new topic: WordPress 5.0.2 issues

If someone (cough) was crazy enough to fork WooCommerce, what would this kind of support look like?


I think that would be something we (the committee) would need to clearly define and chat about.

Are you thinking of becoming that crazy person? :slight_smile:

I’ve been thinking of becoming that crazy person for a while now, even before these conversations started.


@parkerj Just to say that you are not alone in this, already heard that from a few persons(myself included) :rofl:

I think it will happen at some point but it could be soon now. At the moment there aren’t any issues in running Woocommerce in ClassicPress.

1 Like

@parkerj the good news is that you have a lot of freedom to undertake this effort as you see fit. The bad news is that we wouldn’t be able to provide much official help or support right now, beyond giving you a place to put the code if you want, and maybe some commiseration mutual learning about all the things that need to be done to successfully fork large projects.

Are you thinking of forking WooCommerce yourself, or under the ClassicPress name?

If the former, well, you don’t need anything from us to get started :wink:

If the latter, we could use the https://github.com/ClassicPress-research organization and create a repository there. This is a semi-official place for experimental plugins that may one day be official recommendations from within the ClassicPress dashboard, or even integrated into the core software (not as likely in this case).

Either way, if you’re able to create and stay on top of a fork of WooCommerce, then kudos to you. And either way, what will ultimately determine the success of the project is whether members of the community choose to use it on their sites.

1 Like

Definitely under the ClassicPress name.


Ok, so I just need your GitHub username (feel free to send me a direct message here, or on Slack or Discord if you don’t want to share it publicly) and the repository name.

Repository name: ClassicCommerce? Something else?

My Github username is parkerj. But before we proceed, should we vote on what the name should be?

At this point the vote would be between “ClassicCommerce” and “something else”.

We can wait a day or two and see if other suggestions and a consensus emerge. It’s also not a big deal to change the repository name, so I wouldn’t worry about this too much until you’re ready to start actually changing the name in the code.

That was the name that immediately came to mind for me.

( “something else” just doesn’t grab me :grin: )


You should consider names that have an available .com domain, it’ll be needed later down the road for sure.

  • Open Commerce Kit
  • Commerce Kite
1 Like

.org is available though

Definitely Aussie humour.

These are what we have so far:

ClassicPress Commerce (.com available)

Commerce Kite (.com available)

Commerce CP (.com available)

Commerce Classic (.com available)

Open Commerce Kite (.com available)

1 Like