adamY

Problem:
The client is using Timber for WordPress, which utilizes Twig templating. They are concerned about the compatibility of their site due to a new update that removes support for Twig in the language switcher.
Solution:
If you're using Timber and your code resembles the following:

add_filter('timber/context', function ($context) {<br />...<br />\Timber\Timber::get_menu('secondary_footer');<br />$context['options'] = get_fields('options');<br />$context['abs_path'] = __DIR__;<br />$context['cookies'] = $_COOKIE;<br />$context['global_pagination_mid_size'] = 3;<br />$context['is_mobile'] = wp_is_mobile();<br />$context['languages'] = apply_filters('wpml_active_languages', NULL);<br />$context['current_language'] = apply_filters('wpml_current_language', NULL);<br />...<br />return $context;<br />});

then the integration of the language switcher is managed via PHP, and no changes are necessary due to the update. The Twig code within your templates will not be affected by our update unless you have used our Twig template inside shortcodes.

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If this does not resolve your issue, please open a new support ticket.