Messages

Use a Virtual Private Hosting plan. This gives you the capability of setting up your environment yourself the way you like.

There is no risk if you do it right. In konakart/database/YourDatabase you will find a full line of upgrade sql scripts that go from version 2.2.0.3 up to version 5.2.0.0.

Be careful not to skip any release step and it will work well. I've tried it. Keep a backup somewhere, to be on the safe side.

[Import Eclipse Project]

Once you have created your Eclipse project, you can use Netbeans, if you "Import Eclipse Project" and then select "Import Project ignoring Dependencies". I use Netbeans 7, but it should work for Netbeans 6.9.1 as well.

[jsp/CatalogShippingAndReturnsBody.jsp]

In webapps/konakart/WEB-INF/jsp/InformationTile.jsp you find the links:

Code Select Expand

<html:link page="/ShippingAndReturns.do"><bean:message key="information.tile.shippingandreturns"/></html:link><br>
<html:link page="/PrivacyNotice.do"><bean:message key="information.tile.privacynotice"/></html:link><br>
<html:link page="/ConditionsOfUse.do"><bean:message key="information.tile.conditionsofuse"/></html:link><br>
<html:link page="/ContactUs.do"><bean:message key="information.tile.contactus"/></html:link>   

If you go to the struts-config.xml file you will find this action definition: 

Code Select Expand

<action path="/ShippingAndReturns" type="com.konakart.actions.ShippingAndReturnsAction">
<forward name="ShippingAndReturns" path="/CatalogShippingAndReturnsPage.do"/>
</action>
and:

Code Select Expand

<action path="/CatalogShippingAndReturnsPage" forward="catalog.shippingandreturns.page"/>

So look for jsp/CatalogShippingAndReturnsBody.jsp is the page you are looking for. Edit body-content-div.

You will need to also edit CatalogPrivacyNoticeBody.jsp, CatalogConditionsOfUseBody.jsp and CatalogContactUsBody.jsp.

Yeah! Tell me about it...   

Have tried a few things:
1. AdminMessages_el.properties with ISO-8859-7. Did not work either.
2. I moved the AdminMessages_el.properties (with \uNNN encoding) to AdminMessages.properties and everything started working.
3. I moved the AdminMessages_el.properties with ISO to AdminMessages.properties and it displayed garbage.

For some mysterious reason, although the necessary XML files are all updated and correct, the Admin-app does not switch locale automatically.
I will have to stopkonakart, move the file and startkonakart again. I can certainly live with that, since nobody needs to change the language
of admin very often. Still i remember the times (around version 2.2.x.x and 4) when i could switch the locale from "Languages" and only needed to log-out.

Thank you very much. The funny thing with 5.2.0.0 is that i managed to get it to work OK in Windows-XP with the \u characters in the Messages file.
The switch from English to Greek works only after a reboot. I Ubuntu it doesn't work at all. It just shows the status words in Greek in the "My Store Status" page,
but these come from the database. Like that:

My Store Status
   
Άκυρη Πληρωμή Orders               0
Ακυρώθηκε Orders                     0
Απεστάλει Orders                       0
Απεστάλει Μερικά Orders             0   
Πληρωμή Ολοκληρώθηκε Orders   0   
Σε Αναμονή Orders                    0   
Σε Αναμονή Πληρωμής Orders      0   
Σε Επεξεργασία Orders               0   
Number of Customers                 4   
Number of Products                   0   
Number of Manufacturers            1

[ascii2native]

For all previous KonaKart i had to use for greek UTF-8. In order to convert i had to either use ascii2native filter or the property file editor of NetBeans in order to "i18nize" my Administrator.
Should i convert the messages to ISO-8859-7 (greek) and try to use them straight away? If this works then the file should be editable throught the Administrator editor.

[German]

Here are is a small part of the AdminMessages_de.properties and below it one of AdminMessages_el.properties.
In the german file you can see Umlaut ans Es-Zet, used directly and unencoded.

In order to make the greek Administrator work, we must provide the \uNNN encoding. Why is there a difference?
This makes processing of the AdminMessages_el.properties impossible through the Administrator.

German

Code Select Expand

#--------------------------------------------------------------------------------------------------
# Admin Message Catalogue
#--------------------------------------------------------------------------------------------------

#--------------------------------------------------------------------------------------------------
# General
#--------------------------------------------------------------------------------------------------

