asyaT

Problem:
The client needed to reopen a ticket because a custom field was not showing in the WPML Classic Translation Editor.
Solution:
We resolved the issue by adding the following code to the

functions.php

file in the child theme folder:

function wpmlsupp_7499_allow_translating_numbers( $is_translatable, $job_translate ) {
    $data = $job_translate['field_data'];
  
    if ( 'base64' === $job_translate['field_format'] ) {
        $data = base64_decode( $data );
    }
  
    if ( is_numeric( $data ) ) {
        return true;
    }
  
    return $is_translatable;
}
add_filter( 'wpml_tm_job_field_is_translatable', 'wpmlsupp_7499_allow_translating_numbers', 10, 2 );

This code allows numeric values, which are usually excluded, to be translated in the WPML translation editor.

If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues and verifying that you have the latest versions of themes and plugins installed. If the issue persists, please open a new support ticket with us.