Messages

You'll probably get some clues if you enable the database logging so see which queries are generated.

So in konakart-logging.properties set logging like this:

Code Select Expand


log4j.logger.org.apache.torque.util.BasePeer  = DEBUG
log4j.logger.com.workingdogs.village          = DEBUG


No... I looked into this...  there is no problem upgrading from 3.2.0.0 to 4.2.0.1 (or from versions prior to 3.2.0.0 to 4.2.0.1 assuming you use the corrected version of the 3.2.0.0 to 4.0.0.0 script as discussed below).

The problem only occurs because of the insert of the 221 record (forceRegisterCustomer) in the 3.0.1.0 to 3.2.0.0 upgrade script...

Therefore, if you have never run the upgrade_3.0.1.0_to_3.2.0.0.sql script there is no need to update the 3.2.0.0 to 4.0.0.0 script and all upgrades will run smoothly using the scripts in all the download packages.

I think we'll now "tone down" the warning message on our known problems page to clarify that this is only a problem for people coming from versions prrior to 3.2.0.0.

Thanks for your confirmation and raising the problem in the first place!

Heidi

I've been looking into this a bit deeper.

Did you actually start off with a version earlier than 3200 and at some point run the upgrade_3.0.1.0_to_3.2.0.0.sql script?

I'm guessing you did.  Please can you confirm?

You are safe to include that line as you saw in the 4.1.0.0 release version.

It looks like it's missing from the 4.2.0.1 release.

Thanks for bringing this up.

Use AdminDataDescriptor.ORDER_BY_REVIEWID_ASCENDING or AdminDataDescriptor.ORDER_BY_REVIEWID_DESCENDING instead, since those Order_by_Date constants you're using aren't supported in that API call..

--Heidi

When upgrading between versions there is an upgrade database script to run.. please see:

http://www.konakart.com/docs/CreateDatabase.html#UpgradeDB

One way to upgrade is to download the zip install and inside that you will find the database upgrade scripts you need and all the new jars to copy over.

