The documentation page for this says that it's for v1 of Tea commerce and to go to the documentation portal for documentation for version 2. However that just seems to document the API.
I'm just trying to add a simple shop to an existing website. Is there any getting started documentation for version 2.
You should install the Tea Commerce starter kit and steal whatever you need from that. It's a fully functional e-commerce site with most of what you will need. Then if you need some more advanced stuff you can find it on the documentation site. Any questions you can trow at us here at the forum.
This seems to fire the afterAddOrUpdateOrderLine method I've taken from the starter kit. However the parameter jQForm is null. Is this parameter not passed when the order is updated using javascript.
Sorry to hear about the server form. Kill that if you can! Most of the time the server form is only used on specific pages. Maybe you can add the server for on the few templates it's required and then remove it from everywhere else. Would make your life so much easier!
When you use the JavaScript API there will be no form. The form is sent when using the html API and the ajaxForm class.
It is expected that when you are using the JavaScript API you have a click event or something added to a specific element and therefore already have the DOM in play.
We have a couple of user control macros across all the pages on our site so killing the server form isn't an option.
On a slightly off topic note, can I ask you to elaborate on how getting rid of the server form makes life easier. Do you mean umbraco development in general or when using tea commerce.
We have been working with Umbraco for quite a few years up till now. We startet out doing user control macros and thought it was great. At one point we stopped using them and startet using normal xslt/razor macros working with Umbraco base and JavaScript. Now we can do form posts, ajax and nice and clean HTML without viewstate, ascx files and other ASP.NET nastyness. :)
Also your server side code can be much cleaner and doing changes to existing serverside code is easier.
I dare not say. It will mostly be my colleague Anders who will be doing the documentation. It won't be in the beginning of the month. I can say that much.
Is there no getting started documentation for v2
The documentation page for this says that it's for v1 of Tea commerce and to go to the documentation portal for documentation for version 2. However that just seems to document the API.
I'm just trying to add a simple shop to an existing website. Is there any getting started documentation for version 2.
Hi Suzub,
You should install the Tea Commerce starter kit and steal whatever you need from that. It's a fully functional e-commerce site with most of what you will need. Then if you need some more advanced stuff you can find it on the documentation site. Any questions you can trow at us here at the forum.
/Rune
I think I was just expecting the package to be like uBlogsy or something and already have macros for product listings etc set up.
I've installed the starter kit though so will start stealing what I need from that.
Turns out I can't steal that much from the starter kit. That uses the HTML api however our site uses a server form :/
I've been trying to use the javascript but have a problem with the afterAddOrUpdateOrderLine method. I call this method to add a product to the cart.
TC.addOrUpdateOrderLine({ productIdentifier: nodeId, quantity: 1, storeId: 1 });This seems to fire the afterAddOrUpdateOrderLine method I've taken from the starter kit. However the parameter jQForm is null. Is this parameter not passed when the order is updated using javascript.
Sorry to hear about the server form. Kill that if you can! Most of the time the server form is only used on specific pages. Maybe you can add the server for on the few templates it's required and then remove it from everywhere else. Would make your life so much easier!
When you use the JavaScript API there will be no form. The form is sent when using the html API and the ajaxForm class.
It is expected that when you are using the JavaScript API you have a click event or something added to a specific element and therefore already have the DOM in play.
/Rune
We have a couple of user control macros across all the pages on our site so killing the server form isn't an option.
On a slightly off topic note, can I ask you to elaborate on how getting rid of the server form makes life easier. Do you mean umbraco development in general or when using tea commerce.
We have been working with Umbraco for quite a few years up till now. We startet out doing user control macros and thought it was great. At one point we stopped using them and startet using normal xslt/razor macros working with Umbraco base and JavaScript. Now we can do form posts, ajax and nice and clean HTML without viewstate, ascx files and other ASP.NET nastyness. :)
Also your server side code can be much cleaner and doing changes to existing serverside code is easier.
Just a few of our experiences.
/Rune
Interesting. I didn't know there was another way of doing things like forms bar user controls or contour ;)
Maybe something to look at in the future.
I've seen a few mentions of the.net api documentation going live in August. Will that be happening early in the month of the latter part?
I dare not say. It will mostly be my colleague Anders who will be doing the documentation. It won't be in the beginning of the month. I can say that much.
/Rune
@suzyb Anders just tweeted this: The #teacommerce JavaScript API is now fully documented bit.ly/19dgWqF#umbraco#ecommerce#easyToLearn
is working on a reply...