Background of the issue:
I'm trying to translate labels set up in a View created with the Advanced Custom Views Framework plugin. I have created a custom post type and custom fields using ACF. I then created a View using Advanced Custom Views and linked it to my group of custom fields. I set Advanced Custom Views to use Blade and I activated their file storage system so that a language file was created in my child theme. In the file, it says 'This file was generated automatically and contains instance labels for easy detection by multilingual tools.' and it does include all the labels from my View.
Symptoms:
I can't find the labels from my View in String Translation. Everything that was set in ACF is translatable, just not what was set up in the Custom Views Framework.
Questions:
Why can't I find the labels from my View in String Translation?
How can I make the labels from the Custom Views Framework translatable?
Yes, in that support page (hidden link), it says "Advanced Views uses the built-in WordPress translation function __('field label', 'themeDomain') for all View and Card labels. This allows you to translate labels seamlessly using your preferred multilingual plugin, eliminating the need for creating a separate View or Card for every language."
So I'm not sure why I can't see the labels automatically in the string translation?
What I understood was that I had to activate their File system storage so it would create a scannable file in my child theme for WPML and other multilingual tools, but what you are saying is that I need to edit this file with the correct textdomain? If so, which textdomain do I have to use? My theme's (generatepress)? The ACF Views's textdomain (acf-views)?
Lastly, I did add a label manually in the template (<h2>{{ __('Coordonnées', 'generatepress') }}</h2>) and it was automatically added to their multilingual file in my child theme (last line in the attachment), but I still don't see it in string translations, even after rescanning the file for new strings.
I will contact them to see that I'm following their steps correctly, but if I am, is there a reason why I can't see the strings in WPML even when I add the textdomain (as I did for one string as seen in attachment)?
in theory, yes, but this plugin works a bit differently. Typically, a getText() call is made directly within the plugin's PHP file, not in a generated file. The text domain itself doesn’t matter much—it’s just an identifier. You can try using "test" as a placeholder.
Lastly, I did add a label manually in the template (<h2>{{ __('Coordonnées', 'generatepress') }}</h2>) and it was automatically added to their multilingual file in my child theme (last line in the attachment), but I still don't see it in string translations, even after rescanning the file for new strings.
This seems to be the main issue—the getText() call wasn’t set up correctly. If you adjust it here, it should generate properly in the file.
Here are the steps to try:
1) Modify one string, ensuring it includes a text domain.
2) Check the generated file in your child theme to see if it updates.
3) Rescan the child theme in WPML -> themes & plugin localization.
4) Verify if the strings appear in WPML -> String Translation.
Thanks. I did what you said and it worked for the label I had created manually, but not for the others.
That said, I did hear back from the author of the plugin. They explained their plugin picks up the text domain automatically, based on the ‘Text Domain’ setting, defined in the heading of style.css of the theme. Since my child theme didn't have a text domain setting, it wasn't working. Now that I've defined it, it works.
