This thread is resolved. Here is a description of the problem and solution.
Problem:
The client was unable to see the translated string for a custom plugin named 'growytasty' on the frontend, despite having scanned for strings and translated them in WPML.
Solution:
We discovered that the issue was related to the text domain not being loaded correctly. To resolve this, we added the following code to the 'growytasty.php' file to ensure the text domain is loaded:
function growytasty_load_textdomain() {<br /> load_plugin_textdomain('growytasty', false, dirname(plugin_basename(__FILE__)) . '/languages');<br />}<br />add_action('plugins_loaded', 'growytasty_load_textdomain');After adding this code, the text domain loaded properly, and the translation appeared correctly on the frontend.
For more details on configuring and loading translation files, you can visit our documentation: Translating the Theme You Created.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
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.
This topic contains 9 replies, has 3 voices.
Last updated by 2 months, 3 weeks ago.
Assisted by: Bobby.
 |
|
 Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00) |
|
|
|
|
|
|
|
 Supporter Languages: English (English ) Timezone: America/Los_Angeles (GMT-08:00) |
|
|
|
Please see the screenshot - it's right below the product.  |
|
Supporter Languages: English (English ) Timezone: America/Los_Angeles (GMT-08:00) |
|
|
Supporter Languages: English (English ) Timezone: America/Los_Angeles (GMT-08:00) |
|
|
|
|
|
Supporter Languages: English (English ) Timezone: America/Los_Angeles (GMT-08:00) |
Thank you, I was able to locate it. You are not directly outputting the "Producer" string in your code. Instead, you are passing it to WooCommerce via the $tabs['producer']['title'] array entry, and WooCommerce handles rendering it on the product page. I did a quick test to make sure it is being picked up correctly by adding "test" in front of it, this worked and it displayed in the front end as well as being picked up by String Translation. So far we know that the string is being picked up in the front end as well as String Translation. since this string is not being translated properly, the issue is likely related to the text domain not being loaded. To verify I added this code in growytasy.php and reloaded the front end at the footer.
add_action( 'wp_footer', function() {
// This will output whether the text domain is loaded correctly
if ( is_textdomain_loaded( 'growytasty' ) ) {
echo '<p>Text domain growytasty is loaded.</p>';
} else {
echo '<p>Text domain growytasty is NOT loaded.</p>';
}
});
( I have removed now since after registering the text domain verified that it is being loaded) The results are that the textdomain is not being loaded properly, which also explains why the .mo/.po files are missing from the plugin. To load the text domain I added the following code in growytasy.php
function growytasty_load_textdomain() {
// Adjust the path to the 'languages' folder if needed
load_plugin_textdomain( 'growytasty', false, dirname( plugin_basename( __FILE__ ) ) . '/languages' );
}
add_action( 'plugins_loaded', 'growytasty_load_textdomain' );
The translation is working OK now and the text domain is loaded properly. Related Documentation: Our support policy does not cover custom themes and plugins. The provided code is for your use at your own risk, and WPML does not maintain it. Always back up your site before making any changes recommended by us or others.   |
|
|
