What’s the architecture for the ClassicPress Plugin Directory?
I’m planning to built a small store. I will explore Classic Commerce, but I’m not sure other code is compatible, so I’m looking at my options.
The particular issue is that I need to customize each product at or before the sale. One thought is to list the volume as ‘1’ and then reissue the product after customizing.
Any suggestions?
Thanks
The ClassicPress directory was made with ClassicPress - I do think using Custom Post Types.
Classic Commerce being a fork of Woo allows to manage variable products just like Woo does.
As I specified in the other thread, you can use Sean’s version of it that you can find here.
2 Likes
Thank you. The CC 2.0.9 is actually worse than CC 1.0.4 when testing in PSI, and in my opinion. looks better. It has a couple issues, fresh out of the box, but they are DIY fixable.
The newer CC 2.0.9 crops the full images:
The PSI issues with CC 2.0.9 are less transparent.
What are the issues for upgrading or not upgrading?
Thanks!
I have not used Classic Commerce, but in my opinion, the only things that might not work are payment gateways: Stripe, PayPal and so on.
Everything else is the same: custom post types and meta fields. That’s all.
Obviously, there might be bugs, improvements , new features added to the non-payment codebase, and you should test everything.
If you want to stick with 1.0.4, set up a few test products, make them $0.01 and purchase them yourself. If your desired payment gateway works, that’s all that matters.
1 Like
Thanks!
And double thanks for catching the CSS post. What I mistook for style.css was my notes for “Headers and Footers” snippets. Not the same!
1 Like
As I stated, Sean’s version is slightly more secure - but both have issues.
What I found in my Classic Store fork is that the payment system needs to be refactored, that many libraries are at a very old version and a system needs to be setup so that they upgrade via renovatebots (that is a GH action specifically made to run when a new version of the library exist to upgrade the bundled ones in a software). Also Classic Store (that is for now a soft fork of a previous version of Sean’s CC) will need a better shipping management, a template overhaul for products and archive pages and if I can get to it a better system to manage free checkout/discounts/product variations etc.
To do all this I am really taking the time to STUDY the code because it’s an e-commerce system, basically something that people are going to use to manage sales and receive money. I am not confident in refactoring it blindly without prior understanding.
1 Like
Woo commerce was forked from Jigoshop if that help any.
Thanks for your patience. I left the Press world almost ten years ago because I wanted faster pages and I could do what I needed by hand. I’m returning, in part, because of the excellent work at ClassicPress.
WP was a fork of B2 cafelog when it started… 
Aside from that I stated it’s a fork of Woo so that you could understand its capabilities. I know as of now it’s not au par with the standards needed for e-commerce. but I really hope to be able to bring it up to speed, even with my limited skills.
That said I agree CP community is doing amazing things.
1 Like