Messages

You need to add $company to the address format template for the country being used. You can find the templates under "Localizations" in the admin app.

This is done for performance reasons. The DataDescriptor object has an attribute to allow you to decide whether to retrieve the description or not. If you take a look at RecentlyViewedProductsWithDetailsBody.jsp you'll see an example of getting back the description for an array of products. You can get and set the DataDescriptor used in the ProductManager directly from the action classes.

Take a look at http://www.konakart.com/docs/EngineCustomization.html

At the moment, through the API you can get a list of products belonging to a bundle. There isn't an API call to get a list of bundles for a product although you could do it with a custom API call with a query on the products_to_products table.

The content stored in the CMS has to contain some metadata that binds it to the KonaKart product. This could be the product id or SKU.

To view product details you can call the following struts action, passing it the product id:

SelectProd.do?prodId=17

To add to cart you can use:

AddToCartFromProdId.do?prodId=4


There are plenty examples in the JSPs of the store front application available in the download kits.

What we normally suggest is to make the KK session last longer than the LR session. Once the LR session times out, it won't allow you access to the KK Admin App.

In previous versions of KK, a timeout of the Admin App session was causing an exception. However, this should have been fixed in the latest release.

You just have to intercept the editProduct API call using the custom engine.

You can send template based mails (using the admin app or APIs) to all customers who have asked to be notified about a product.

These mails don't get sent out automatically every time you make an edit since that wouldn't work in a real world scenario. You have to decide when to send them and what template to use. This process could be automated if for example you wanted to always send out a mail when the price changes. You could store the name of the template in a product custom field or a configuration variable if it is common to all products.

I want to view more details about customer in order details page.

Add the detail to the Velocity template (OrderDetails_xx.vm)

If you haven't purchased the Admin source code, then you can't generate new javascript using the GWT compiler. However, there is a mechanism for integrating custom panels to add your own functionality within the Admin App framwork. Look at 
http://www.konakart.com/docs/AddingCustomFuncAdminApp.html

Example: I want to have the access to add more than 4 images for the product in the admin. Is it possible?

I would do this using a naming convention like we do with our store-front application (i.e. sku_img_1, sku_img_2 etc.). However, if you really want to store many different image names, you can always use custom fields.

I need to be able to implement multiple product options for the same product. I'm selling a magazine and need to be able to sell a half year and full year subscription. I'm hoping, and figuring, this isn't that big of a deal. When I search for 'models' or 'model' here in the forum I get 2 results total.

You can implement as many options as you want; each of which changes the final price of a product. e.g. http://www.konakart.com/konakart/SelectProd.do?prodId=1

The potential pony that I also am asking for is to be able to sell two models of two different products together.

You could bundle them, although if the options have to be fixed you may have to store the options in a custom field of the bundled product so that you know exactly what the bundle consists of.

You can add as many as you want. In our demo we use 8 images (4 small and 4 large). They all follow a naming convention so that you only have to store one image name associated with the product. Take a look at ProductDetailsBody.jsp.

KonaKart is API based which means that all functionality is available through the API calls . If you use the Custom Engine http://www.konakart.com/docs/EngineCustomization.html you can easily add code before and after the API calls in order to perform some custom action. This is normally a better approach than adding the code in the store-front application since it applies whenever the API call is called regardless of who is making the call.

You can upload images from other parts of the admin app to get them on the server so you could get them there, although I'd say that most of our customers use FTP as part of an automated process, rather than uploading single images through the admin app.

Anyway, if you are integrating KK with a CMS system it probably makes more sense to manage the content through the CMS since that's what it's good at doing.