Justin,
Many thanks for your prompt reply. I think a fundamental challenge is that there are 3 vendors involved: WP, Widgets Reloaded and WPML. I’m not expert enough in WP to know exactly why the following is happening:
MY GOAL
– set up 2 groups of categories, each with their own child categories (this works fine using WP / Widgets Reloaded when I am only using English).
– implement multi-language support (not sure about other vendors, but WPML uses a separate cat id for each instance of a category – lang).
CAT ID’s
Sorry for the confusion. I have been using cat id’s with Widgets Reloaded and that has not been a problem (at least, when there is only 1 lang).
But note that, at least when using WPML, WR (and I assume native WP) needs to have separate hierarchies for English and Chinese, since each parent has its own cat id (see example below).
EXAMPLE
Parent Category A
English Cat ID = 11
Chinese Cat ID = 21
Parent Category B
English Cat ID = 12
Chinese Cat ID = 22
Child categories are not an issue, other than, when i set up the child categories in an alternative language, the translated categories have to be “pointed to” the alt language parent categories (in this case, Cat ID 21 and 22, respectively).
WPML and WR
For some reason, WPML can detect the existence of child categories and display the correct translations. But it cannot correctly detect and display the parent categories. So when a user selects an alternative language (e.g. Chinese) the result is:
– Category Group A (still displays in English)
—- Child Category 1 (correctly displays in Chinese)
—- Child Category 2 (correctly displays in Chinese)
– Category Group B (still displays in English)
—- Child Category 3 (correctly displays in Chinese)
—- Child Category 4 (correctly displays in Chinese)
The problem is not the admin translation – i have successfully translated all parent and child categories. The problem is that WP / WR / WPML cannot detect a parent and display its translation.
STRUCTURAL ISSUE
I’m new to WP, so if this comment is not correct, please disregard.
Most s/w with integrated multi-language implement translations, including primary language, as a child of any entity or attribute. So, categories would have a 1:M relationship with their respective translations. For example:
Category A (Cat ID = 11)
– EN translation (resides in a separate cat / translation entity)
– CH translation (resides in a separate cat / translation entity)
There would not be a separate category for each translation. One category : multiple translations.
It appears multi-language was added after the initial architecture for WP was designed. If I could make a suggestion, I think the WP team would be the most appropriate team to implement multi-language. It seems that all the 3rd party vendors are trying to “work around” the WP architecture, resulting in somewhat inconsistent behavior.