I had an issue that widgets wouldn’t show up, but I discovered it was because the languages weren’t checked. However, checking them would override all other conditions and showing the widget on every page of that language.
I found a workaround to that, it requires you to edit the code though.
Find this block in display-widgets/display-widgets.php, using either the plugin editor in the wp admin or another editor:
if ( ! $show && defined( 'ICL_LANGUAGE_CODE' ) ) {
// check for WPML widgets
$show = isset( $instance[ 'lang-' . ICL_LANGUAGE_CODE ] ) ? $instance[ 'lang-' . ICL_LANGUAGE_CODE ] : false;
}
and change it to:
if ( $show && defined( 'ICL_LANGUAGE_CODE' ) ) {
// check for WPML widgets
$show = isset( $instance[ 'lang-' . ICL_LANGUAGE_CODE ] ) ? $instance[ 'lang-' . ICL_LANGUAGE_CODE ] : false;
}
Previously, because $show is negated, if a language was selected for a widget, it would disregard the other conditions. Say you have two pages: Page 1 and Page 2, and you have two languages: English and Swedish. You want to show the widget only on Page 1 on both languages.
Before, when $show was negated (so if show is false, it would match the condition of the if and check if the language is set). The plugin first checks if we should show it on page 2. We don’t want that, so $show becomes false. Then it comes to the problematic if-block, where false would become true and the plugin checks the language. As we want the widget to be shown on both English and Swedish, $show is now set to true, disregarding that it was false before.
Dunno if this solves all use cases though, maybe there was some use case that I’m not using that was the reason it was like that, or it was just a mistake, but it seems to work for me when I want to show a specific widget on specific pages on all languages.
You’d have to tick show on all languaged pages though, if Page 1 (English) and Sida 1 (Swedish) is the same page, you have to tick both if you want to show it on both (as well as both languages).
Oh also, if you update the plugin after doing this, you have to redo the change unless the plugin author fixes this the right way.
