Messages

Hi,

Your English is perfect !

KonaKart EE doesn't require Liferay EE. It works fine with Liferay CE.

In the AdminOrderSearch object you can set the search rule:

public void setCustomerNameRule(int customerNameRule)

The rule for the search. Valid values are:
KKConstants.SEARCH_EXACT
KKConstants.SEARCH_ADD_WILDCARD_BEFORE
KKConstants.SEARCH_ADD_WILDCARD_AFTER
KKConstants.SEARCH_ADD_WILDCARD_BEFORE_AND_AFTER
KKConstants.SEARCH_USE_GLOBAL_CONFIG

You should use the AdminApi call

Code Select Expand

public AdminAddressSearchResult getAddresses(String sessionId, AdminAddressSearch search,
            int offset, int size) throws KKAdminException;

We released it yesterday.

In the next version (which will be out soon) we've added configurable HTML escaping for the transactional API calls such as editCustomerAddress() or registerCustomer(). However, to ensure a high level of security, what we recommend is for you to only make available the non transactional API calls over the internet and provide an extra layer of your own for the transactional calls so that you can carry out your own HTML escaping and also it's typically better for performance because after for example a registration, you may want to send an email, log in the customer and set some customer tags which you can do directly from the server instead of multiple round trips from the client.

I'm not sure what the problem is? You have access to the dependent products so you can display them next to a checkbox or whichever way you want, and you can automatically add them to the cart in the struts action class if that's what you want to do.

If you don't want them to be found during a normal search just make them invisible.

I'm afraid that doesn't make much sense to me and it's obviously not the way KonaKart works when you install it OOTB.

Without understanding exactly what you've done it's very difficult for me to envisage what's happening. Since you have all of the source and an Eclipse project, what I advise is for you to try debugging the storefront to get some more clues.

I can only see that happening if it's the same user logging in from two different machines since the cart items are retrieved from the database when a customer logs in.

You'll have to manage this yourself when the product is added to the cart. Depending on what your rules are, it may be a bit tricky to manage situations where a customer attempts to remove or change the quantity of just one of the bundle components.

Try checking out with https://www.konakart.com/konakart/Software/KonaKart/KonaKart-Manual/7.3/2_64.action

For the next release we've added a way to be able to login using either a username (new customer attribute) or one of the two telephone numbers. We've also added code to optionally check for uniqueness of these three attributes when registering or editing a customer either from KKEng or KKAdminEng including the Admin App.

I'm not sure what the vendor panel is !

Yes, that's fine. It's really up to you what date you add to that field.

You can modify it yourself.

We have already enabled the JSON on server both the servers in web.xml file.

I would only enable B to avoid using A by mistake.

We are using KKBasePeer.executeQuery("Some SQL Query") statement in action class itself of server A. So did you mean, we will not be able to user the KKBasePeer in server A.

An action class in both A and B does not have direct access to the database. You cannot run SQL from an action class.

After doing the above all four mentioned things, still if two different user tries to login in the two different stores then the user who logged in first store gets logged out when user in second store logs in.

The way you describe it would imply that you can only ever have one user ! This doesn't make any sense to me.