Software for building a custom e-commerce ๐ with a great user experience and a quick purchase process. It can be modified in the visual way. Written in Node.js without any dependencies.
Checkout is showed always at login even when shopping cart is void after once we have loged in in advance with something in the shopping cart.
Also When shopping cart is not void and we create a new user checkout page is not showed. Maybe better check if shopping cart is void and forget about that page procedence attribute we use to know what to show at login. (loggedindata or checkout)
It appears only the default users webadmin...systemadmin...are the only ones that can make a purchase, the new account registrar cannot confirm the order or proceed as there is a missing panel to add details name...address...etc...the issue behaves the same on the your demo site ... but shows clearly in your video that this is the process to check out.
I must say I love this App, the demo is fantastic being playing around with it over the weekend, decided to try and install it on my hosted server via cpanel on namecheap, followed instructions to the T but with no luck. Its been populating the database for hours despite the database imported and installed.
Any other way to do this or am i just missing something obvious?
I've noticed that when using html snippets to copy and paste, the page title disappears. Upon refresh a few elements become void and since I'm not a coder I'm not sure where to correct this.
Another option would be to add variants and sizes.
There is a bug in this version at loadRequest("add my tree") execution because it does not load the result. The resulting error is detected just at the add new item process.
At the moment and until we fix it or we update to a new version, this problem can be avoided by closing the new item product and then opening it again at the product listing.
There is an error at the action loadRequest("add my tree") because it doesnt load the id. So after ading some elements they give error when modifying. We are probably not solving the problem for this version but it will be solved at next version. This happens for example when adding a new shipping type.
The issue can be fixed by editing the element for next iteration.