[Resolved] Translate WP User Manager Multiple Select Field Values

Hi,

could you please share the exact URL of the page shown in your screenshot? I checked the link you provided, but the fields there don’t match what I see in your image.

I would eventually also need to request temporary access (WP-Admin and FTP) to your site
– preferably to a test site where the problem has been replicated if possible –
in order to be of better help and check if some configurations might need to be changed

Your next answer will be private which means only you and I have access to it.

❌ Please backup your database and website ❌

✙ I would additionally need your permission to de-activate and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important.

✙ Please add the Links to the […] Edit Screen, the Page/Post where you insert the […] and the corresponding Front End Page/Screen

Best Regards,
Marcel

Hi,

Thanks for the information!

First, please note that it isn’t possible to update a text domain. A text domain is part of the __() (getText) function that WordPress uses for translations. Changing it would require modifying the underlying code. You can find more details in the WPML documentation here: How to use gettext.

For example, in the linked documentation, you’ll see this format:

__( 'Thank you!', 'my-plugin-domain' );

The part after the string ('my-plugin-domain') is the text domain.

In your case, since you’re using a plugin that automatically handles those fields, things work a bit differently. I’ve scanned the text domain and can confirm that some strings (like “Advocacy”) don’t appear, while others (like “Consulting Specialization”) do show up in String Translation, but not on the frontend, as you mentioned.

Let’s check if this could be a compatibility issue. Please install the affected plugin on this hidden link">test installation along with its WPML add-on, and see if you can reproduce the issue there.

The plugin hidden link">documentation doesn’t indicate that any specific settings are required. It’s possible that the strings aren’t being called properly — for example, if the code is executed with the wrong priority.

If we can reproduce the issue, we can then look for a possible workaround or contact the plugin authors if needed.

Best regards,
Marcel

Hi,

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-user-manager domain was triggered too early.

This issue is related to a WordPress core function. You can find more details here: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/.

I’ll check your reproduction on the sandbox and forward it to our Compatibility Team. I’ll keep you updated on any findings.

Best regards,
Marcel

Hi,

we found two workarounds:

1) The first issue is a simple typo.
Open \wp-content\plugins\wpum-wpml\includes\class-wpum-wpml-fields.php

Line 20
Replace:

add_action( 'update_wpum_field_meta', array( $this, 'update_meta_strings' ), 10, 4 );

With:

add_action( 'updated_wpum_field_meta', array( $this, 'update_meta_strings' ), 10, 4 );

it's "updated" not "update"

- Go to "Users > Custom fields" and edit at least one of the options from that multiselect field.
- Go to "WPML > String Translation" and translate all options.

2) The second issue is that the plugin formats the field output as a comma-separated string. So we need to edit the code and translate each label using the textdomain from String Translation.

Edit ...\wp-content\plugins\wp-user-manager\includes\fields\types\class-wpum-field-multiselect.php

Replace the entire get_formatted_output() function with:

public function get_formatted_output( $field, $value ) {

		$stored_field_options = $field->get_meta( 'dropdown_options' );
		$stored_options       = array();
		$stored_index         = array();

		// Build lookup maps: value => label and value => original index
		foreach ( $stored_field_options as $key => $stored_option ) {
			$val = isset( $stored_option['value'] ) ? $stored_option['value'] : $key;
			$lbl = isset( $stored_option['label'] ) ? $stored_option['label'] : '';
			$stored_options[ $val ] = $lbl;
			$stored_index[ $val ]   = $key;
		}

		$values = array();

		foreach ( $value as $user_stored_value ) {
			if ( ! isset( $stored_options[ $user_stored_value ] ) ) {
				continue;
			}

			$label = $stored_options[ $user_stored_value ];

			// Determine original index for this option so we can match textdomain package
			$index = isset( $stored_index[ $user_stored_value ] ) ? $stored_index[ $user_stored_value ] : 0;

			// Translation via WPML. 
			$translated_label = apply_filters( 'wpml_translate_single_string', $label, 'wpum-fields-wpum-field-' . $field->get_ID(), 'wpum-field-dropdown_options_' . $index );

			$values[] = $translated_label;
		}

		return implode( ', ', $values );

	}

We’ll reach out to the authors so they can update their code. Please let me know if everything worked as expected on your end.

Best Regards,
Marcel