Lang Export / Import Results: Not Quite The Same
|
Posted
#71040
(In Topic #14987)
|
|
|---|---|
|
Fan in action |
I noticed that "export language pack" exported everything in "lang_custom/JA" but not "pages/comcode_custom/JA" Or "site/pages/comcode_custom/JA". So I exported those by file instead. When I imported to the local machine and displayed the site in Japanese, some things were translated, somethings weren't (still displaying in English). I was wondering if I had missed exporting some files, or if something wasn't listed in the "Export Files" list. I also noticed that in the Admin Zone, most of the Admin menus were displaying in Japanese except for some items under the "Content" menu : Contacts, Frequently Asked Questions, Hosted Sites, Links, Modifications, Products, Super-Member projects. The rest of the items in this menu displayed in Japanese properly. On my local machine, all admin menus and their items are displaying in Japanese 100%. I exported files from these folders: "lang_custom/JA" "pages/comcode_custom/JA" "site/pages/comcode_custom/JA" I have included comparison screen shots for reference. Notice that the top menu and side panels are still displaying in english on the target machine. What did i miss in the language export/import process ? Thanks, SJ |
|
Posted
|
|
|
Community saint |
I'm just taking a guess here but all of those items are catalogs/catalog entries. You might need to export/import those separately. Bob |
|
Posted
|
|
|
Fan in action |
I thought I would check to see if there were any files I may have missed, so I focused on the left side panels. I searched for the keyword "GUESTBOOK" (Features panel, left side). This is what i found in global.ini (EN) GUESTBOOK="Guest Book" (JA) GUESTBOOK="" I am at a loss. The left side panels on the site page (local machine, displayed above) clearly shows everything displaying in Japanese, including the translation for 'Guest Book', yet when I check global.ini the entry is blank. It all displays fine on my local machine, but…I am not sure how. And I still need to figure out why its not completely displaying on the target machine. |
|
Posted
|
|
|
ocStaff (admin) |
If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource. |
|
Posted
|
|
|
Fan in action |
In the "ocpX_translate" table to be precise. I guess some of the translation is saved to file and some is stored in the db. If I export the ocpX_translate table and import it on my target test machines, would that be enough to complete the language transfer, or are there other tables that would also need export ? Also, I have a small problem. No idea how it happened. I upgraded ocportal on all machines. The target machines ocp database properly says ocp7_XXXXXX for each table. But my machine's ocp database (which has ALL the Japanese properly displaying) says ocp6_XXXXXX. I checked the ocp upgrade tool, and it says the database version is 7.1 (current), so there is nothing to upgrade. I have no way to re-upgrade/force upgrade the db to version 7. If you know a workaround for this let me know. [UPDATE]We re-translated all the missing stuff on a different machine, so we won't worry about importing from my funny database. So, that is taken care of. Thanks, SJ
Last edit: by samurai_jack
|
|
Posted
|
|
|
ocStaff (admin) |
A few points here… Guestbook is a Comcode page, so primarily is stored as the .txt file. You're actually looking at the caching – so if the Comcode Page cache is emptied it will clear that out and read it from disk again. Content is stored in ocpX_translate also, but these won't be contained in a 'language pack'. This is similar to what I mentioned in my last post: default content will be created in Japanese when you install, if Japanese is installed when the installer is running. 'ocp7_' is a table prefix and does not mean that you are actually running ocPortal 7. It is the default table prefix when v7 is installed, but we don't rename tables when you upgrade so it only means what you originally used. This has confused other people too, so we'll just make it 'ocp_' in the future for new installs. If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource. |
1 guests and 0 members have just viewed this: None
Control functions:








Last edit: by