I’m experiencing an issue with WPML String Translation that only occurs on my production site.
Problem description:
String translations are applied only to the first translated string within a given text domain. As soon as I translate additional strings in the same text domain, those translations are not applied on the frontend.
Important details:
• All strings are correctly registered and translated in WPML → String Translation
• The issue affects only strings from the same text domain
• On localhost, everything works correctly (all strings translate as expected)
• The issue appears only on the production site
Production environment:
• WPML (latest version)
• WP Fastest Cache
• Cloudflare (admin is not cached)
• Translations are handled via String Translation (e.g. __('Text', 'theme'))
I have already verified that:
• The correct text domain is used consistently
• No custom caching of the admin area is enabled
• The strings exist only once and are not duplicated
• Clearing all caches does not resolve the issue
Given that this works perfectly on localhost, it looks like either:
• a caching-related issue affecting string loading, or
• a problem with how translated strings are stored or retrieved in production
Could you please advise:
1. Whether this is a known issue with caching/CDN setups
2. Which WPML components or database tables are critical for String Translation loading
3. If there is a recommended configuration for WP Fastest Cache + Cloudflare in this case
If needed, I can provide debug information or temporary access.
Thank you for your help.
Best regards,
Leoš Lang
The topic ‘[Closed] String translations working only for first string in text domain’ is closed to new replies.
