Solutions for translating custom fields

  • Resolved sofysoares

    (@sofysoares)


    10 months, 2 weeks ago

    I’m developing a website in Portuguese using Elementor Pro, Pods Custom Post Types plugin, with custom taxonomies and custom fields.

    After finishing the site in Portuguese, I translated it into English using the WPML plugin, and everything seemed fine—except the custom fields were not translated. When I started trying to translate those fields, the pages where they appear began causing critical errors on the site or layout issues. It seems the pages can’t properly load the translations of those custom fields.

    I’ve tried several different solutions, but nothing has worked. Do you have any suggestions for alternative configurations, or do you know if there are any incompatibilities between these tools, plugins, fields, loops…?

    Thank you.

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

Viewing 1 replies (of 1 total)
  • Plugin Support pdclark

    (@pdclark)

    8 months, 1 week ago

    Details for WPML may be best discussed with their paid support team, as the source code is not publicly available.

    Other users have had some success with https://ww.wp.xz.cn/plugins/polylang/ , although multilingual use cases on custom datasets can be expansive and complex.

    WordPress multisite is another approach: https://learn.ww.wp.xz.cn/lesson/setting-up-a-wordpress-multisite-network/ : it tends to simplify multilingual configurations when each language has its own sub-site. Multisite configurations are not without nuance, but it tends to be a widely tested approach to related content within a single WordPress instance. Another approach is to separate single-site WordPress configurations within subdomains or subdirectories. This increases compatibility with plugins not ideal with multisite, but does loses shared user table functionality default to multisite.

Viewing 1 replies (of 1 total)

The topic ‘Solutions for translating custom fields’ is closed to new replies.