That ecommerce solution has not been ported, the onlty store add-on at this time is the vivid store -https://www.concrete5.org/marketplace/addons/store-ecommerce-from-vi...

Is that officially endorsed by C5 Portland Labs? ( that was kind of my main question)

Also, this looks really great so I will be using this on store I'm building now. Will let you know if theres any trouble. I've used Vivid store in the past but didn't want to use it again as I can confirm it needs work. I didn't want to build a Magento site for the type of store this customer wants, so I'm really glad to find out about this.

Oh, and to answer your question about it be 'official endorsed by Portland Labs', the answer to this is no - they're not anything to do with it.

It's purely an open source project, something maintained by the community.

This works fine in C5.8?....I get some errors -
When i click on products or any store package single page:


Or only in the future?

A few weeks back I did spend some time addressing quite a few V8 incompatibilities. Andrew also has kindly been looking at the package to work out what are backwards compatibility issues on the v8 side of things. It got it working pretty much, it was really just the fieldless forms that provided a challenge.

But I haven't done any testing under v8 more recently, so I'm not surprised there are a few errors. I wouldn't think there'd be many though. Detailed bug reports (or fixes) on github are always appreciated.

OK. I will add this error to github.

Not related - it could be great to add some "DEMO" page (Even without any CSS design - deafult html styles). I really want to know how you control "categories" in this package.

Do you have live site example you use this package? Thanks :)

I'm getting alot of SQL errors:
https://github.com/concrete5-community-store/community_store/issues/...

Community Store is unstable, and I've had a number of issues with it.

Use the Vivid Store package. It's been updated recently, and I've never had any problems.

What issues have you had with it? I've not seen any bug reports from yourself on github.
We're running a few shops in production with it - perhaps you are thinking back to with it was under much heavier development?

The issue about with the SQL errors is something I'll resolve, but I believe they're related to running MySQL in strict mode (which I _think_ is not a typical setting).

SQL reports are for community store. The problem I had with vivid store was functionality, where we had to manually add a product block to the product page to get the product info to show up, and I need that done automatically for our clients.

Yesterday I switched MySQL over to strict mode and went through Community Store, addressing the errors you listed, plus a couple of others. So those errors have been resolved.

So I need to change the mySQL settings for it to work?

No, just download the latest master from github.

Awesome, glad its working now, and I can confirm its working great, the development must be solid behind this.

I'm getting new SQL errors, now when I try to save the settings:

An exception occurred while executing 'UPDATE CommunityStorePaymentMethods SET pmButtonLabel = ?, pmSortOrder = ? WHERE pmID = ?' with params ["", "", 2]: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'pmSortOrder' at row 1

Still getting this error:

An exception occurred while executing 'UPDATE CommunityStorePaymentMethods SET pmButtonLabel = ?, pmSortOrder = ? WHERE pmID = ?' with params ["", "", 2]: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'pmSortOrder' at row 1

Any time I try to save dashboard settings.

Sorry, I fixed pmSortOrder SQL error in a branch I'm working on and hadn't pushed it to master. That should be there now, plus some other fixes to do with strict mode.

How do I install Stripe payments?

The Stripe add-on requires composer, so you need to download it from github (https://github.com/concrete5-community-store/community_store_stripe), unzip it to your packages directory (make sure the folder is just named community_store_stripe) , run composer on the package, _then_ install it via the dashboard.

Got it

As a generalisation, developers should keep the MySQL on their development systems set to strict. They will discover many kinds of bug to do with input data validation and storage before the code gets to anyone else.

Lack of input data validation is a recurring problem with submissions to the PRB. Its easy to solve, but often neglected.

I use concrete5 for a year and never heard about this project (And really need e-commence solution). Thanks!

I think it could be great to add some "demo page" for this (And some "SEO" aspect). Open source -- > more users --> better product. Even if this package is not for "editors".

Since our most recent updates, vivid store is pretty stable. We provide support for support tickets, which are paid.

Do the product pages automatically populate now or do we still have to add a product block to the page manually? I do recall you have some really useful and well made plugins though.

Maybe you should reply to members' concerns with this in the support forum instead of leaving them hanging.

Edit: or charge for the add on and release non destructive updates.

Could you @mesuva and @Vivid comment on the differences between Community Store and Vivid Store at the moment? What were the original reasons for the Community Store fork and how do the features differ? Are both being developed further as individual products or are you sharing code back/forth between these projects?

Many of the feature differences between the two stores are quite subtle (and to be honest I'm not up to speed myself on the features of more recent versions of Vivid Store).

But the more significant differences I think would be:

- Community Store defaults to use Bootstrap based styling, blocks and single pages have bootstrap classes on them, whereas Vivid Store includes its own styling for such items. Items like the cart look quite different because of this.
- Shipping methods and discounts are handled differently
- Community Store has separate indicators on an order for payment and fulfilment
- Order and receipt emails are styled differently, with different options for email header and footer content
- And probably the main difference is that Vivid Store is on the concrete5 marketplace, while Community Store will only ever be provided via github. It's under a broader organisation that has related add-ons:https://github.com/concrete5-community-store...

More broadly speaking, Community Store is aimed towards developers with more concrete5 experience, for them to use a platform for developing custom shops rather than an install-and-go solution.

The primary reason for Community Store being developed as a separate project was there was a need for more aggressive development without being tied to having to be backwards compatible with the marketplace version.

Both projects are ongoing as separate projects - the codebases are now quite distinct, so although there may be opportunities to share code (and both are MIT), many components won't be directly compatible.

Thanks @mesuva!

Also not being aware of most recent Vivid Store, and becoming a better C5 developer every day, I can say that for my clients the community store is easier for them to manage whether than means adding new products to their website or adding completely new product sections if they so please. The only time I used Vivid store was a while ago and adding a product involved both adding it via the dashboard and adding a product page for it, where community store will build the front end page automatically when you add it to the dashboard. If you have no developer experience Vivid store will probably work great, as our customer is still processing orders with it to this day (although not very many but that has nothing to do with Vivid store, lol).

Edit: Sorry I just realized you asked Mesuva and Vivid this question not me, lol. But theres my answer anyways. Thanks.