application.title               = Shop - Administrationsoberfläche
language.dir                    = de

#--------------------------------------------------------------------------------------------------
# buttons
#--------------------------------------------------------------------------------------------------

button.add                      = Hinzufügen
button.add.var                  = Neu
button.add.group                = Gruppe
button.addPoints                = Add Points
button.addr                     = Addresses
button.addToProm                = Verwalte Sonderaktionen
button.api.calls                = Zeige API Aufrufe
button.back                     = Zurück
button.cancel                   = Abbrechen
button.clear                    = Löschen
button.close                    = Schließen


Greek

Code Select Expand

#--------------------------------------------------------------------------------------------------
# Admin Message Catalogue in Greek
#--------------------------------------------------------------------------------------------------

#--------------------------------------------------------------------------------------------------
# General
#--------------------------------------------------------------------------------------------------

application.title               = \u0395\u03c6\u03b1\u03c1\u03bc\u03bf\u03b3\u03ae \u0394\u03b9\u03b1\u03c7\u03b5\u03af\u03c1\u03b9\u03c3\u03b7\u03c2
language.dir                    = el

#--------------------------------------------------------------------------------------------------
# buttons
#--------------------------------------------------------------------------------------------------

button.add                      = \u03a0\u03c1\u03bf\u03c3\u03b8\u03ae\u03ba\u03b7
button.addToProm                = \u0394\u03b9\u03b1\u03c7\u03b5\u03af\u03c1\u03b9\u03c3\u03b7 \u03c4\u03c9\u03bd Promotions
button.api.calls                = \u0395\u03bc\u03c6\u03ac\u03bd\u03b9\u03c3\u03b7 \u03ba\u03bb\u03ae\u03c3\u03b5\u03c9\u03bd API
button.back                     = \u03a0\u03af\u03c3\u03c9
button.cancel                   = \u0391\u03ba\u03c5\u03c1\u03bf
button.clear                    = \u039a\u03b1\u03b8\u03b1\u03c1\u03b9\u03c3\u03bc\u03cc\u03c2
button.close                    = \u039a\u03bb\u03b5\u03af\u03c3\u03b9\u03bc\u03bf
button.coupons                  = \u0394\u03b5\u03bb\u03c4\u03af\u03b1
button.delete                   = \u0394\u03b9\u03b1\u03b3\u03c1\u03b1\u03c6\u03ae
button.deleteOption             = \u0394\u03b9\u03b1\u03b3\u03c1\u03b1\u03c6\u03ae \u03b5\u03c0\u03b9\u03bb\u03bf\u03b3\u03ae\u03c2
button.deleteOptionValue        = \u0394\u03b9\u03b1\u03b3\u03c1\u03b1\u03c6\u03ae \u03c4\u03b9\u03bc\u03ae\u03c2 \u03c4\u03b7\u03c2 \u03b5\u03c0\u03b9\u03bb\u03bf\u03b3\u03ae\u03c2

Correction:

I was trying a greek Konakart 5.2.0.0 yesterday, and realized that administrator works correctly with an AdminMessages_el.properties file and no AdminMessages_el_GR.properties with just the following complaint:

PropertyFileFinder.findProperties() Could not find AdminMessages_el_GR.properties on the classpath

It seems that for the 5.2.0.0 version the internationalized AdminMessages.properties file has to be called AdminMessages_it_IT.properties otherwise KKE complains about it. Previous versions were satisfied with the AdminMessages_it.properties.

The ones that should not be translated are:

seo.product.category=category
seo.product.manufacturer=manufacturer
seo.product.name=name
seo.product.model=model

You find them at the top of Messages.properties.

You should not translate "category", "manufacturer", "name" and "model". Then your URL's will be built correctly.

We tried mochahost.com. They offer very good services at reasonable prices.

Thank you Brian!
You are absolutely right! I just wanted to post a new reply about it, but you were faster.

There has been a Virtuozzo-configuration issue by the provider, which was later repaired.

In the mean time we installed the 32-bit Konakart with the 32-bit Sun-JDK successfully on a 64-bit CentOS5.
Everything seems to be running smoothly and very fast too.

Do you think we should bother and switch everything to 64-bit?

Could the silent mode installation script of the 64bit Konakart be broken?
I installed, with more or less the same command, the 32bit version
and now konakartadmin runs perfectly well.