Messages

i'm trying to transfer konakart customers in another system for authentication

It's not clear to me what you are trying to do.

Are you trying to move KonaKart customers to another system or are you trying to move customer records from another system into KonaKart's database?


Note that we don't like to publish details of the password generation for security reasons.

You should be ok to extend the size of columns in the KonaKart DB.  When running the upgrade scripts first check each statement to ensure that any column changes that may have occurred do not conflict with yours.  It would be unusual for there to be a conflict but it's worth checking.  Generally speaking you should be OK extending the size of columns used by KonaKart but, in some cases, you might find that the field validation in the Admin Application assumes the original size - so that may need to be modified.

No, you're right, those custom attributes are only for products but you can use a similar technique to combine your attributes and save them in one custom attribute on the order.

Have you considered using custom attributes where you can have an unlimited number of custom attributes?

Alternatively, can you save your attributes in some kind of data structure (in JSON format perhaps?) to combine more than one of your business quantities in one custom column?

If you don't want the EPayBG module you need to remove it.

Remove the payment modules you don't want from the configuration_value for the configuration_key MODULE_PAYMENT_INSTALLED (this is in the configuration table in the database).

If you don't need any particular module you can remove its jar from the konakart and konakartadmin webapps (WEB-INF/lib directories)

You can also remove them from the "konakart.modules.payment" property in konakartadmin.properties if you don't want to appear in the Admin Console.

Code Select Expand

konakart.modules.payment=Authorizenet BarclaycardSmartPayHosted BarclaycardSmartPayApi Bluepay Caledon Chronopay Cod CommideaVanguard CyberSourceSA Elink Eway_au GlobalCollect MoneyBookers Netpayintl PayflowPro Payjunction Paypal Usaepay Worldpay WorldPayXMLRedirect

It's a one-way algorithm - not designed to go from the value in the database to the original password.

Yourpay was retired in v7.4.0.0 (Feb 2015) because its gateway service was no longer available.

So really...  you shouldn't have had that active in your database for a long time. It wouldn't have worked.

Anyway, it sounds like you have removed it now so that's good.  You can remove its MODULE_*** configuration values if you wish but they won't be used.   Normally these are removed when you remove a module from the Admin Console but in your case you were using a version that didn't have the module to delete yet it was still present in a database from an earlier system that did have the module.   With the benefit of hindsight it would have been better to remove the modules before upgrading.

You administer the modules in the KonaKart Admin Console.  That's where you install / remove / configure them.  See under Modules >> Payment

If you remove a module from there it should not show up in your log like that.

Obviously the konakart and konakartadmin webapps must be using the same database.

If you removed them they shouldn't be there any more.  Maybe your Admin Console's webapp is pointing to a different database?

You seem to have got yourself in a bit of a mess.

Can you install a fresh copy and work from that?

When upgrading the database from one version to another you must execute the relevant upgrade scripts in the correct sequence from the version you started on to the version you want to reach.

It's a configuration parameter.  You set these in the Admin Console.   In this case it's a module configuration parameter.

Take a look at:

https://www.konakart.com/forum/index.php?topic=1812.0

Which site are you upgrading from v3?  That's a very old version 

We have been working on a solution for running our automatically-generated portlets in Liferay 7 and DXP.   It's quite close but not ready yet.  We are about to release v8.3 of KonaKart in which the solution for Liferay 7 is included but not fully-working so unless you want to spend time resolving the outstanding problems it's not recommended (there are issues with jQuery compatibility amongst others).

So, currently we are suggesting that if you want to us KonaKart in Liferay 7 or DXP you should use the KonaKart APIs to underpin your own portlets blending eCommerce functionality with your other content.  An excellent way to do this is by leveraging the KonaKart Tiles which provide a full KonaKart storefront in JavaScript.  Both techniques offer a good solution for the ultimate in flexibility on the storefront.

There is no problem with KonaKart co-existing with Liferay's new OSGi architecture.

If you wanted to continue to use the automatically-generated portlets you will have to stay on Liferay 6 for now.

No I would never recommend that you log out the user just because he's made a payment.

I would recommend you revert to the original code and keep the customer logged-in.   If the customer's session is being lost you should investigate why...  check the URLs in use at each stage to see why it considers that your customer has switched to another session.

The reports are merely examples so feel free to change the data source if that's the way you got your new ones to work.  Indeed you will find it a lot easier when working in BIRT's designer if you hard code the datasource and not access it dynamically (as we do in the sample reports).

For more information on BIRT report design you might like to look at their tutorial at http://www.eclipse.org/birt/documentation/tutorial/tutorial-14.php

It's difficult to say why....  for me with a standard installation it just works.

Do you get any clues in the tomcat log?

If you enable Javascript debugging on the browser do you see any useful information?

Buy X Get Y Free is indeed designed for the same product.

You might want to look at the FreeProduct module which would allow the specification of the tie as the free product.

You have the source code for the modules.  You may need to merge the code from the above two order total modules to create a module that's just what you want.....