A widget on your site shows up to three different kinds of text, and each one is translated by a
\ndifferent part of the plugin. When a widget shows the wrong language, this page tells you which
\nof the three it is and where to fix it.<\/p>\n
This covers classic widgets<\/strong> – Search, Categories, Recent Posts, Tag Cloud, Custom HTML and the The Title<\/strong> field every widget has, and the body of a Custom HTML<\/strong> or Text<\/strong> widget, are Turn this on under LATW Multilingual \u2192 Settings \u2192 Translation \u2192 Other objects<\/strong>, with Translating a widget’s title\/text by hand is part of the free version. Translating it If you leave the Title<\/strong> field empty, WordPress does not store a title at all – the widget falls A Search<\/strong> widget’s button, a Categories<\/strong> widget’s default heading (“Categories”) when you There is nothing to configure here.<\/strong> This plugin switches WordPress’s own active language for the heading changes language on its own, with no setup and no cost, exactly as it does when a When this does not apply:<\/strong> a theme or add-on that typed its own text straight into the PHP code A Recent Posts<\/strong> widget’s list of titles and dates, a Categories<\/strong> widget’s list of category There is nothing to configure here either.<\/strong> These widgets automatically show the posts, terms The classic-widget field map (which fields of which A widget id_base not in this map is not offered on the Strings page at all – its Title<\/strong> field A widget on your site shows up to three different kinds of text, and each one is translated by a different part of the plugin. When\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-122","post","type-post","status-publish","format-standard","hentry","category-latw-multilingual"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/122","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=122"}],"version-history":[{"count":0,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/122\/revisions"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nrest of the widgets you place in Appearance \u2192 Widgets<\/strong>, or that a theme\/page builder adds under
\na “WordPress” or “WordPress Widget” category (Elementor’s wp-widget-*<\/code> widgets are this: they are
\nyour theme’s own registered widget, only wrapped so it can be dragged onto an Elementor page). A
\nwidget an Elementor add-on built from scratch (not a wrapped WordPress widget) is a different case<\/p>\n\n
The three kinds of text<\/h2>\n
1. Text you typed into the widget<\/h3>\n
\ncontent you wrote yourself. WordPress stores it once, the same for every language, so it has to be
\ntranslated like any other text on the site.<\/p>\n
\nClassic widgets (title & text fields)<\/strong>. Once it is on, each widget instance appears on the
\nStrings<\/strong> page (filter Type<\/strong> by Widgets<\/strong>), and its fields open in the usual translation
\npanel from there.<\/p>\n
\nautomatically with AI requires PRO<\/strong>.<\/em><\/p>\n
\nback to its own built-in heading, which is case 2 below.<\/p>\n2. The widget’s own built-in text<\/h3>\n
\nleft Title<\/strong> empty, a Tag Cloud<\/strong> widget’s heading (“Tags”), a Recent Posts<\/strong> widget’s
\ndefault heading (“Recent Posts”) – none of this is stored anywhere in your database. It is a
\nstring built into WordPress core (or, for a theme-specific widget such as a theme’s own
\n“Recent Posts” variant, built into the theme’s code), printed fresh every time the widget renders.<\/p>\n
\nevery visitor to the language of the page they are looking at, and WordPress prints these built-in
\nstrings in whatever language is active – the same mechanism that translates the “Read more” link
\nor the comment form’s labels. As long as:<\/p>\n\n
\nLanguage<\/strong> shows the full list WordPress knows; a language with no pack falls back to the
\nstrings baked into the code, normally English), and<\/li>\n__()<\/code>, _e()<\/code>) instead of a
\nhard-coded string,<\/li>\n<\/ul>\n
\nhuman visitor changes their own WordPress admin language.<\/p>\n
\ninstead of running it through __()<\/code>\/_e()<\/code> cannot be switched this way – there is no mechanism to
\nhook into, because WordPress never sees the string as translatable. That is a limitation of that
\nwidget’s code, not something this plugin (or any translation plugin) can patch from the outside.
\nIf one specific widget’s built-in heading refuses to change language while every other one does,
\nthat is the most likely reason – worth checking with whoever built the theme or add-on.<\/p>\n3. Content the widget pulls in live<\/h3>\n
\nnames and links, a Tag Cloud<\/strong> widget’s list of tags – none of this text lives on the widget
\neither. It is read fresh, on every page load, from your posts, categories and tags.<\/p>\n
\nand links of the language being viewed, because the posts and terms themselves are translated
\nposts and terms – the same translation you already did (or will do) from the Posts<\/strong> page or the
\ntaxonomy screens. Translate the post, or the category name, and every widget that lists it follows
\nalong; there is no separate “widget content” to keep in sync.<\/p>\nQuick way to tell them apart<\/h2>\n
\n\n
\n \nWhat you see wrong<\/th>\n Where to fix it<\/th>\n<\/tr>\n<\/thead>\n \n A title you typed yourself into the widget<\/td>\n Strings<\/strong> page, type Widgets<\/strong> (needs the “Classic widgets” setting above)<\/td>\n<\/tr>\n \n A heading with no Title<\/strong> set (e.g. widget just says “Categories”)<\/td>\n Nothing to fix here – check the target language has a WordPress language pack, and see “When this does not apply” above<\/td>\n<\/tr>\n \n A post title, date, category name or tag shown inside<\/em> the widget<\/td>\n Translate that post\/category\/tag itself<\/td>\n<\/tr>\n \n Text typed into an Elementor widget’s own settings (a heading, a button label built by the add-on)<\/td>\n See Translating Custom Elementor Widgets<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n What this does not do<\/h2>\n
\n
\nlanguage, the same way a menu has one structure. You cannot show a widget in one language only.<\/li>\n
\nHTML widget, for instance) – only the fields listed in the field map above are read; arbitrary
\nmarkup inside them is left as-is.<\/li>\n
\netc., inside a “block” widget) are translated too, but as block content – see the block editor’s
\nown strings under Strings \u2192 Blocks<\/strong> rather than the Widgets filter.<\/li>\n<\/ul>\nDeveloper reference<\/h2>\n
id_base<\/code> are treated as text) is
\narray( 'title' => 'text', ... )<\/code> per widget type, filterable with latwm_widget_text_fields<\/code>:<\/p>\nadd_filter( 'latwm_widget_text_fields', function ( $map ) {\n \/\/ A theme widget registered as id_base \"tj-recent-posts\" with its own \"title\" setting.\n $map['tj-recent-posts'] = array( 'title' => 'text' );\n return $map;\n} );<\/code><\/pre>\n
\n(if it stores one) stays untranslated even with Classic widgets<\/strong> turned on, until it is added
\nhere. This only affects case 1 above (text you typed); cases 2 and 3 are unaffected by this map,
\nsince they do not go through the widget-translation layer at all.<\/p>\n","protected":false},"excerpt":{"rendered":"