Viewing 4 replies - 1 through 4 (of 4 total)
  • Hello, usually such field should be set to “translate” in WPML > Translation Management > Multilingual Content Setup > Custom Term Meta Translation (because they are assigned to terms).
    Once this is done, it should be visible when you create a new translation job or re-send already translated element to translation again.
    You could also check in WPML > Taxonomy Translation – if it is shown there as well.
    If this is not happening, perhaps it would be a good idea to open a new ticket in our support forum at wpml.org so that we can investigate more in-depth of the cause of this.

    Thread Starter kjwuan28

    (@kjwuan28)

    Hello George,

    We have already tried that before but still it doesn’t show up when we tried again after your reply. Maybe I’ll open a ticket later.

    Thank you very much for your reply.

    i checked further the issue.
    It seems that this is not yet implemented properly and should be implemented in a future WPML version.
    At this time I cannot tell when this will be implemented.
    You can still translate without this interface manually by going to the taxonomy in the other language, provided that you selected that the meta field is set to translate in WPML > Translation management > Multilingual content setup > Taxonomy Translation

    Thread Starter kjwuan28

    (@kjwuan28)

    Hello George,

    Yeah I guess we can only go manually to the taxonomy. We’ll just wait for this feature to get implemented.

    Thank you very much!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Add ACF Fields in WooCommerce Multilingual Category Tab’ is closed to new replies.