Messages

You could achieve this with the multi-store version of KonaKart which however isn't free. In our next version coming out soon, we've introduced a multi-vendor mode which will allow vendors to maintain their own products. If a customer buys multiple products (from different artists) in a single order, the customer sees the shipping charges from the various artists and each artist receives an order containing only his own products. The payment goes to the main store belonging to the administrator who then has to redistribute it to the artists.

The way to achieve this with KonaKart is to use variable quantity product options. i.e. You have a variable quantity weight option with an option value of Kg. When you associate this with the product you can define the price per Kg and on the storefront side the customer can enter the number of Kg he wants to buy. In our standard storefront we automatically render an input field for this type of product option.

Of course its possible. Take a look at some of our customer sites:

http://www.eq3.com/ca/en/p25579/panton-junior-chair
http://www.farmrio.com.br/loja/vestidos/produto/12141?pagina=-1&contexto=novidadinhas&idestampafiltro=14111
http://www.globus.ch/fr/shop/produits/494/Olio-Aceto-in-Legno.html
https://raceforlife.cancerresearchuk.org/rfl/forms/shop/shop_product.jsf?productId=163&categoryId=23

The reason for setting them to be invisible is so that they aren't present in the category tree. If you want them to be present then set them to visible.

When you set a category to be invisible, it isn't returned in the category tree of the storefront engine. If you know the id you can get it using the getCategory() API call.

Whenever we run the startup script

Is that startkonakart.bat ?

Looks like you've given it an image name without an extension so the split doesn't work.

It's been available for a while for supported customers. Contact us if you want a copy.

Please attach it to your post. Thank you 

Within the application you can use the editCustomer() API call:

    /**
     * The Customer object will replace the existing customer object in the database.
     * <code>cust</code> has to be the same customer logged in with a valid <code>sessionId</code>.
     * Only non null attributes or integers not equal to -1 will be used (i.e. set an integer field
     * to -1 if you do not want to change it).
     * <p>
     * The attributes from the Customer object that are used are :
     * <ul>
     * <li>gender</li>
     * <li>firstName</li>
     * <li>lastName</li>
     * <li>birthDate</li>
     * <li>emailAddr</li>
     * <li>faxNumber</li>
     * <li>telephoneNumber</li>
     * <li>telephoneNumber1</li>
     * <li>locale</li>
     * <li>newsletter</li>
     * <li>password</li>
     * <li>customerType</li>
     * <li>customerGroup</li>
     * <li>custom1</li>
     * <li>custom2</li>
     * <li>custom3</li>
     * <li>custom4</li>
     * <li>custom5</li>
     * <li>dateLastModified</li>
     * <li>globalProductNotifications</li>
     * </ul>
     *
     * @param sessionId
     *            The session id of the logged in user
     * @param cust
     *            The customer object to edit
     * @throws KKException
     */
    public void editCustomer(String sessionId, CustomerIf cust) throws KKException;

Yes, you can do that either through the admin app or the admin APIs.

When you use the admin app, it also prompts you to allow you to send a template based email for which group you are being transferred to. e.g. You may sign up as a wholesale customer but be temporarily be put into a retail customer group until you are approved. When you are approved, the administrator changes your group and sends out an email to inform you of the change.

Check out the KonaKart mobile storefront application  http://www.konakart.com/konakart-m/Welcome.action .

The demo uses the same instance of the KonaKart eCommerce engine as the standard demo (so you don't need to register again). All of the JSPs have been rewritten in order to provide a touch friendly interface for mobile handsets and tablet computers.

Can you point me to your current store so that I can get an idea of the type of customizations you've made?

You can still use 6.5 but only with the struts1 storefront. It's explained in LiferayPortletInstallation.pdf in the doc directory.

We are working on "portalising" the new struts 2 storefront application. Currently, only the struts 1 storefront can be converted to a portlet using the ANT task. You can run the struts 2 app in an iFrame portlet.

The struts 2 application cannot use the struts portlet bridge and it uses a lot more AJAX and javascript and a KK tag library which makes the exercise more difficult. However, we have it working in the lab and hopefully it will soon be made available. Our aim this time around is to make a tighter integration with Liferay by providing SSO in the new storefront portlet.