Title: WPML String Translation plugin
Last modified: November 21, 2017

---

# WPML String Translation plugin

 *  Resolved [Yael Reinhardt-Matsliah](https://wordpress.org/support/users/pixelhappystudio/)
 * (@pixelhappystudio)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/wpml-string-translation-plugin/)
 * Hello,
 * When I view my widgets on sites using WPMl and Black Studio, I see warnings:
 * WARNING: This widget has one or more translations made using WPML String Translation
   plugin, which is now a deprecated method of translating widgets, in favor of 
   the “Display on language” dropdown introduced with WPML 3.8. Please migrate your
   existing translations by creating new widgets and selecting the language of this
   widget and the new ones accordingly. Finally delete the existing translations
   from WPML String Translation interface.”
 * I initially thought this was coming from WPML so their support executed a general
   scan and confirmed that this message is not coming from WPML. It is being generated
   by the Black Studio TinyMCE Widget.
 * Can you provide more information on this warning? I have multiple sites, some
   with dozens of widgets, so would like to understand how critical this and if 
   things will break any time soon before I am able to update all the widgets.
 * Thank you.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwpml-string-translation-plugin%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Marco Chiesi](https://wordpress.org/support/users/marcochiesi/)
 * (@marcochiesi)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/wpml-string-translation-plugin/#post-9709658)
 * Hello Yael,
    I confirm that warning is displayed by our plugin when it detects
   widgets translated via WPML String Translation, which is now a deprecated method
   for having multilingual widgets.
 * Starting from WPML 3.8, recently released, we recommend to use their native “
   Display on language” drop-down.
 * Please also see our FAQ about this, here’s a copy:
 * > If you’re using WPML v3.8 or newer and you need to translate a widget, we recommend
   > to create a separate widget for each language of your site and assign the language
   > to each widget accordingly using the selector “Display on language” provided
   > by WPML. This way you will be able to work with the visual editor also for 
   > translations.
   >  For older versions of WPML (up to 3.7.x), we recommend to install
   > the 3rd party WPML Widgets plugin, which provides the same feature described
   > above, that was not available natively on WPML. In the past, we also suggested
   > to translate the widgets using the official WPML String Translation plugin,
   > but this method is now deprecated as it was not very friendly due to the inability
   > of using the visual editor for translations. If you were using WPML String 
   > Translation, we recommend to switch to the aforementioned translation method
   > and remove the entries in WPML String Translation list after you moved them
   > to be real widgets. Starting from version 2.6.0 of Black Studio TinyMCE Widget,
   > a warning will be displayed if any deprecated translation is detected.
 * An example to clarify: suppose you have a widget that has to be displayed in 
   two languages, i.e. English (primary) and Italian.
 * With the old setup, you would have created the English widget on the Widgets 
   screen, then you would have translated it with WPML String Translation plugin(
   with no visual editor).
 * With the new setup, you would create two widgets on the Widgets screen, both 
   using the visual editor, and simply assign the language accordingly, with the“
   Display on language” drop-down provided by the new version of WPML.
 * To switch from the old setup to the new setup, you will need to copy and paste
   the translations (title + text) from WPML String Translation to newly created
   widgets for the secondary language(s), and also assign the proper language to
   each widget (both the original one and the new ones).
 * Old translations will keep working as usual, but we recommend to switch to the
   new system.
 *  Thread Starter [Yael Reinhardt-Matsliah](https://wordpress.org/support/users/pixelhappystudio/)
 * (@pixelhappystudio)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/wpml-string-translation-plugin/#post-9722078)
 * Thank you for the detailed response, Marco, much appreciated!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘WPML String Translation plugin’ is closed to new replies.

 * ![](https://ps.w.org/black-studio-tinymce-widget/assets/icon.svg?rev=2627604)
 * [Black Studio TinyMCE Widget](https://wordpress.org/plugins/black-studio-tinymce-widget/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/black-studio-tinymce-widget/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/black-studio-tinymce-widget/)
 * [Active Topics](https://wordpress.org/support/plugin/black-studio-tinymce-widget/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/black-studio-tinymce-widget/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/black-studio-tinymce-widget/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Yael Reinhardt-Matsliah](https://wordpress.org/support/users/pixelhappystudio/)
 * Last activity: [8 years, 6 months ago](https://wordpress.org/support/topic/wpml-string-translation-plugin/#post-9722078)
 * Status: resolved