Kryptronic Software Support Forum

Second the request!  I would really like a relatively easy way to have multiple languages available to the customer, as our business is worldwide.  Even if we, as the site developer, have to provide all the translation, if the capability was built into the new CCP, that would be a real plus!

So does that mean if I want my shop to be available in German, French, and Spanish in addition to English, I have to buy 3 more CCP licenses?

In addition to the issue of multiple licenses, does that mean you'll need multiple databases as well?  I assume you would, so that product descriptions can be different in each language.  Presumably then, in that scenario, your orders would be seperated into seperate databases depending on the language the user chose?  Sounds kind of cumbersome to manage, but please correct me if I'm not understanding the process correctly.

Thank you for the clarification.  I think I understand what you mean in terms of management and I definitely see your point about what drove the current path.  But just so I'm clear on what I'm in for, having multiple languages will basically be the same as managing two entirely seperate ecommerce sites, right?  I guess the only real issue then would be to make sure I have unique order number schemes (number prefix, probably) for each storefront so that I don't end up with duplicate order numbers for what are basically two presentations of the same store.  Or would it be possible to configure it so the two stores use the same order tables (tracking and trackitem in 5.1 nomenclature), making only one order list for both language versions of the store?

Thanks for the information Nick!

1) So basically out of the box, CCP6 only supports 1 language. (much like what is on the current CCP5)

Correct.  Translated versions will be made available at a later date.  They take time to formulate.

2) To get 2 languages, we need the main domain (eg. abc.com) and let's say to support spanish we need sub-domain (eg. sp.abc.com) and so on...

3) Basically both will be on separate database and have to be administered separately, out of the box... (though we can hack CCP6, but not recommended for layman)

Incorrect.  One domain and one database account is needed.  You will install two applications on your single domain / single core that uses a single database account.  You'll administer all apps using the same URL and the same backend interface.

4) So customer cannot order in English and Spanish at the same time... both will appear as separate order.. (i.e. 1 order at abc.com and 1 order at sp.abc.com). In other word, the cookie that store persistence on abc.com and sp.abc.com will not mix...

They would link into a separate store.  And shop in just that store.  Basically on the home page they would choose the link for the store they want to shop in.

5) So basically we have 2 stores to manage each which its own inventory and should not be mixed, think it like 1 HQ and 1 branch.

Correct.

6) We can use the same order code for both store, but we need a way to mark whether it is from abc.com or sp.abc.com (maybe the title on the invoice should be typed as ABC Inc. (EN) and ABC Inc. (SP) )

7) If not it will be better off to use order code with some prefix.... eg. abc.com ==> order code EN001-002, and sp.abc.com ==> order code SP001-002 (i.e. it is the same order number but with language prefix)...

Use of a different order number prefix will suffice.  The customer will have access to all the orders using their customer account to view orders.  Each order link would direct them to a different store (that originated the order).

8) Sure this is very cumbersome to manage...  BUT a separate 2 stores to manage (1 HQ and 1 branch) is sure better way to manage than 1 store with jumble-up languages all over the place if some no-brainer customers keep on jumping from language to language when online shopping...

That's why we went this route.  Not many users will be going multi-language so we did not want to jumble everything up for them.  And for those that do, this is the cleanest way to do it providing the most user friendly shopping experience for customers.

9) At least when these no-brainer customers jump from language to language they end up with multiple store order... which they will be forced to stick with 1 language in order to consolidate their order to just 1 store...

10) So this is a no-winner problem... OK I can live with CCP6 solution (1 language - 1 licenese), albeit the hole in the pocket.... a small amount compared to multi-jumble-up order with inter-mixture of languages in the order / invoice..

If direction is given to the customer on an entry page (shop here in English, shop here in Spanish, etc.) then you eliminate that confusion right off the bat.  This should be done like an automated phone system does right at the start (press 1 for English, press 2 for Spanish) without giving the option to jump back.

OK here is what I understood..

1) 1 language - 1 license....

============================================
eg. we need 3 languages (English, Spanish, French)

a) Only 1 database is needed however ....

b) But need to install on 3 directories (/public_html/store) (/public_html/store/sp)  (/public_html/store/fr)

c) Each installation need to be run separately and individually activated... i.e. we install CCP6 for 3 times but for each time we specify different directory but specify the same database

=================================================================================================

So we get:

a) One customer account can access all orders in all the 3 languages. Hence with the same username-password, we can access all 3 separate language stores.

b) However no order will inter-mix with different language... i.e. English order will not mix with Spanish order, etc....

c) This create some management problem though.. we end up with 1 HQ store (English) , 1 branch store (Spanish), 1 branch store (French).. each with it own separate inventories count...

d) However we will be able to access all 3 stores in just 1 admin area....

==========================================================

So in summary we got:
a) 3 separate stores (3 separate licenses)
b) 1 customer account for each username-password which can access all 3 stores
c) 1 admin control panel


There won't be situation where we will end-up in the NO-NO-SITUATION of:
a) 3 separate stores (3 separate licenses)
b) Each customer need to create 3 different account for each language
c) 3 admin control panels for each language

As I understood it, the customer would need a seperate account for each store.  I think it would be basically the same as three entirely different sites - there really is NO multi-language support in the new version that I can see.  The only advantages would be that Nick seems willing to give discounts for multiple installations and that all three stores would be accessible from the same admin URL, which is the same situation you'd have if you had 3 totally independent stores selling different things.  You'll be in the same admin, because of the unified KHXC backend, but you'll have three seperate inventories to control (which doesn't really work, since the inventory probably won't be laguage specific) and you'll have three seperate lists of orders to fill.  Presumably, you'll also have to pay for 3 skins and 3 copies of any customer-side mods you might get from third parties.  I have to say, I'm not too happy with that solution - I would have preferred some sort of language file solution.  Almost all desktop software can manage it that way, and while I'm no web app expert, I don't understand why the same approach couldn't be utilized for CCP.  Maybe proper multi-language support will be available in the form of an add-on module at some future date.

Actually the customer accounts and skins are all unified under the KHXC interface.  If your skin is built to handle multiple stores (the default one is) then the same skin can be used for all three stores (or you can clone it at will and assign copies to different stores with different content).

The problem (as stated above) with just using language files is that you end up with a mixed interface.  You have instructions and messages in one language and products in another.  Multi-language implementations in other programs that use the language file approach are not very user friendly as a result.

ncp wrote:

Repeating on the post 3 years ago... Will there be multi-lingual support in CCP7 ???

Negative

Negative