Back to Community
Home / Community / Plugin → Translate multilingual sites – translatepress

Troubleshooting Missing Content and Translation Issues in TranslatePress

47 threads Sep 10, 2025 Plugin → Translate multilingual sites – translatepress

Content

Users of the 'Translate Multilingual sites – TranslatePress' plugin sometimes encounter issues where specific content, such as blocks, images, or text, does not appear or translate correctly on their multilingual sites. This guide outlines the most common causes and provides step-by-step solutions to help you resolve these frustrating display problems.

Why Does This Happen?

These issues often stem from conflicts with other plugins or themes, caching mechanisms, or the way dynamic content is handled by the translation process. Common scenarios include:

  • A new block or element is visible in the default language but missing in translated versions.
  • Images display correctly in one language but appear broken or show the wrong translation in another.
  • Previously translated content reverts to the default language or disappears entirely.
  • Specific elements, like WooCommerce cart messages or ACF dropdown values, are not translatable.

Common Solutions to Try

1. Perform a Basic Conflict Test

Plugin or theme conflicts are a frequent cause of missing content. To test for this:

  1. Switch your site's theme to a default WordPress theme, such as Twenty Twenty-Four.
  2. Deactivate all plugins except for TranslatePress.
  3. Check if the missing content now appears in the translated language.
  4. If it does, reactivate your plugins and theme one by one, checking after each activation to identify the conflicting software.

Important: It is highly recommended to perform this test on a staging site to avoid disrupting your live website.

2. Adjust TranslatePress Advanced Settings

The plugin's Advanced tab contains several troubleshooting options that can force content to be detected and translated.

  1. Navigate to Settings → TranslatePress → Advanced.
  2. In the Troubleshooting section, try enabling the following options one at a time, saving changes, and checking your site:
    • Fix missing dynamic content
    • Disable dynamic translation
    • Filter Gettext wrapping options
  3. After making any changes, clear all your site's cache (server, plugin, and browser cache).

3. Clear All Caching

Caching is a common culprit, especially for images that stop displaying correctly after a cache purge or for content that appears correctly for logged-in users but not visitors.

  • Clear any caching from your caching plugin (e.g., LiteSpeed, WP Rocket, W3 Total Cache).
  • Clear your browser cache or test the site in an incognito/private browser window.
  • If your hosting provider has a server-level cache (e.g., SiteGround Optimizer), clear that as well.

4. Check and Re-Translate Problematic Strings

For images or specific text strings that are not displaying correctly:

  1. Go to the TranslatePress translation editor.
  2. Search for the string or image URL that is not working.
  3. If a translation exists, delete it and re-save the correct translation.
  4. If the string cannot be found, it may not be detected by the plugin. The 'Fix missing dynamic content' option can sometimes help with this.

5. Investigate Database and Collation Issues After Migration

If problems began after migrating your site, there may be database inconsistencies. Errors mentioning Illegal mix of collations indicate a database collation conflict. This typically requires advanced database management to ensure all tables have consistent collation settings.

When to Consider a Rollback

If an issue started immediately after updating TranslatePress or WordPress to a new version, and the conflict test did not reveal a problem, the issue may be compatibility-related. As a temporary measure, you can roll back to a previous, working version of the TranslatePress plugin using a rollback plugin while waiting for an official update from the development team.

By methodically working through these steps, most common content display issues can be identified and resolved. The key is to test changes one at a time to pinpoint the exact cause.

Related Support Threads Support