• Welcome to KonaKart Community Forum. Please login or sign up.
June 25, 2019, 06:49:52 pm


KonaKart v8.9 - Released Aug-2018 - see KonaKart website for details

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - innes

Feature Requests / Re: packaging libraries better
August 15, 2013, 09:09:33 am
Thanks jordinini, I will have a look.

I also came across a mavenised KK as part of the integration with HippoCMS (https://github.com/jmirc/Hippo-CMS-Konakart) that you may be interested in looking at.

Programming of KonaKart / Re: GWT version
June 22, 2012, 08:41:01 am
Excellent, many thanks Ming!
Programming of KonaKart / Re: GWT version
June 21, 2012, 08:27:32 pm
Hi Ming

Thanks for the GWT version details...do you know the GWT version for

Many thanks,
Shopping Widgets / Re: Shopping Widgets
May 16, 2012, 10:59:11 am
Looks really good.

Will it be in both Community & Enterprise editions?

Can you filter what products are available in the widget?  For example can I select only certain categories. manufacturers or product types?

I can see lots of applications.

Feature Requests / Re: packaging libraries better
April 13, 2012, 06:46:57 pm

Definitely looking for integrating KonaKart with Maven.

Hi Ryan

Thanks for the reply.  Sounds like a plan, I'll let you know how it goes.

Many thanks,
Hi all

I see a number of posts (including a previous one from myself) relating to multi-currency support.  However, these seem to relate to reasonably old versions of KK, so I thought I would ask the question again to get the latest guidance.

My customer wants to enable multi-currency in KK using the existing multi-currency setup but with the additional step of also passing across the user selected currency and associated Order value to PayPal.

I notice from previous postings that KonaKart made the design decision not to expose this, as it is not guaranteed that all Payment Gateways support multi-currencies.

Debugging the checkout process suggests that the default currency & value are set in the Order in com.konakart.bl.OrderMgr.createOrderWithOptions, which is not part of the KK Open Source code.

Is there a recommended way to customise KK to support this functionality?

I have looked at a number of approaches (using custom fields, adding a conversion in the PayPal module) but the Order Total is used in multiple places like Order History & customer emails which means I need to make changes in multiple places to ensure consistent messages to the customer.  Ideally, I would like to change one place that works with the existing KK code to replace the default currency & value in the Order with the customer selected currency & value.


I tried installing the latest version of dotCMS with the KonaKart plugin but this fails (see http://tech.groups.yahoo.com/group/dotcms/message/10144) & leaves the installation corrupted.

I notice from the README that this is only tested with
Tested with Versions:
   0.1  Konakart 5.0.0
   0.2  dotCMS

Are there any plans to upgrade the plugin to support the latest versions of dotCMS?  I appreciate that the plugin is "as is" however it will quickly become irrelevant if it cannot be run with the latest dotCMS.


I am trying to run the tests using the Ant script, however the "start-server-for-tests" target has the following:

<copy file="tomcat/conf/server-tests.xml" tofile="tomcat/conf/server.xml" overwrite="true"/>

This file does not exist in the dotCMS installation I have checked out fron SVN.

I tried commenting out this step & just use the default server.xml but every test fails with:
java.net.ConnectException: Connection refused
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
   at java.net.Socket.connect(Socket.java:529)
   at java.net.Socket.connect(Socket.java:478)
   at java.net.Socket.<init>(Socket.java:375)
   at java.net.Socket.<init>(Socket.java:189)
   at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:86)
   at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:652)
   at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:628)
   at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:526)
   at org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect_aroundBody0(HttpClientConnectionHelper.java:144)
   at org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect_aroundBody1$advice(HttpClientConnectionHelper.java:307)
   at org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect(HttpClientConnectionHelper.java:1)
   at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.callRunTest(DefaultHttpClient.java:163)
   at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:81)
   at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:307)
   at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(DefaultHttpClient.java:1)
   at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebTest(HttpProtocolHandler.java:164)
   at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody0(HttpProtocolHandler.java:83)
   at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody1$advice(HttpProtocolHandler.java:307)
   at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest(HttpProtocolHandler.java:1)
   at org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestCaseCaller.java:145)
   at org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCactusTestCase.java:218)
   at org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTestCase.java:134)
   at junit.framework.TestResult$1.protect(TestResult.java:106)
   at junit.framework.TestResult.runProtected(TestResult.java:124)
   at junit.framework.TestResult.run(TestResult.java:109)
   at junit.framework.TestCase.run(TestCase.java:120)
   at junit.framework.TestSuite.runTest(TestSuite.java:230)
   at junit.framework.TestSuite.run(TestSuite.java:225)
   at junit.framework.TestSuite.runTest(TestSuite.java:230)
   at junit.framework.TestSuite.run(TestSuite.java:225)
   at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
   at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

Is there anything in the server-tests.xml that I need?

Hi Trevor

Apologies for the delay in getting back to to you.  I have thought about this a bit more and was wondering if I could add additional relation_types to products_to_products?

At the moment I can see a value of '5' in the demo sql, are there defined values for the various merchandising relationships?  Do you know the impact on the admin app & kk API if I added (for example) 10 for parent/child, 20 for sibling, 30 for alternative formats?

Do you know where the relation_type values are defined?  Are they configurable?

Great, thanks.  I'll have a look.


I am looking at the dotcms plugin & want to extend the checkout to support the payment providers in my KK Admin (especially PayPal). Can you provide the recommended steps to do this?

Should I use the downloaded plugin (it looks like there is source code & Ant script* provided) as a starting point and then extend it to support the additional KK functionality I require?

How do I add my additional code to the dotCMS installation?  Do I run the dotCMS Ant script to refresh the plugins?

Is there an tutorial that explains how to customise the plugin?  This would be really useful as the plugin is a good example of how a KK & dotCMS could interact but to get it into production we will need to customise it.  This would also be required if we are to benefit from new KK functionality in the future


ps Ant script consist of:

<project name="KonaKart plugin" default="build">   
   <import file="../common.xml"/>   

but common.xml isn't in zip file?
Thanks Trevor.

I had looked at the merchandising types but I was wanting to keep them for their original purpose.  Do you know if you can add more types?

I am thinking that I would like Parent/Child (eg track to & from album), siblings (others tracks on same album), alternative formats (eg pdf, epub, kindle).

We are prototyping integrating dotCMS & KonaKart.

How would I upgrade the KK plugin & dotCms/KK themselves without losing existing setup but also gaining new functionality/bug fixes?  How do we handle the scenario where we need to edit the "view" defined in the plugin to suite our requirements? For example from the evaluations we have done so far, the plugin expects 4 images on the product detail page but we normally only have one.  This results in the missing image icon being displayed. We can edit this locally but the more changes we introduce to the plugin the greater the cost in upgrading to new versions (that I assume will be required for newer versions of Kk). 

The raises an assumption on our part:  will the plugin be maintained going forward or is it purely designed as framework that we then run with?