Messages

Thanks Clinton,

Looks like our deployed Tomcat is not validating the web.xml. We'll update this for all future releases.

Regards,

Julie

Hi Clinton,

Is this something you are seeing in the 2.2.0.7 release that you didn't see in the previous one ?

Thanks,

Julie

Hello Bruce,

I suggest that you do have a separate product with unique SKU for each article. Alternatively you could have one product with many options although this isn't really feasible with thousands of options.

If each article is a separate product with a unique SKU and correct name, this will ensure that all of the features of KonaKart will work correctly such as the invoice, the callback when an order is made etc. and from the order you will always be able to track down exactly what was bought.

Just out of curiosity, if you don't have all of your products in the catalog, how can a customer find them ?

Regards,

Julie

Hello,

In KonaKart a basket item has to be associated with a product. When you create an order, you pass in an array of basket items and from this array it needs to be able to figure out what products (+ options) you are ordering.

Julie

Hello,

We have an example of how to create an order (which involves adding products to the basket) which you can download from http://www.konakart.com/apiexamplesfaq.php .

Normally you would create a basket item by giving it a product and a quantity. i.e.

            // Create a basket item
            BasketIf item1 = new Basket();

            // Set the product id for the basket item
            item1.setProductId(PROD_ID);

            // Set the quantity of products to buy
            item1.setQuantity(1);

            // Add this basket item to the basket
            eng.addToBasket(sessionId, 0, item1);

What you will notice is that the final_price attribute of the customers_basket table is populated automatically since it gets the price from the product. The finalPriceIncTax attribute is calculated on the fly, when for example, you call the getBasketItemsPerCustomer() method. It takes into account the customer's address and tax rate in order to calculate tax.

Regards,

Julie

Hi,

There is no API that searches the options of a product. If this is important for you, for someone to search on say "black", what I suggest is for you to add a section in the description that says something like "The Nokia 1110i is available in the following colors black, white etc. etc."

Regards,

Julie

[searchForProducts()]

Hi,

The API call you need to use is called searchForProducts() . One of the parameters that you supply is a ProductSearch object. In this object you can specify :

• The category


• The manufacturer


• The price range


• The date range for when the product was added


• Search Text, and whether to search in just the name or in the description as well

Regards,

Julie

[getProductsPerCategory()]

Yes !

You need to use the API call , getProductsPerCategory() . You can find details in the Javadoc:

getProductsPerCategory

ProductsIf getProductsPerCategory(java.lang.String sessionId,
                                  DataDescriptorIf dataDesc,
                                  int categoryId,
                                  boolean searchInSubCats,
                                  int languageId)
                                  throws com.konakart.app.KKExceptionReturns a Products object for the given category and language.

Only Products with a non zero status and non zero invisible are returned. The description (which can be very long) and the array of options are not set. Also only the first two custom fields are returned (custom1 and custom2). The specialPrice is null if a special offer doesn't exist for the product.

dataDesc may be null. In this case, the number of retrieved products is limited to a default number, the products are ordered by the ProductId and the offset is set to zero. However, by setting the attributes of dataDesc, the following functionality may be controlled :
The maximum number of Product objects returned.
The offset which defaults to zero. This is useful when there are many Product objects, in order to return them using multiple calls to this method.
Whether or not to return invisible products.
Criteria on the custom attributes. If a custom attribute is set then only products with a matching custom attribute value are returned.
The Products may be sorted by :
Name
Price Ascending
Price Descending
Date Added
Manufacturer
Times Viewed

Parameters:
sessionId -
dataDesc -
categoryId -
searchInSubCats - Determines whether products are searched for in the subcategories of the specified category
languageId - The id for the language that will be used. Value of -1 selects the default language.
Returns:
Returns a Products object
Throws:
com.konakart.app.KKException

Regards,

Julie

Hi Joel,

Have you tried tabbing out of the field that you are editing ? In the case of product, since there is so much data, we only validate once you leave the field that you are editing rather than after every keystroke. Note that the save button will remain disabled if the data doesn't validate. In this case the field(s) that don't validate should turn yellow.

Regards,

Julie

Hi Clinton,

It's such a good point we have already done this for the next release    (that will be v 2.2.0.7)

What you will see is all the customisable application classes inside konakart_custom.jar and konakartadmin_custom.jar.   These classes will be all those for which you have source that's shipped under the examples directory in the kit.

This should make it a lot cleaner as you suggest and easier to build your own customisations into these custom jars.

The new release will be (should be?!) available this week.

Regards,
Julie

Hi Sivaprakash,

You should always get the session from a login call to the API and not generate it yourself.  Note that there are different logins and session Ids for the KonaKart application API and the KonaKart Admin API.

I'm afraid that for security reasons we don't think it's appropriate to disclose the way the session Ids are produced.

I still don't understand why you need to know this anyway, since you should get the sessionId from a login call to either API.

Perhaps I've misunderstood your question?

Regards- Julie

Hello Sivaprakash,

But it is in hex decimal.May i know..How u r generating that value. whether its random value or its related to user id. Can u tell me.Please help me.

Can you explain why it is important for you to know these details? 

Thanks,
Julie

Hi Sivaprakash,

Yes, in the KonaKart Admin App up to and including the 2.2.0.6 release, the browser refresh will reload the admin app into the browser and force you to login again as it deliberately clears the state.  It's designed so that you shouldn't need to hit the refresh button, unless perhaps you need to load a new version of the admin app.

However, in the next release there are some changes in this area.  In KonaKart Admin App v 2.2.0.7, after the browser refresh is clicked, the user will return to the page they were on prior to the refesh.   The Admin App uses cookies for this information so it'll only work if cookies are enabled.

A much more significant change in the 2.2.0.7 release is the new role-based security for the Admin App.   This should be available later this week.  For news of this and notification of all new releases, ensure you register for the forum newsletter - a mail is sent out when new releases become available.

Julie

[webapps/konakartadmin/WEB-INF/classes]

Hello,

In versions up to and including KonaKart 2.2.0.6 you set the konakart-logging.properties logging properties under the konakartadmin webapp... (in webapps/konakartadmin/WEB-INF/classes) eg, these are usually the useful paths to set :

log4j.logger.org.apache.torque.util.BasePeer  = DEBUG
log4j.logger.com.konakart                           = DEBUG
log4j.logger.com.konakartadmin                    = DEBUG

In KonaKart 2.2.0.7 and beyond there is a new logging option - this is really most useful as a diagnostic tool.   The idea is that it enables "client-side" logging of the Admin APIs.   The KonaKart Admin App uses the Admin APIs so it can be used to diagnose problems in the Admin App but with the logging directed to the server log.   Note that this can be a useful tool for diagnosing problems in any custom interface you might build to the Admin APIs - it allows you to send a logging message to the server log through the API.   

The next release of KonaKart (v2.2.0.7) is quite close to being ready...  Watch out for it later this week.

I wouldn't use DEBUG for the above quantities for too long because there will be a lot of diagnostic output to wade through!

good luck!
Julie