Did PortlandLabs ever port their ecommerce addon to 5.7?
Permalink
But its not released, we have started using this packae on our projects. Its working perfect, better than Vivid Store (Vivid store is full of bugs and it seems they are not providing support)
You can download it from herehttps://github.com/concrete5-community-store...
Contact me if you are having any issue with this package (When using composer), Please also report the issues you are facing.
Also see :
https://www.concrete5.org/community/forums/customizing_c5/community-...
AND
https://www.concrete5.org/community/forums/customizing_c5/ionicanjul...
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.
It's purely an open source project, something maintained by the community.
When i click on products or any store package single page:
The class 'Concrete\Package\CommunityStore\Src\CommunityStore\Group\Group' was not found in the chain configured namespaces Concrete\Core, Application\Src
Or only in the future?
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.
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 :)
https://github.com/concrete5-community-store/community_store/issues/...
Use the Vivid Store package. It's been updated recently, and I've never had any problems.
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).
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
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.
Lack of input data validation is a recurring problem with submissions to the PRB. Its easy to solve, but often neglected.
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".
Edit: or charge for the add on and release non destructive updates.
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.
Edit: Sorry I just realized you asked Mesuva and Vivid this question not me, lol. But theres my answer anyways. Thanks.