Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:

If you're trying to activate 'Custom Fields Translation' in WPML and cannot find the option in WPML → Settings, it might be due to the type of your subscription.

Solution:

We recommend checking your subscription type. The 'Custom Fields Translation' feature is available only with the 'Multilingual CMS' subscription, not with the 'Multilingual Blog' subscription. If you have the latter, you will need to upgrade your subscription. You can do this at WPML Purchase.

If this solution does not apply because it might be outdated or not relevant to your case, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 1 reply, has 0 voices.

Last updated by henrikR-17 3 weeks, 6 days ago.

Assisted by: Shekhar Bhandari.

Author Posts
December 18, 2024 at 6:47 pm #16527255
December 19, 2024 at 7:35 am #16528553

Shekhar Bhandari
Supporter

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

Thank you for contacting WPML support. I'd be happy to assist you on this issue.

Custom field translations is not available with the subscription type "Multilingual Blog" you have, you will need to upgrade the subscription to Multilingual CMS to use that feature. https://wpml.org/purchase/

Let me know if this helps.

Thanks

December 19, 2024 at 12:11 pm #16529970

henrikR-17

OK. Thank you.
You and I and Astra Theme support might have saved some time, if my plugin was named "WPML Multilingual Blog" and not "WPML Multilingual CMS". 😉
In that case I and Astra would not have thought that "Custom Fields Translation" just needed to be turn on...