Skip Navigation


Reported for: WPML Multilingual CMS 4.4.8

Overview of the issue

You might have problem visualizing the contents of a Visual tab in the Classic Translation Editor.

This was introduced by the WordPress 5.6 and it will be fixed in WordPress core:


Don’t hesitate to make a full backup of your site before proceeding.

We have currently 5 possible workarounds:

  1. You can use Advanced Translation Editor.
  2. Alternatively, you can also install the Enable jQuery Migrate Helper plugin.
  3. You can click the Text tab and then return back to Visual tab in the Classic Translation Editor interface.
  4. You can also:
    • Edit your  wp-config.php file.
    • Just after line:
      define( 'DB_COLLATE', '' );
    • Add this:
      define('CONCATENATE_SCRIPTS', false);
  5. Finally, you can add the following snippet in your functions.php theme file.
    add_filter( 'wp_default_editor', create_function( '', 'return "html";' ) );

32 Responses to “Visual Tab in Classic Translation Editor is not showing contents after update to WordPress 5.6”

  1. Going back and forth from Text to Visual does not work. For anyone having this issue, there is an easy short term fix until the developers get the upcoming release out. You simply need to install and activate Enable jQuery Migrate Helper plugin. This solves the problem by reverting to a depricated JQuery Migrate for plugins like WPML that are not written for the updated version that came with the WP 5.6 update. Bests!

    • Hello there,

      Thank you for sharing this workaround, however it may be caused by an issue from a previous WordPress update.
      We are working on it.

      Thank you for your understanding.

  2. Hello,

    I’ve installed and activated the Enable jQuery Migrate Helper Plugin on my site. And I checked again the page to translate my homepage, I still don’t see the fields to translate medias. Do I have to modify something else ?

    Regards, Jeremy

    • Hello Jeremy, what was the issue?
      I’m going to install the plugin now.
      It’s weird because it doesn’t happen in every page or product, the visual tab sometimes works, sometimes doesn’t…

  3. Thank you very much, you have solved the problem momentarily, I hope they will correct it in the next update

    Thank you very much great job.

  4. El error sigue estando y la versión de WordPress es 5.8, el tema es que avece carga y otras no. La verdad me parece que es una incompatibilidad de wpml con wordpress en si. Cuando estarían arreglando el problema.

    • Hola,
      De momento la errata sigue estando abierta, tan pronto tengamos novedades de nuestros desarrolladores avisaremos aquí y la maracaremos como resuelta.
      Gracias por tu comprensión.

    • We totally understand you but there is a limitation from WordPress Core. I recommend you to try our Advanced Translation Editor which not only solves this issue but also is more powerful and bring you a lot of tools for translating your site smoothly.

  5. Just wondering about the status of all of this.

    I am refitting an existing WPML WooCommerce shop with a new theme, and today, I tested out each of the four workarounds on both pages and products.

    The results:
    – workaround 1: messed up the entire existing translation.
    – workaround 2: works, but only after one or two page refreshes.
    – workaround 3: does not work. No matter how many times I click back and forth between visual and text, the visual option does not display the content.
    – workaround 4: this is a deprecated PHP function, and it causes three errors because the headers are already sent within WP standard files.

    The best workaround at the moment is to just open the page translation using the flag at the top bar, thus showing the entire page.

    This mess I cannot explain to my clients.

    If you read the page to which you’re referring regarding the WP bug, they consider it resolved. Doesn’t it have to do with the fact that WPML has not updated their plugins to the new version of jQuery WP is also using?

    Is there an update to this? When can we expect WPML to update jQuery?

    • Thank you for your report, Boris.
      If any of the workarounds here displayed works for you, please open a ticket in our support forum as it may be an edge case. In that way we will be able to help you better.

  6. So apparently this is still an issue, at least on my site. Will this be resolved as beginning to use Advanced Translator on existing site is not a feasible suggestion for moving forward.

    • I understand the confusion. The first workaround is to attempt any of the solutions here presented. However, if they don’t work in your website, we need to investigate further.

    • Hello there,
      This issue is not longer reproducible in a clean installation. Instead, it involves a wide range of themes and plugins, that’s whey we have recently updated this errata with a new workaround (4) attempting to cover more scenarios.
      We will keep this page updated as soon as we have more news.

  7. If it can be helpful.
    I’m having this problem as well and noticed that the problem occurs on litespeed servers. Basically if I take the same site and install it on a server without litespeed the problem doesn’t occur and the visual editor loads correctly.

    • Thank you for sharing your findings. Indeed, it seems there are some conditions regarding hostings or other third parties which creates the issue with WPML.
      Anyway, this should be fixed soon. In the meantime, don’t hesitate to use workaround number 4 which has helped recently many other users.

  8. Hello,

    I am using this workaround:

    add_filter( ‘wp_default_editor’, create_function( ”, ‘return “html”;’ ) );

    It seems to work but Query Monitor says: Function create_function() is deprecated

    Could you please help to modify the function.


    • Hello there,
      If you are having issues with that workaround, I would recommend you to try the number 4 which cover more scenarios and it is cleaner to implement.
      I hope it helps.

  9. Any updates? When will it be fixed?

    I tried the recommended workarounds, but unfortunately they still create some issues.

    • Hello there,
      If any of the workarounds works for you, please open a ticket in our support forum as we would need to investigate your case. Please when you do it, specify that any of the five solutions worked for you.

Leave a Reply

Please stay on topic and be respectful to others. If you need help with issues not related to this post, use our Support Forum to start a chat or submit a ticket.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>