Twig Language Switcher

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.

Problem:
The client needs to determine if Twig templates are being used on their multiple sites and seeks assistance with the transition for an upcoming Twig template update.
Solution:
If you've added the language switcher through WPML settings, a shortcode, or a widget, rest assured it will continue to function correctly. However, if the switcher is implemented directly in your theme's code, you should consult the theme author to understand how the WPML language switcher is integrated. Alternatively, if you have the necessary skills, you can check the theme's template files yourself to identify the file responsible for rendering the switcher and verify how it has been integrated. It's also crucial to ensure that you have a full website backup for any of your sites as a precaution. For more detailed guidance, you can refer to the following documentation:

• Designing Custom Currency Switchers Using Template Files
• WPML Language Switcher Hook
• WPML Shortcodes API

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.

Problem:
The client needed to determine if their site uses Twig templates for the WPML language switcher, as they received a notification about changes related to Twig. They provided code snippets and details about their implementation, which they did years ago and were unsure about the current setup.
Solution:
We advised the client that the code they shared indicates a PHP-based implementation of the WPML language switcher, not a Twig-based one. Therefore, their current setup should not be affected by the changes related to Twig templates. We recommended that they ensure they have a full website backup as a precaution. Additionally, we confirmed that all links shared in the support ticket are private and only visible to the client and the support team.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket.