@timkaye do we have time to recreate UnitTests? I am not skilled with them and learning them might take time for me. If we do have someone who can do that and then we can brute force it and add tests to it, I think I can help Sean to work on the errors that come up?
I’m afraid I have no expertise with unit tests at all. That’s been Matt’s and Simone’s domain, though I think @citrika is learning how they work.
Could we copy or export the unit tests first, then add them back afterwards?
At one time Matt did post a quick outline of how to set up unit tests locally (which I cannot find now), but it still required running them manually and was a bit clunky (compared to setting up coding standards).
Slightly off-topic, but in my country (NL) WooCommerce is almost useless without a payment method called iDeal. This (and other popular payment methods) are added to the site with plugins such as this one.
I installed it, but it simply doesn’t work. At first I thought changing the plugin headers would solve this, but there are more references to WC in the code base (to complicated for me).
So if CC 2.0 officially becomes available, the next step should be to somehow make popular payment plugins compatible.
@Guido07111975 try installing CC Compatibility for Woo Addons. Seems that Mollie Payments for WooCommerce works with the compatibility plugin installed.
Yes, there may be some edge cases where the compatibilty plugin is needed. I ran into one myself. It depends on how the add on checks if WooCommerce is enabled.
I will send Sean a pm because I’m running into a problem but I’m not certain it’s caused by CC or the Mollie plugin.
Update available with a few minor fixes v2.0.4
7 Likes
Great, will download and test it later this week.
The Mollie plugin (as mentioned in a previous reply) did not work properly in last version (order did not send), but I will continue to troubleshoot that.
I see that the official version on Github is still the older version. Is there a plan to merge this with the official one on GH?
That’s the plan. It seems there are some hurtles to deal with, so it’s going to take some time.
1 Like
Downloaded and gonna test it now on the development site of my client 
cu, w0lf.
It has been about 6 months since the first post about this new version of CC.
Is already decided if this v2 will replace v1 in the repository? And when?
v2.0.6 available.
Fixed bug in password reset.
3 Likes
Will try it soon!
Already plans to host the plugin at GitHub? This way it can become the official ClassicCommerce and listed at the CP Directory.
That may happen eventually. The issue is that I would need to document all the changes made, which I didn’t do as I was working on it. It took months of free time as it is without taking the time to record everything.
The other option might be to rename it and submit it as a fork, but I don’t think It should be named anything other than Classic Commerce, and I’m not sure I would be able to keep all the links to the documentation on classiccommerce.cc.
I haven’t had time to work on this as of late either. I’m running it on a few websites I manage. If an issue pops up, which have been few and far between, I fix it and put out an update. For now, it’s easy enough to update it via upload. Lots of plugins are like that.
2 Likes
I think forking it could be a solution. It might mean also copying over the CC website - but that might be a good thing all in all. A rebrand could do that plugin (and CP) some good by showing that the ecosystem is growing and encouraging people to come to CP. Also by rebranding and taking it over you could monetize by selling e-commerce services and extensions geared to CP. In the long run this would make your efforts profitable and I see it also as being recognized by the community for all the good work you put in to maintain it.
I think we should make it an official CP plugin and list it as (major) version 2 at the Plugin Directory. This way the plugin is hosted at GH and all can submit Issues and PRs.
I did install it a couple of times last year and it works fine. I don’t think a missing changelog is that important, as long as it still works as expected. Current one in the directory is ancient, so a replacement would be good.
But in order to do this someone with access to the current CC needs to help. Maybe @Simone?
1 Like
Correct, a “version 1” also doesn’t have a changelog as such, it just lists features.