Background of the issue:
I updated WPML to version 4.6.14 and WordPress to version 6.7 in my local environment. I use translatable strings with __(), esc_html_e() functions, and POT files. The issue seems to affect only parent themes where I call load_theme_textdomain() function with after_setup_theme(). Child themes with textdomain added with load_child_theme_textdomain() work fine.
Symptoms:
The translatable strings are not working anymore; they only show default languages. This issue occurs with sites using a parent theme and WPML with the latest version of WPML and WordPress 6.7.
Questions:
Why are the translatable strings not working with the parent theme after updating WPML and WordPress?
How can I resolve the issue of parent theme strings not translating with the latest WPML and WordPress versions?
Reference to our recent chat, meanwhile this ticket is attended by one of my colleagues, please provide temporary access (WP-Admin and FTP), preferably to a test site where the problem has been replicated.
Your next answer will be private, to share this information safely.
Also provide detailed steps to reproduce the issue and links to pages in the admin and on the frontend.
IMPORTANT: Please take a complete backup of the site to avoid data loss.
I made test environment for the live version of the site that I had problems with in local environment. I updated WordPress version and WPML plugins (and every other plugins) to latest version. Everything seems to be working correctly now.
The issue seems to be only in my local environment. I don't quite understand why, because it should be similar to the server, only difference being Apache(local) and Litespeed(server).
I need to investigate this more and see if I can get the local environment working correctly. But for now it is good to know that the live sites are working as intended and I can update them.
