Skip to content Skip to sidebar

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 replies, has 0 voices.

Last updated by artakG 6 days ago.

Assisted by: Lauren.

Author Posts
February 11, 2026 at 9:34 pm #17814425

artakG

I am currently working with a WordPress site where the theme utilizes information from the "Dealer" user role to populate two different blocks on the dealer-specific pages.

While most of the data is functioning correctly, I am encountering a synchronization issue with the translation of the Nickname field.

The Goal: To have the user "Nickname" appear in the site’s secondary language across all theme blocks.
Current Progress: We have already implemented the translation for the nickname field using XML configuration.

The Problem: The translation is only partially successful.
Block A: Displays the translated nickname correctly.
Block B: Continues to display the original (default language) nickname, ignoring the translation.

It appears that one of the blocks is fetching the nickname data differently or bypassing the translation filter. Could you please help me identify why this specific string remains untranslated in the second block and provide a solution to ensure consistency across both sections?

February 11, 2026 at 10:40 pm #17814491

Lauren
WPML Supporter since 10/2015

Languages: English (English )

Timezone: America/New_York (GMT-05:00)

To confirm, please go to Users → Edit Dealer

Change “Display name publicly as” to something unmistakable like:
DISPLAYNAME-TEST-123

Visit the page where Block B is showing the wrong name.

If Block B changes to DISPLAYNAME-TEST-123, then Block B is definitely using display_name (not nickname).

Please let me know the results.

February 12, 2026 at 12:19 pm #17816911

artakG

The solution you suggested didn't work either. I've decided to simply hide that field, as the name is already displayed elsewhere. Thank you for your support.