Vivid/Community Store - client requires a calendar entry on order for dated pre-orders, help!
Permalink
As per title, my client requires a calendar functionality on orders being placed, this is a butcher's service that wants to take dated pre-orders for Christmas.
Currently using Vivid store, but more than happy to jump ship to the github community store if required, however as Vivid is in place would help out time wise to keep on it.
Thank you for any assistance you can provide!
Currently using Vivid store, but more than happy to jump ship to the github community store if required, however as Vivid is in place would help out time wise to keep on it.
Thank you for any assistance you can provide!
Its worth moving to community store ASAP. Vivid store is unsupported. All the new development is on community store.
Hi John,
Understood, to be honest I only just found out about it today! Have been using Vivid for projects for a while (have a lazy load js and css boilerplate rigged up for it for rolling out installs).
That said, would there be any assistance you could provide upon the CS, perchance?
Thanks.
Understood, to be honest I only just found out about it today! Have been using Vivid for projects for a while (have a lazy load js and css boilerplate rigged up for it for rolling out installs).
That said, would there be any assistance you could provide upon the CS, perchance?
Thanks.
Not in time for XMAS I am afraid.
Looking at your requirement, I would guess adding a date attribute to the product could be a starting point. But that is just a quick guess.
John, just given that a go, however, appears to only apply to adding a new product admin side, not towards client facing side.
Thanks again.
Thanks again.
Are there product option or choice attributes, like on the old 5.6 eCommerce?
Yes you can add attributes to product entry, the usual fare - text, textarea, checkbox, date/time and what not.
I've actually only a day or so ago finished up developing a new feature for Community Store where there are additional ways for customers to enter in product options (beyond the existing select options).
This hasn't been merged into the master yet, but it's sitting in github as a pull request: https://github.com/concrete5-community-store/community_store/pull/11...
It's functionally complete, but it hasn't been heavily tested at this point.
The feature adds in being able to add text fields, text area fields, and hidden fields to a product. A good example of use might be 'Message on card', if you are selling something like a gift card, or 'Special requirements' if you're selling something like a ticket to an event.
What I also included with the feature is the ability to have a 'handle' with each field. This is really just a way to associate a custom class with an option, something you'd really use programatically.
In the case you've described it should be possible to create a custom Product block template that applies a datepicker to text field that has a specified handle/class associated with it. I imagine it might be a case of actually limiting the date picker programatically to the current season.
I'd like to test and merge this change soon-ish, but I can't say for certain when that will be - potentially next week.
This hasn't been merged into the master yet, but it's sitting in github as a pull request: https://github.com/concrete5-community-store/community_store/pull/11...
It's functionally complete, but it hasn't been heavily tested at this point.
The feature adds in being able to add text fields, text area fields, and hidden fields to a product. A good example of use might be 'Message on card', if you are selling something like a gift card, or 'Special requirements' if you're selling something like a ticket to an event.
What I also included with the feature is the ability to have a 'handle' with each field. This is really just a way to associate a custom class with an option, something you'd really use programatically.
In the case you've described it should be possible to create a custom Product block template that applies a datepicker to text field that has a specified handle/class associated with it. I imagine it might be a case of actually limiting the date picker programatically to the current season.
I'd like to test and merge this change soon-ish, but I can't say for certain when that will be - potentially next week.
This sounds perfect, as a front end guy with basic PHP skills, however, I feel I may need further assistance in manipulating said function in to the package. My client's budget should be able to cover this if it is required.
Am installing a fresh C5 and CS on my dev server to start diving in.
Thank you for the heads-up, please keep me in the loop!
Am installing a fresh C5 and CS on my dev server to start diving in.
Thank you for the heads-up, please keep me in the loop!
Hi Ryan,
Any further news on the status of this update? I have perused the GitHub since latest push, but I am guessing that no merge was made for the desired functionality tweaks as of yet?
Thank you once again for the heads up.
Any further news on the status of this update? I have perused the GitHub since latest push, but I am guessing that no merge was made for the desired functionality tweaks as of yet?
Thank you once again for the heads up.
I've been working on another feature that I was planning to merge in at the same time as the product option fields PR, but that's taken me longer than I realised!
So I've merged in the pull request for the feature, you should find that now in the master branch.
I have briefly tested it again and fixed a bug already, but it certainly would benefit from further testing.
So I've merged in the pull request for the feature, you should find that now in the master branch.
I have briefly tested it again and fixed a bug already, but it certainly would benefit from further testing.
Hi Ryan,
Have the newest C.S. installed on a fresh C5 install locally, been playing with everything - so far no issues and a really robust package, a breath of fresh air after the Vivid Store, so initially, thank you for your efforts there!
Have dived into the code and fiddled some with a replication of the checkout.php Single Page where 'Delivery Instructions' which under sits '$form->textarea('store-checkout-shipping-instructions', h($shippingInstructions))'. I know you've said previously about modifying another attribute that is called in to handle my desired functionality, however, was wonder if it were possibly easier to modify the above to handle a simple data picker? At this point I don't think validation is priority, i.e. making sure that there is only a certain date range and what have you.
Any hints or tips would be absolutely amazing, if you could spare any time - as before, I am more than happy to put forward some of the clients budget for this functionality, too.
Best
Have the newest C.S. installed on a fresh C5 install locally, been playing with everything - so far no issues and a really robust package, a breath of fresh air after the Vivid Store, so initially, thank you for your efforts there!
Have dived into the code and fiddled some with a replication of the checkout.php Single Page where 'Delivery Instructions' which under sits '$form->textarea('store-checkout-shipping-instructions', h($shippingInstructions))'. I know you've said previously about modifying another attribute that is called in to handle my desired functionality, however, was wonder if it were possibly easier to modify the above to handle a simple data picker? At this point I don't think validation is priority, i.e. making sure that there is only a certain date range and what have you.
Any hints or tips would be absolutely amazing, if you could spare any time - as before, I am more than happy to put forward some of the clients budget for this functionality, too.
Best
