Handling multilingual site (PODS, WPML)

  • Resolved soulwasted

    (@soulwasted)


    5 years, 9 months ago

    Hi.

    I am bit (bit more) struggling with proper displaying translations for client’s website. Development preview is here: https://strapa.cz/ivb
    (I can provide FTP credentials and Duplicator copy of this.)

    Original language is czech (CS) and second one is english (EN).
    There is an option in WPML ?Adjust IDs for multilingual functionality“ which I checked on. And this handles proper displaying pods for both languages in some cases. But in another cases it doesn’t work.

    One case is to show translations of a field which is relationship and that relationship is translated (has different text for CS and EN). CS language has set and filled everything. All custom fields — text, relationships. Some relationships are same in both languages (such as titles: PhD.,…). And this works fine.
    But some relationships has different translations. For CS “?editel” and for EN “director”. I set this just in CS. Doing this in EN is redundant. But here it is impossible for me to get values like this.
    More about it here: https://wpml.org/forums/topic/wpml-doesn-show-translated-relationship-custom-fields/

    If you have any suggestions or if you can cooperate with WPML guys. I would be very happy ??

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter soulwasted

    (@soulwasted)

    I didn’t mention links to differences in CS and EN:
    CS: https://strapa.cz/ivb/osoba/josef-bryja/
    EN: https://strapa.cz/ivb/en/person/josef-bryja/
    (this is just for testing, live web is here: https://www.ivb.cz/osoba/josef-bryja/)

    Plugin Contributor Jim True

    (@jimtrue)

    You brought this over to our Slack Support; the type of relationship you were doing was specifically to a taxonomy and that’s not supported in WPML or Polylang. Taxonomies should be associated to the custom post types and then the taxonomy would translate properly when set to be translated.

    After discussion, you had set the taxonomies to be relationships, because you wanted to limit to single selects. This is not the appropriate way to override Taxonomy input; there’s a code solution for that:
    https://docs.pods.io/code-snippets/change-taxonomy-input-to-single-select/

    The other item that dropped out of that discussion was Simple Custom Defined List relationships. Those can’t be translated since they are configured at the field level and have no capacity to support translation.

    If your simple list (like Title of person) is just to enforce structure, you’re better off creating a Custom Post Type called ‘Titles’, turn off the editor in Advanced Options, Supports, and set that field as a relationship to your Post type peoples. Then set the post type to be translated and it should automatically be selected for the appropriate language through the relationship field.

    Thread Starter soulwasted

    (@soulwasted)

    Jim, thank you for your assistance. You gave me a lot of good advices.

    I am still looking for a way how to display translated relationships.
    More here: https://github.com/pods-framework/pods/issues/5307.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Handling multilingual site (PODS, WPML)’ is closed to new replies.