Text strings aren’t translatable or plugin ignores multilingual frameworks.
Plugin Doesn’t Support Translations or Multilingual Setup
Key Points: You can’t translate plugin strings, or it conflicts with WPML/Polylang/TranslatePress.
You build a bilingual site — but the plugin insists on showing buttons and messages in one language only. Or worse, it breaks translations across your site. That’s poor i18n/l10n support.
🌐 Root Issues
- Plugin doesn’t use
__()or_e()functions for strings - No
.potfile or translation domain provided - Plugin conflicts with language switchers or translated URLs
🛠️ Fix or Workaround
- Check if plugin offers language packs via WordPress.org
- Use Loco Translate or Poedit to manually translate strings
- Contact author to request proper localization support
📢 Note
Multilingual sites depend on cooperation between theme, plugin, and translator — even one outlier breaks the experience.