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 notice from the README that this is only tested with Tested with Versions: 0.1 Konakart 5.0.0 0.2 dotCMS 126.96.36.199
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.
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?
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
Hi 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?