Skip Navigation

WPML 4.0.5 brings improved compatibility with the Elementor page builder. You can now translate Elementor templates and global widgets. As always, this release also brings numerous new features and bugfixes.

Translating Elementor’s global widgets and templates

With Elementor Pro you can create global widgets. They allow you to reuse the same widget across different parts of your site. This way, when you update your global widget in one place, all instances across your site get updated as well.

Elementor Pro also allows you to create custom templates and use them in any page on your site. This includes templates for sections and footer.

There are two main steps for translating Elementor templates and global widgets:

  • Translate the global widget or a template.
  • Translate any page that features this global widget or a template.

Go to the Elementor -> My Templates page. All templates and global widgets will appear there. Simply click to translate any of them, using the + icon for the desired language.

Translating a global Elementor widget
Translating a global Elementor widget

Translation Editor page will open and you can easily translate your global widget or a template.

Visit our documentation page for detailed information about translating Elementor templates and global widgets.

Other Features and Bugfixes


Besides the improved Elementor compatibility, we fixed some important bugs:

  • Fixed an issue with language information being added to the database when “attachments” were set as not translatable.
  • Fixed an issue with Enfold causing the translated elements to not appear on the translated front-end pages.
  • Resolved issues occurring during concurrent requests when upgrading to 4.0.4.
  • Resolved CORS error when creating a page in the secondary language and languages per domains are set.

WPML String Translation 2.8.5

We implemented the new Translation Memory feature in String Translation. It automatically fills the translation field in the database with the translated value if that value already exists in the database.

WPML Translation Management 2.6.5


  • Added highlighting for already translated fields in the translation editor.
  • Implemented the Translation Memory feature for exported XLIFF files. Now if a string has already been previously translated, its translation will be pre-populated in the XLIFF files.
  • Added grouping for Translation Services in the respective tab of Translation Management.


  • Fixed the translated terms included in the translation job regardless of related setting.

WPML Media Translation 2.3.5


  • Resolved compatibility exception between Formidable Forms Pro and WPML Media.
  • Fixed tooltip text in media translation icon.
  • Added a tooltip in media translation page for translation control buttons.
  • Fixed an issue when reverting media to original before clicking in the “Save media translation” button.

How to update

As always, you will receive this update for WPML plugins automatically to all registered sites. You can download and install manually from your WPML account. Please be sure to update all of WPML’s components.

Finally, remember that it’s always a good idea to back up the database before updating anything on your sites.

18 Responses to “WPML 4.0.5 with support for Elementor templates and global widgets”

  1. @Dario: “Samantha” seems to be a spam bot, hoping for a SEO backlink in comments (even if it’s only a “nofollow” link). In a few years bots will surely pass the turing (and maybe also the grammar) test…;-)

    • Thanks, Frank! To be honest, I wasn’t sure if she was or not. Sometimes, we get even more cryptic messages than this – from real people. 🙂

  2. For some time now, I have not been able to update WPML and other plugins (incl. theme DIVI from Elegant Themes). I have deleted all plugins that I don’t use, but this does not make a difference. I keep getting messages that files cannot be created (I cannot attach a screenshot, unfortunately ).
    Can you help?

    • Hi, Petra! The newest ticket from you in our system is from 2 and a half years ago.

      Could you please share the link to your ticket here? Maybe it wasn’t submitted?

      King regards, Dario

    • Hi, Petra! Yes, I see the ticket now in our support queue. Our supporters will answer you very soon. Thanks for updating me on the matter!

      Kind regards, Dario

  3. After we updated the WPML plugin to 4.0.5 (on July 24th) we started having a new problem.

    Whenever we upload an image, it does not show it in our media library either our main one (spanish) or secondary one (english). In order to see it, every time we have to click on:

    WPML support > troubleshooting > “Set language information” (Adds language information to posts and taxonomies that are missing this information.)

    This will let us see the images but it will not fix the problem and we continue to have it. Contacted support a while back but since they are located I assume in India, I would get a response at midnight and made conversation drag on, until finally I get a response “I uploaded the images and its showing perfectly in the media library so could you please check the issue further?”.

    This is after I sent them an admin account, a backup of our site, and our debug info. Really don’t know what else to do.

  4. I am extremely unhappy with the new 4.0 changes. Why change something that was working al ready and not give us an option? I updated yesterday and today all of my clients are complaining that they can’t translate their content anymore.

    Why would you just assume that everyone wants to divide roles like Translation Managers and Translators? Why not just let all of the translators edit the content…

    The usual + sign or pen sign was working wonderfully, this is way too complicated. I just want my editors to be able to edit everything in both languages…

    Tried making all editors both translator and translator managers, but it still won’t work by just clicking the pen or + sign to edit.

    Absolutely hate the update

    • I’m not sure what went wrong with the sites that you recently updated. For existing sites, there should be no difference in workflow. All translators can continue translating exactly as before, without additional choices.

      For new sites, there’s a link to click which bypasses the whole Translation Manager assignment.

      If these two aren’t working for you, we need to check why. Can you please create a support ticket that shows us what you’re getting? Add another comment here with the link to the ticket so I can follow up.