Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Europe/Madrid (GMT+02:00)

This topic contains 4 replies, has 1 voice.

Last updated by Marcel 1 day, 6 hours ago.

Assisted by: Marcel.

Author Posts
June 12, 2025 at 8:29 am #17128896

adamY

Background of the issue:
Our website uses Timber for WordPress, which relies on twig templating for the front-end. With the new update removing support for twig completely, we need some guidance on how to convert this website to be compatible.

Symptoms:
The new update has removed support for twig completely.

Questions:
How can we convert our website to be compatible without twig support?

June 12, 2025 at 9:47 am #17129263

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi,

Welcome to WPML support. I will answer this ticket before the ticket is assigned to one of my colleagues.

The TWIG template support removal is happening only on the WPML-related side, which is the language switcher or the currency switcher if you use WooCommerce.

If you used custom TWIG code to create the language switcher you will not be able to use that anymore.

But the default language switcher feature that adds to the menu would work as before.

So if you added the language switcher from WPML > Languages > Menu language switcher that should be fine.

Would you please give us more information on how the language switcher is implemented on your website?

Also having debug information will help to see how your website is set up. Would you please kindly follow the steps below to provide the debug information?

- Go to "WordPress Dashboard > WPML > Support > Debug Information (Link)".
- Copy the Debug Information from there.
- Get back to this chat screen and scroll down.
- Find the "Additional Data" section below. (Check the screenshot below)
- Click on the "Debug Info" item to expand it.
- Paste the debug information into the text area.
- Click the "Send Debug Info" button.

Screenshot:
https://wpml.org/wp-content/uploads/tmp/debug_info_20.png

Thanks.

June 18, 2025 at 4:03 pm #17147613

adamY

Debug info attached.

There are a lot of translations done inside twig templates, for example -

<p>{{ __(child.title, 'yoko-yachts') }}</p>

'child.title' references a string pulled in from WordPress ACF fields.

There are many more like this. Are you saying these won't be affected by the update, even though they are located inside .twig files?

Thanks in advance

June 18, 2025 at 4:04 pm #17147615

adamY

[removed]

June 19, 2025 at 12:00 pm #17150524

Marcel
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: Europe/Madrid (GMT+02:00)

Hi there,

If you're using Timber, you most likely have code similar to the following example:

add_filter('timber/context', function ($context) {
...
\Timber\Timber::get_menu('secondary_footer');

    $context['options'] = get_fields('options');
    $context['abs_path'] = __DIR__;
    $context['cookies'] = $_COOKIE;
    $context['global_pagination_mid_size'] = 3;
    $context['is_mobile'] = wp_is_mobile();
    $context['languages'] = apply_filters('wpml_active_languages', NULL);
    $context['current_language'] = apply_filters('wpml_current_language', NULL);
...
    return $context;
});

If that’s the case, the switcher integration is handled via PHP, so no changes are needed. Twig code within your template wouldn’t be affected by our update — unless you’ve used our Twig template inside shortcodes.

Best Regards,
Marcel