Release Notes

Release notes for KonaKart v 8.3.0.0

  • v8.3.0.0 a major public release that contains many new features and bug fixes.
  • When upgrading from version 8.1.0.n, ensure that you run the following upgrade database script for your chosen database:
    • upgrade_8.1.0.0_to_8.3.0.0.sql
  • Backwards Compatibility Alert
    • TotalDiscount promotion module has been modified to calculate a percentage discount on the current order amount when it is called. This may be less than the original sub-total if for example a product discount or a buy x get y free discount has already been run.
    • With the introduction of the new MySQL JDBC driver (mysql-connector-java-5.1.39-bin.jar) you will need to add &useSSL=false to your JDBC connection URL if you don’t want to enable an SSL connection to your MySQL database.
    • The following properties in konakart.properties and konakartadmin.properties have been replaced:

      • konakart.ws.mode = 0
      • konakart.ws.customersShared = false
      • konakart.ws.productsShared = false
      • konakart.ws.categoriesShared = false
      • konakart.rmi.mode = 0
      • konakart.rmi.customersShared = false
      • konakart.rmi.productsShared = false
      • konakart.rmi.categoriesShared = false
      • konakart.json.mode = 0
      • konakart.json.customersShared = false
      • konakart.json.productsShared = false
      • konakart.json.categoriesShared = false

      Instead of the above, the following new properties (placed in konakart.properties and konakartadmin.properties) should be used in all cases:

      • konakart.engineMode = 0
      • konakart.customersShared = false
      • konakart.productsShared = false
      • konakart.categoriesShared = false
    • The following KonaKartAppEngineServlet servlet initialization parameters have been replaced:

      • mode
      • storeId
      • customersShared
      • productsShared
      • categoriesShared
      • defaultStoreId

      Instead of the above, the following new properties (placed in konakart.properties and konakartadmin.properties) should be used in all cases:

      • konakart.engineMode = 0
      • konakart.defaultStoreId = store1
      • konakart.customersShared = false
      • konakart.productsShared = false
      • konakart.categoriesShared = false
    • The following properties in konakartadmin_gwt.properties have been replaced:

      • konakartadmin.gwt.mode = 0
      • konakartadmin.gwt.customersShared = false
      • konakartadmin.gwt.productsShared = false
      • konakartadmin.gwt.categoriesShared = false

      Instead of the above, the following new properties (placed in konakartadmin.properties) should be used:

      • konakart.engineMode = 0
      • konakart.customersShared = false
      • konakart.productsShared = false
      • konakart.categoriesShared = false
    • The following KKAdminGWTServiceImpl servlet initialization parameter has been replaced:

      • defaultStoreId

      Instead of the above, the following new property (placed in konakartadmin.properties) should be used:

      • konakart.defaultStoreId = store1

Release notes for KonaKart v 8.1.0.0

  • v8.1.0.0 a major public release that contains many new features and bug fixes.
  • When upgrading from version 8.0.0.n, ensure that you run the following upgrade database script for your chosen database:
    • upgrade_8.0.0.0_to_8.1.0.0.sql
  • Backwards-Compatibility Alert:
    • Java 6 is no longer supported.
    • MS SQL Server Users – Upgrading from previous versions.

      From v8.1.0.0 of KonaKart the default set-up for SQL Server uses NVARCHAR for columns where it is expected that Unicode data may be required. For example, NVARCHAR is used for columns that are populated by users (such as first name, last name etc). For those MS SQL Server users who are upgrading to v8.1.0.0 of KonaKart an upgrade script is provided to convert the relevant VARCHAR columns to NVARCHAR columns to bring the database in line with the default v8.1.0.0 database.

      It is strongly-advised that you study the MS SQL Server upgrade script at “*\database\MSSqlServer\upgrade_8.0.0.0_to_8.1.0.0.sql” to see that it meets your requirements and is compatible with your own MS SQL database (it might not be if you’ve modified the columns in your version).

      It is strongly-recommended that you test the execution of this particular upgrade script on a copy of your own production database prior to executing it on your live production database.

