You set the availability start date in the future. So you don't want to show that product. That's why you receive this error. Field "Available start date" is used to set the first day when the product should appear on your store.
It requires a little customization. First of all you should limit the date picker. Because the trip starts from i.e Monday, so users should not be able to reserve another days of week. Then each trip should be a independent product. Of course it's possible to extend the reservation functionality, but it should be done with a plugin.
I found the issue, which was not an issue actually. If you are using the Available start/end date fields in your GrandNode store and you are able to see the products on category pages, please remember to disable the "Ignore "filtering start and end date available products" (sitewide)". We are highly focused on GrandNode performance, mentioned fields are mostly unused by users, so we decided to ignore them by default, to improve the category pages performance out of the box in bigger stores.
Yeah, I know that. I meant what should I do, to get the same thing on my test environment. Because as you can check on our demo, http://demo.grandnode.com I'm able to create reservation product, then assign it to category and view it from category page. That's why I'm asking.
What should I do to reproduce the issue? Step by step instruction is very appreciated.
We are working on the upgraded developer guides, for now you can check some existing widgets in GrandNode.
That's great! I'm very happy that you solved the problems.
I answered on all of your emails while ago. In the case of support related with paid plugins or themes it's better to reach us at firstname.lastname@example.org during our working hours - Mon - Fri - 7:30 am - 3:30 pm CEST.
Thanks for explanation. I understand it now.
To be honest, the most easiest way to handle it, if you don't want to publish it globally, is to create a simple widget, which changes what you want. Without changing the application core.
You can always make that change in the core and create the pull request, if it will be ok, we will with pleasure add it to the project, without problems.
I saw that it's visible on the home page. Did you solve the problem?