Hello Sampsu, first of all DAFS. You CANNOT create a new language just by copying the lang file into the lang dir and select it in admininstration. It doesn't work that way. Try following:
try this on a clean English/Polish install of QC. I use Italian lang file as a demo here.
- chmod all required directories and files, including config/ and lang/ - create a new language in the administration, name it as IT - then copy the italian translation file it.php to the lang/ directory, overwriting the existing it.php - then set the language IT as default for webshop in the administration>settings>options and also as the default administration language (those are two different drop-downs) - you will have to manually create all relevant pages, like search page, basket, order form page, etc. It's not that difficult, do it in the administration>pages - you will need to set the default pages for search, order form, basket, etc. in the administration>settings>page
Then it should work.
And here is the second, easier solution: If you want only 1 language in your e-shop, just substitute the content of files lang/en.php and config/lang_en.php for italian content. And translate the names of the pages in the administration. That's the easiest way. The default language would be 'en' - but it would actually be the italian translation.
concerning adding old products -- converter should work, but if it doesn't, perhaps I could be of service, e-mail me at http://nlp.sk/antispam/
QC v3.x
sampsu
2008-06-04 14:36
but does db/ have to be empty for all fi_ files ?
Why is that made so hard, when the 2.x and 1.x versions were aesy to install any language.
sampsu
2008-06-04 15:07
Ooo
I just realized that there really is this "greate new language" in admin section.
But that doesnt work right, it makes fi.php file to lang/ folder, but givs only 644 righs for that and owner is some strange. So that file is useles =)
And when doing it the "old" way and copy all neccesery files with FTP program to server (ingluding fi.php) it giwes the errors i wrote earlier.
your questions and comments are actually pointless. 664 should be allright, if the PHP scripts can write to the files. You can always copy the '664 files' to your disk, then delete them on the server, then upload them back and chmod them 777.
Again, you cannot set up language the old way, just by copying 1 file.
QC v3.x
sampsu
2008-06-04 19:14
ok.
thanks that worked (deleting that one owned by server only and uploading new that was owned by my user)
But how about the old products. What name is the file that should contain products. because i only see old orders in admin area.
I wouldn't recommend a conversion by-hand unless you know EXACTLY what you are doing (your questions indicate that you're a little inexperienced). Either use the script or hire someone to help you.
QC v3.x
Harly
2008-07-11 23:55
The solution is: 1) Download the language-file you want (e.g. "fi.php"). 2) Rename the "fi.php"-file to "en.php". 3) Upload and overwrite the "old" "en.php"-file with the correct language for your country/nation, and now your ready to continue with the newly changed language working on your site! NOTE: If you experience any letters, who dosen't show as they should, like I did with the letters æ,ø and å from the danish language, you just correct this in: Languages -> your language (e.g. "fi"). Ajust the sentenses to the correct special letters of your country/nation and save the changes. That's what I did, and it worked like a charm!
P. S. Administrators of the great CMS' of this site: The installation-instructions for the language-files is incorrect or obsolete. It simply dosen NOT work at all. But my way works fine! You may want to look into this soon, so no one else have to go through the same hassel that I did, before I found my own way of doing it right.
P. P. S. I really like your products, the CMS and the Quick Cart. Very nice work guys!
Respectfully, Harly.
Harly
2008-07-12 00:08
Additional notes: Remember to KEEP the default settings on "en"; because this is the language-file that you've changed, and renamed, you don't have to cange those settings. Just a little reminder, folks!
Respectfully, Harly.
Harly
2008-07-12 11:34
This is the wrong or obsolete installation-instruction, that I found on the Translation-download-site: (Do NOT follow these instructions!!!)
"------------------------------ Quick.Cart by OpenSolution.org www.opensolution.org ------------------------------
HowTo install new languages in Quick.Cart ------------------------------ step 1) download file from http://opensolution.org/download/ step 2) unzip file on Your local drive step 3) log to admin panel and add new language step 4) copy (overwrite) file (*.php) to "lang/" directory
now You can edit config/general.php file and change language ($config['language'])"
Just to let you know where I found the INCORRECT Instructions!
Respectfully, Harly.
Zeddy
2008-07-22 09:57
Ok, but what if i do not wish to overwrite the existing languages, or for example add three new languages, how do i go about then?
add them in administration, like this, one by one: - create a new language in the administration, name it as IT - then copy the italian translation file it.php to the lang/ directory, overwriting the existing it.php - then set the language IT as default for webshop in the administration>settings>options and also as the default administration language (those are two different drop-downs) - you will have to manually create all relevant pages, like search page, basket, order form page, etc. It's not that difficult, do it in the administration>pages - you will need to set the default pages for search, order form, basket, etc. in the administration>settings>page
I experimented a lot of trouble migrating from 2.2 to 3.2 but I am not supposed to talk about paied versions here, so let me just talk about the language issue and a 2.x to 3.x migration.
a) There is an architecture issue within QC. The problem is that some non data files are today language related. Example : if you take a demo version of QC, then ask for creating a new language, you have to go to the settins menu then create the file (this will create all empty database files for this language), then fill in the translated message file. When you are done, choosing the new language causes all the architecture of the site to disappear. Why ? Because the architecture files contain the prefix of the language. To me, this should not be implemented that way. Swapping from one language to another one should ONLY change the language text and NOT deal with architecture (what the implementers call DESIGN in the migration HowTo document, which is wrong. Design is choosing colors and position of objects in pages, not creating or deleting pages, but I'll come back on this other issue later)
b) the current architecture of QC is made that way :
admin related files : language independent architecture related files : language dependent database files : language dependent
To me, it should become (in a new major release of the product)
admin related files : language independent architecture related files : language independent database files : language independent
Why ? because changing a language preference on a web site should have nothing to do with the site itself, only with the ability for a visitor to understand what is printed on his/her screen.
Again, this is my opinion after 30 years of IT consulting :-)
The ONLY example I know of a language related "design" is a Hong Kong site which does not offer exactly the same products when swapping from English to Japanese. And in this particular case, the architecture of the site is not at all affected by the language change. Only the data displayed.
c) Until I have completed successfully my own migration and fully documented the fixes to include in the HowTo, here is a suggestion to easily succeed in implementing a new language :
1° fully build the site in English or Polish (both have the same architecture) then test it (mainly the paiement stuff)
2° go to the settings menu and ask for a new language creation. This will create (among others) a new messages text file, that you'll have to translate (if not already available in the DL area of the OpenSolution site). WARNING : for paied versions, language files are NOT compatible from say 3.0 to 3.1 or 3.1 to 3.2 upgrade or for standard to Pro or Pro to EXT migration)
Some vocabulary commonly used in the IT world : Architecture : the way the site is built in terms of pages and navigation Design : colors and objects on a page Migration : moving from a major release to another major release. Ex.: 2.x to 3.x or Standard to Pro, or Pro to EXT Upgrade : moving from a minor release to another minor release. Ex.: 3.1 to 3.2
3° when you have your new language set up, the program will have created for you all database files for this new language. Now you have to get your architecture done for this new language. To do that, just duplicate all missing files with the new language prefix from say the en_ files. This will build an architecture identical to the existing one. Then, go to the settings menu, select the new language for the default language, and your site will be exactely the same whatever language you choose
4° as the new database files are empty, you need now to convert your old database to its new version, using the appropriate conversion utility available in the DL area of the OpenSolution site.
5° test all of it, should be fine.
I consider starting a forum on all this because the current forum from Open Solution cannot be ordered by categories, making searchs difficult. I do not say it is not good, everyone has understood my concern :-)
Talk to you later, Pals. And thanks again to OpenSolution for this product.