Another method would be to save your current customisations aside, then install the new version of KonaKart (specify the same database as you did before but don't load the tables this time);  run the db upgrade script(s) that are required to get from your old version to the new one, then finally you can copy back your own customisations.

(It's probably a good idea to quicky run the new version of KonaKart before you copy your customisations back in just to check that things are working as expected).

Which route you take is rather dependent on your starting position.

Note that we go to great lengths to maintain backwards compatibility at the API level... so your old client code should always work against the new versions.

If new features have been added to the client side in our storefront application in the new release that you want in your heavily-customised storefront, you should probably install a separate instance of KonaKart and refer to that to copy over the new features that you require.

From v4.2.0.0 you can configure the Admin App to work in mulitple languages at the same time.   In the Enterprise version you can switch between your supported languages dynamically.

Take a look at the AdminMessages.properties file (konakartadmin/WEB-INF/classes)

You can define strings for these configuration titles which will override the database values. eg. for the configuration title you mentioned you would set this property:

#cfg.title.MODULE_PAYMENT_AUTHORIZENET_STATUS  = Enable Authorize.Net Module

You can set the configuration title and description using this flexible method.

--Heidi

There are properties files for these translations.  Look at the module sources in your download package.. under

custom\\modules\\src\\com\\konakart\\bl\\modules\\payment\\*

Hi Joe,

What you're asking is beyond the scope of what I'm able to provide on this forum... we would be able to help with that kind of question as part of a consultancy or support arrangement however.

Don't forget you have custom fields on the product which you could use to save seller details.  This might be sufficient for your needs?

What you're trying to acheive is perfectly feasible however.

You wouldn't have to set the users to Admin Users manually if you set them up as Admin users when they signup.  (Obviously you would want to assign them an appropriate role so that they could only do what you allow them to do).

You have a choice but I think the new entry form in the storefront for adding user products is best for this.

--Heidi

You can do this kind of thing by making the users administrator users.  From the Admin App help page on Edit Customer:

The Customer Type may take one of three values:
1. An Administrator User
2. A Standard Application Customer
3. A Default Customer.

An Admin User can also log into the application normally.

Also.. you will want to set up a new role for this kind of user - say AddProductRole - that allows one of these users to insert a new product but not change anything else like all the store's configuration values or delete users etc!  Once you've set up this role you assign it to the user.   Check out the role based security in the Admin App.

Another possibility is to create a product input page in the storefront application and insert the product using the Admin API.

--Heidi

You can find the codes in the source files that are included under modules in your download package:

Code Select Expand

C:\Program Files\Kona4100c\custom\modules\src\com\konakart\bl\modules>findstr /s /n /c:"String code =" *.java
ordertotal\productdiscount\ProductDiscount.java:61:    private static String code = "ot_product_discount";
ordertotal\shipping\Shipping.java:47:    private static String code = OrderTotalMgr.ot_shipping;
ordertotal\subtotal\Subtotal.java:48:    private static String code = OrderTotalMgr.ot_subtotal;
ordertotal\tax\Tax.java:48:    private static String code = OrderTotalMgr.ot_tax;
ordertotal\total\Total.java:46:    private static String code = OrderTotalMgr.ot_total;
ordertotal\totaldiscount\TotalDiscount.java:60:    private static String code = "ot_total_discount";
payment\authorizenet\Authorizenet.java:57:    private static String code = "authorizenet";
payment\bluepay\Bluepay.java:52:    private static String code = "bluepay";
payment\chronopay\Chronopay.java:50:    private static String code = "chronopay";
payment\cod\Cod.java:46:    private static String code = "cod";
payment\elink\Elink.java:48:    private static String code = "elink";
payment\epaybg\Epaybg.java:54:    private static String code = "epaybg";
payment\payjunction\Payjunction.java:57:    private static String code = "payjunction";
payment\paypal\Paypal.java:64:    private static String code = "paypal";
payment\usaepay\Usaepay.java:51:    private static String code = "usaepay";
payment\worldpay\Worldpay.java:53:    private static String code = "worldpay";
payment\yourpay\Yourpay.java:61:    private static String code = "yourpay";
shipping\digitaldownload\DigitalDownload.java:50:    private static String code = "digitaldownload";
shipping\fedex\Fedex.java:143:    private static String code = "fedex";
shipping\fedex\Fedex.java:1407:                String code = codeArray[i];
shipping\flat\Flat.java:55:    private static String code = "flat";
shipping\free\Free.java:48:    private static String code = "free";
shipping\freeproduct\FreeProduct.java:52:    private static String code = "freeproduct";
shipping\item\Item.java:57:    private static String code = "item";
shipping\table\Table.java:60:    private static String code = "table";
shipping\ups\Ups.java:123:    private static String code = "ups";
shipping\ups\Ups.java:1304:                String code = codeArray[i];
shipping\usps\Usps.java:176:    private static String code = "usps";
shipping\usps\Usps.java:1168:                String code = codeArray[i];
shipping\uspsint\Uspsint.java:140:    private static String code = "uspsint";
shipping\uspsint\Uspsint.java:1185:                String code = codeArray[i];
shipping\zones\Zones.java:63:    private static String code = "zones";
--Heidi

Hi Jérôme,

PCI compliance is a lot more than just the software being used.

The rules for PCI compliance fall into are six major categories within the standards established by the PCI Security Standards Council, which are as follows:

* Build and maintain a secure network
* Protect card holder data
* Maintain a vulnerability management program
* Implement strong access control measures
* Regularly monitor and test networks
* Maintain an information security policy.

Within these six categories are 12 requirements that address particular issues and that are directly related to web application security:

1. Install and maintain a firewall configuration to protect card holder data
2. Do not use vendor-supplied defaults for system passwords and other security parameters
3. Protect stored card holder data
4. Encrypt transmission of card holder data across open, public networks
5. Use and regularly update anti-virus software
6. Develop and maintain secure systems and applications
7. Restrict access to card holder data by business need-to-know
8. Assign a unique ID to each person with computer access
9. Restrict physical access to card holder data
10. Track and monitor all access to network resources and cardholder data
11. Regularly test security systems and processes
12. Maintain a policy that addresses information security.

KonaKart can be implemented as part of a PCI-compliant service...if all of the above satisfied.
With KonaKart you have the choice of not storing credit card details or storing them in an encrypted fashion.
You also have the choice of using SSL for secure communication of data across networks.

--Heidi

The section on Custom Credential Checking in the User Guide could be helpful for this:

http://www.konakart.com/docs/CustomCredentialChecking.html

--Heidi

Hi,

I've read that you can solve this by using inline CSS, eg. <div style="font-size:8pt;padding:3px;"></div>

Not ideal... it's really gmail that's not observing the standard here.  Don't know if they plan to fix that.

--Heidi

Hi,

Thanks for posting your own solution and your suggestion.

Thanks also for the Italian translations.  Translations are always very welcome - please post to our Contributions board, thanks.

--Heidi