Background of the issue:
We received a message from WPML about TWIG: 'If your site currently uses Twig templates for your language or currency switchers, please contact our support team soon. Our supporters are specially trained and ready to guide you through migrating to a PHP-based switcher solution.' Our site uses Twig templates.
Symptoms:
No specific issue or error message mentioned.
Questions:
What can we do with our site that uses Twig templates?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
My name is Marcel, and I’m the team lead for Christopher.
First of all, thank you for your patience. I understand how frustrating changes like this can be, especially when they impact your workflow. I’m truly sorry for the inconvenience. Decisions to phase out functionality are never taken lightly, but in this case, it was necessary for security reasons.
In some cases, Twig is used only in isolated components, such as a language switcher, and can be fairly easily replaced with a PHP-based version. However, in your case, the language switcher is integrated into a fully custom theme built entirely with Twig, which makes the situation a bit more complex.
When a theme relies entirely on Twig, our ability to offer hands-on support becomes quite limited. In these scenarios, your original developer is usually the best person to make the required adjustments, as they know the structure and logic of your theme far better than we do.
I checked your site, but currently don’t see the language switcher on the frontend. However, because the Theme File Editor doesn’t provide access to the Twig files in your resources folder, no changes could be made there. Is it possible that ongoing changes on your side might be affecting what we’re seeing at the moment?
To assist you further, I’d like to request FTP access. This would help me better understand how your theme is working and allow me to review the Twig implementation directly. If possible, we’d look into temporarily commenting out the relevant code to prevent errors from the deprecation, and evaluate whether switching to a standard menu-based solution could work—ideally without requiring a custom PHP switcher. This really depends on how the current switcher is styled and implemented, which I can't assess without seeing the actual output.
Again, I appreciate your understanding. While our ability to make changes may be limited in this case, I’m happy to bring this to our developers to see if there’s anything we can do from our side, even with the constraints of a fully Twig-based theme.
Best regards,
Marcel
The topic ‘[Closed] TWIG’ is closed to new replies.