Release notes for KonaKart v 8.0.0.0

  • v8.0.0.0 a major public release that contains many new features and bug fixes.
  • When upgrading from version 7.4.0.n, ensure that you run the following upgrade database script:
    • upgrade_7.4.0.0_to_8.0.0.0.sql
  • Backwards-Compatibility Alerts:
    • Due to a slight code-reorganization to remove some cyclic dependencies a few classes have moved from one konakart jar to another and some classes have been removed:

      From konakart.jar to konakart_custom.jar:

      • com.konakart.bl.OrderIntegrationMgr$TaxModuledata


      From konakart.jar to konakart_utils.jar:

      • com.konakart.KonaKartVersion
      • com.konakart.app.KKException


      From konakart_custom.jar to konakart.jar:

      • com.konakart.blif.LDAPMgrIf
      • com.konakart.bl.modules.ordertotal.OrderTotalInterface

    • These redundant classes have been removed:

      Removed from konakartadmin_gwt.jar:

      • com.konakartadmin.client.util.GWT_Validation
      • com.konakartadmin.client.util.GWT_Utils

      Removed from konakart_payment_worldpay.jar:

      • com.konakart.actions.gateways.WorldPayXMLRedirectResponseAction
    • Several jar name changes. Introduced the jar names used by maven for the purpose of supporting maven builds.
    • Admin Objects no longer inherit from AdminObjectIf which has been removed. The id in the inherited AdminObjectId was causing conflicts. In any custom code that you have written you should check that you are setting the correct Id – a simple recompilation of your code will tell you. If you have any compilation failures, replace the setId() or getId() with a set or a get of the relevant object Id and not the generic id attribute.
    • The addTerm() method of the AdminSolrMgr has an extra attribute (catalogId) . This is only of interest if you have specialised this method in your own AdminSolrMgr.
    • Enterprise users should ensure that the correct “EE” managers are specified in the two main properties files: konakart.properties and konakartadmin.properties. AdminProductMgrEE and AdminOrderMgrEE were introduced so if you are upgrading you will need to specify the new EE class names. You will need to specify:

      • konakart.admin_manager.AdminProductMgr = com.konakartadmin.bl.AdminProductMgrEE
      • konakart.admin_manager.AdminOrderMgr = com.konakartadmin.bl.AdminOrderMgrEE

      If you already had your own specialisations of these Managers you will need to modify these to extend the EE versions in order to access the new Enterprise functionality.

    • In the MqOptions class the attribute “String customInt1″ has been changed to “int customInt1″.

    Release notes for KonaKart v 7.4.0.1

    • v7.4.0.1 is a minor public release containing a fix for the following problem:
      • In the Admin Application it was not possible to create a new Manufacturer if configured to show Manufacturer Ids.
    • No database upgrade scripts are required. The 7.4.0.1 version of KonaKart is compatible with the 7.4.0.0 database.
    • No compatibility alerts; No special actions required.

    Release notes for KonaKart v 7.4.0.0

    • v7.4.0.0 a major public release that contains many new features and bug fixes.
    • When upgrading from version 7.3.0.n, ensure that you run the following upgrade database script:
      • upgrade_7.3.0.0_to_7.4.0.0.sql
    • Backwards-Compatibility Alert:
      • Payment Gateways retired: CyberSource HOP, CyberSource SOP, YourPay. These were removed because their gateway services are no longer available.

    Release notes for KonaKart v 7.3.0.1

    • v7.3.0.1 is a minor public release containing fixes for the following problem:
      • Fix a security vulnerability in Struts-2
    • No database upgrade scripts are required. The 7.3.0.1 version of KonaKart is compatible with the 7.3.0.0 database.
    • No compatibility alerts; No special actions required.

    Release notes for KonaKart v 7.3.0.0

    • v7.3.0.0 is a major public release that contains many new features and bug fixes.
    • When upgrading from version 7.2.0.n, ensure that you run the following upgrade database script:
      • upgrade_7.2.0.0_to_7.3.0.0.sql
    • A number of classes have been moved from the konakart.jar to the konakart_custom.jar. This has been done to make it much easier to customise these classes and re-generate the konakart_custom.jar by using the standard ANT build in the custom directory. The classes that have been moved are:
      • *custom/appn/src/com/konakart/bl/modules/ordertotal/OrderTotalInterface.java
      • *custom/appn/src/com/konakart/bl/modules/ordertotal/OrderTotalMgr.java
      • *custom/appn/src/com/konakart/bl/modules/others/AddrValidationInterface.java
      • *custom/appn/src/com/konakart/bl/modules/payment/PaymentInfo.java
      • *custom/appn/src/com/konakart/bl/modules/payment/PaymentInterface.java
      • *custom/appn/src/com/konakart/bl/modules/payment/PaymentMgr.java
      • *custom/appn/src/com/konakart/bl/modules/shipping/ShippingInfo.java
      • *custom/appn/src/com/konakart/bl/modules/shipping/ShippingInterface.java
      • *custom/appn/src/com/konakart/bl/modules/shipping/ShippingMgr.java
      • *custom/appn/src/com/konakart/bl/modules/shipping/WeightCost.java
    • Publish Products and Google Shopping functionality has been removed due to the demise of Google Base then Google Shopping.
    • Modified the Admin API call editOrder() to include the OrderProduct custom fields. This change should be backwards compatible but it’s good to be aware of it.
    • The mobile storefront is no longer included in the download package since the storefront now has a responsive design.

    Release notes for KonaKart v 7.2.0.2

    • v7.2.0.2 is a minor public release containing fixes for the following problems:
      • When running KonaKart in the mode that allows checkout without registration, the password entry fields would disappear after changing country when attempting to register.
      • Fix to struts.xml to prevent CVE-2014-0094 vulnerability.
      • Enhanced security to eliminate a Session Fixation vulnerability. Thanks to Christian Schneider for reporting the issue.
    • No database upgrade scripts are required. The 7.2.0.2 version of KonaKart is compatible with the 7.2.0.0 database.
    • No compatibility alerts; No special actions required.

    Release notes for KonaKart v 7.2.0.1

    • v7.2.0.1 is a minor public release containing a fix to the installers to allow automatic detection of a java 7 JRE and a fix for the deployment of a duplicate custom source file (The java source file “*KonaKart/custom/modules/src/com/konakart/bl/modules/shipping/BaseShippingModule.java” was deployed to two places so you can delete this one and leave the one in “*KonaKart/custom/appn/src/com/konakart/bl/modules/shipping/BaseShippingModule.java”
    • No database upgrade scripts are required. The 7.2.0.1 version of KonaKart is compatible with the 7.2.0.0 database.
    • No compatibility alerts; No special actions required.

    Release notes for KonaKart v 7.2.0.0

    • v7.2.0.0 is a major public release that contains many new features and bug fixes.
    • When upgrading from version 7.1.1.0 or 7.1.1.1, ensure that you run all the following upgrade database script:
      • upgrade_7.1.1.0_to_7.2.0.0.sql
    • Compatibility alerts:
      • The sort order of product options such as size and color is now determined by a sort order attribute which is set automatically by the admin app when the product is saved. Until this attribute has been set correctly, the sort order may not be the same as it was in the previous version of KonaKart.
      • With the upgrade to Torque 4 there are a number of database-related changes to be aware of. See the “Upgrade to Torque 4″ section in the User Guide.

    Release notes for KonaKart v 7.1.1.1

    • v7.1.1.1 is a minor public release containing only a Struts Security update.
    • No database upgrade scripts are required. The 7.1.1.1 version of KonaKart is compatible with the 7.1.1.0 database.
    • No compatibility alerts; No special actions required.

    Release notes for KonaKart v 7.1.1.0

    • v7.1.1.0 is a minor public release with just a few new features and bug fixes.
    • When upgrading from version 7.1.1.0, ensure that you run all the following upgrade database script (which just sets the new version number):
      • upgrade_7.1.0.0_to_7.1.1.0.sql
    • No compatibility alerts; No special actions required.

    Release notes for KonaKart v 7.1.0.0

    • v7.1.0.0 is a major public release that contains many new features and bug fixes.
    • When upgrading from version 6.5.1.0, ensure that you run all the following upgrade database scripts:
      • upgrade_6.5.1.0_to_6.6.0.0.sql
      • upgrade_6.6.0.0_to_7.0.0.0.sql
      • upgrade_7.0.0.0_to_7.1.0.0.sql
    • AdminStoreIntegrationMgrInterface.java has been moved to the blif directory. If you have created your own AdminStoreIntegrationMgr.java class you need to change it to implement:
      com.konakartadmin.blif.AdminStoreIntegrationMgrInterface instead of:
      com.konakartadmin.bl.AdminStoreIntegrationMgrInterface.
    • Definitions in AdminSearchRules.properties have been moved to the konakartadmin_gwt.properties file and are now pre-fixed by “sr.”. The original AdminSearchRules.properties file has been removed.
    • If you used the getPdf(eng.getEngConf(), options) call on the AdminEngineMgrIf the template name used (when the options type was set to KKConstants.HTML_NAMED_TEMPLATE) was retrieved from options.getCustom1(). From version 6.6.0.0 the named template will be retrieved from the options.getTemplateName() attribute.

    Release notes for KonaKart v 6.5.1.0

    • v6.5.1.0 is a minor maintenance release of v6.5.0.0 that fixes a few small UI problems and provides support for the recently-released MySQL v5.6.10.1.
    • When upgrading from version 6.5.0.0, you should consider running the following optional upgrade database script: (in this case this is really only relevant for MySQL users who wish to upgrade to MySQL 5.6.10.1 or higher):
      • upgrade_6.5.0.0_to_6.5.1.0.sql

    Release notes for KonaKart v 6.5.0.0

    • v6.5.0.0 introduces the new Struts 2 based storefront. By default the standard installer (and its Enterprise partner) will install the new Struts 2 based storefront. So, for new installations, if you wish to install the 6.5.0.0 version of the Struts 1 based storefront you will need to first install the standard Struts 2 based storefront, then you must run the Struts 1 installer and its Enterprise partner if applicable). For upgrade installations where you wish to keep your previous version’s Struts 1 based storefront the recommended approach is to:
      • Save your existing store front application somewhere safe before you start
      • uninstall KonaKart
      • Install all of the following in the same location over the top of each other:
      • Using the standard installer, install the new Struts 2 based storefront (but do not update the database using the installer)
      • If you’re using the Enterprise version, install the standard Enterprise version of the Struts 2 based storefront (again do not update the database using the installer)
      • Install the Struts 1 based storefront (again do not update the database using the installer).
      • If you’re using the Enterprise version, install the Enterprise version of the Struts 1 based storefront installer (again do not update the database using the installer)
      • Execute the upgrade SQL scripts for your database type for every release from the one you started with to the latest. Run these one at a time in sequence.
      • Move your previous Struts 1 based storefront code back into the konakart webapp
    • The API call getManufacturersPerCategory() now returns manufacturers for products of the selected category and all of its children. The new getManufacturers() API call may be used to return the manufacturers for only the selected category.
    • When upgrading from version 6.3.0.0, ensure that you run all the following upgrade database scripts:
      • upgrade_6.3.0.0_to_6.4.0.0.sql
      • upgrade_6.4.0.0_to_6.5.0.0.sql

    Release notes for KonaKart v 6.3.0.0

    • The JSON Server has become an Enterprise-Only feature and the JSON APIs are now “switched off” after a default installation. The user guide contains instructions explaining how to enable them.
    • Configuration parameters now have a new “return_by_api” attribute. To return the value of a configuration parameter through the storefront API (KKEngIf) you need to set the return_by_api column to 1 (true). By default the return_by_api value will be 0 (false). Therefore, you will need to set these values to 1 (true) if you need to access them using the various getConfiguration() API calls on the storefront API (KKEngIf). The database upgrade scripts for the 6.3.0.0 release set the “return_by_api” attribute to 1 (true) for all configuration parameters in a defined set of configuration groups (see upgrade scripts for details) which in the default installation are required by the storefront to function correctly. You should review the configuration parameters that are returned by the APIs for suitability in your system. The Admin App has been modified to allow you to set the “return_by_api” setting for each configuration parameter. It is recommended to set “return_by_api” to 0 (false) wherever possible to maximize performance, minimize memory usage and tighten security.
    • The editConfiguration() API call on KKEngIf has been deprecated but has also been modified to return a KKException in all cases. You should use the Administration APIs (defined in KKAdminIf) to modify configuration parameters.
    • When upgrading from version 6.0.0.0, ensure that you run all the following upgrade database scripts:
      • upgrade_6.0.0.0_to_6.1.0.0.sql
      • upgrade_6.1.0.0_to_6.2.0.0.sql
      • upgrade_6.2.0.0_to_6.3.0.0.sql

    Release notes for KonaKart v 6.0.0.0

    • With the introduction of Tomcat 7 there is now a requirement to use a minimum java version of 1.6 (previously KonaKart supported Java 1.5 and above).
    • The JSON APIs are now “switched on” after a default installation. The web.xml file of the konakart webapp must be edited in order to disable them.
    • When upgrading from version 5.5.0.2, ensure that you run all the following upgrade database scripts:
      • upgrade_5.5.0.0_to_5.6.0.0.sql
      • upgrade_5.6.0.0_to_5.7.0.0.sql
      • upgrade_5.7.0.0_to_5.7.5.0.sql
      • upgrade_5.7.5.0_to_5.8.0.0.sql
      • upgrade_5.8.0.0_to_6.0.0.0.sql

    Release notes for KonaKart v 5.5.0.2

    • This is a is a bug fix release for Version 5.5.0.1. It requires no database changes. A bug has been fixed in the Admin App Liferay Portlet which wasn’t loading the GWT JavaScript due to a naming error.

    Release notes for KonaKart v 5.5.0.1

    • This is a is a bug fix release for Version 5.5.0.0. It requires no database changes. A bug has been fixed which didn’t allow new customers to register when using the GWT one page checkout code in the store-front application.

    Release notes for KonaKart v 5.5.0.0

    • When upgrading from version 5.2.0.0, ensure that you run all the following upgrade database scripts:
      • upgrade_5.2.0.0_to_5.3.0.0.sql
      • upgrade_5.3.0.0_to_5.4.0.0.sql
      • upgrade_5.4.0.0_to_5.5.0.0.sql

    Release notes for KonaKart v 5.2.0.0

    • When upgrading from version 5.0.0.0, ensure that you run both upgrade database scripts: upgrade_5.0.0.0_to_5.1.0.0.sql and upgrade_5.1.0.0_to_5.2.0.0.sql.
    • By default KonaKart is now configured to use these ports in Tomcat’s server.xml file:
      Port Old New Detail
      Server 8005 8785 Change to avoid clash with default tomcat port
      HTTP Connector 8780 8780 No change
      HTTPS Connector 8443 8783 Change to avoid clash with default tomcat port
      AJP Connector 8789 8789 No change
    • Note that the upgrade script modifies the HTTPS port configuration variable (called ‘SSL_PORT_NUMBER’) in the configuration table if and only if it is currently set to 8443 otherwise it remains unchanged. Also, the upgrade script modifies the ADMIN_APP_LOGIN_BASE_URL configuration variable in the configuration table to use the new HTTPS port but only if the value is currently the default which is ‘https://localhost:8443/konakart/AdminLoginSubmit.do’

    Release notes for KonaKart v 5.0.0.0

    • The velocity templates are no longer stored directly under the WEB-INF/classes directory. They are now stored under the installation home directory in a /templates/store_id/ directory structure where store_id is the id of the store and defaults to store1 in a single store environment. It is possible to move these to any other location so long as you update the TEMPLATE_BASE_DIRECTORY to point at the new location.
    • In addition to moving the velocity templates, they are all (those from the konakart and konakartadmin webapps) now grouped together in the same location. This resulted in a conflict of names where the EmailNewPassword_en.vm existed in both the konakart and the konakartadmin webapps. Therefore the one from konakartadmin has been renamed to be EmailNewPasswordAdmin_en.

    Release notes for KonaKart v 4.2.0.1

    • This is a patch release to fix a minor problem with links in the Admin App

    Release notes for KonaKart v 4.2.0.0

    • The application and admin application method getSpecialsPerCategory() has been given an extra attribute in order to search or not search within sub categories.
    • The PaymentInfo object no longer contains a Secret Key attribute. The method to generate a secret key is now called directly from the payment module when required.

    Release notes for KonaKart v 4.1.0.0

    • The application API call getProductQuantity(String encodedProductId) now returns a ProductQuantityIf object rather than an int. The reason is to return the Date Available as well as the quantity.

    Release notes for KonaKart v 3.2.0.0

    • KonaKart engines have new constructors to cater for multi-store functionality. In some cases the old constructors have been deprecated.
    • SetConfigurationValue() in the Admin API has changed. This now requires an extra parameter. The extra parameter is the session Id. This has been modified to ensure that changes to configuration values are only made by callers with a valid sessionId. (SessionIds are returned from successful logins).
    • For security reasons, the default installation of KonaKart disables the web service interfaces. Look at the on line documentation for instructions on how to enable these interfaces.

    Release notes for KonaKart v 2.2.6.0

    • The database upgrade script sets customers’ customers_type to 0 where the customers_type is null.  This indicates that the customer is a normal customer more explicitly.
    • Previously there were two Application API calls called “getPaymentDetails” (they were overloaded with different parameters). We have changed the name of one of these calls to getPaymentDetailsPerOrder to avoid having any overloading in the APIs. Therefore, if you used:
         public PaymentDetailsIf getPaymentDetails(String sessionId, String moduleCode,
           OrderIf order, String hostAndPort, int languageId) throws KKException
      you should change the name of the call to:
         getPaymentDetailsPerOrder().

    Release notes for KonaKart v 2.2.4.0

    The following deprecated features have been removed:

    • Method – com.konakart.al.CategoryMgr.setCurrentCatAndUpdateProducts(int catId)
    • Tile – CategoriesTile.jsp
    • Action – com.konakart.actions.SelectCategoryAction()

    They have been replaced with:

    • Method – com.konakart.al.CategoryMgr.setCurrentCatAndUpdateProducts1(int catId)
    • Tile – CategoriesTile1.jsp
    • Action – com.konakart.actions.SelectCategoryAction1()

    Release notes for KonaKart v 2.2.2.0

    As far as we aware, 2.2.2.0 does not contain any modifications that could result in compatibility issues from the previous release. The download package has increased in size since the GWT one page checkout code and build file is now included, rather than it being a separate download.