1- Go to WPML String Translation
2- Scroll down to the "Auto register strings for translation" section and enable that option
3- Visit the page where the string is added on the front end
4- Go back to String translation and disable the Auto register option
5- Search again for the string and translate it
If that didn't help, please try the following steps:
1- Go to WPML-> Theme and plugins localization
2- Select the plugin "ELEX Product Price Custom Text" and scan it
3- Go to WPML-> String Translation
4- Scroll down and click on the "Translate texts in admin screens »" link
5- Search for the needed string
6- Select the string and click on the "Add to String Translation" button
7- Then click on "the « Return to String Translation" link
8- Translate the string, clear the cache, and check the front end
Hi
thank you for your answer
The solution you presented didn't help me
I am using the plugin "ELEX Product Price Custom Tex" and as you can see in the photo I am attaching, I use the option: Use Custom Suffix/Custom Suffix , two different descriptions:
1. in the first case: "τμχ. με ΦΠΑ" this should be translated as "pcs. with VAT"
2. in the second case "τ.μ. με ΦΠΑ" this should be translated as "sqm. with VAT"
but in the secont image that i am attaching in the WPLM/String translation only the one string i can find that "in the second case" and i can not find the "first case" to translate it.
and yet, although I cannot translate it, I see that in the product here hidden link next to the price it has got the translation "sqm with VAT" which should not have had this translation but should have had the translation "pcs. with VAT"
I got the reply from our 2nd tier supporters, this could be a compatibility issue.
I have created this clean sandbox setup on our servers here: hidden link (one-click login)
May I kindly ask you to install the "ELEX Product Price Custom Text" plugin and try to recreate the issue? (WPML and WooCommerce are already installed and configured)
Please don't install anything else like plugins that are not necessary, on a clean sandbox we try to use just the WPML plugins and the plugin/theme that's part of the issue.
If the issue is going to take place on this clean setup on our servers too, then I can forward this to our compatibility department.
Please let me know how that goes and what you can find.
Hi
thank you very much for your help
I have installed the plugin : "ELEX WooCommerce Product Price Custom Text (Before & After Text) and Discount"
The original language is the English, and from this language we will translate into German and Danish
in my example I have passed in the English language 2 products
1. hidden link
2. hidden link
in German
1. hidden link
2. hidden link
in Danish
1. hidden link
2. hidden link
the first language is English, and they should be translated into the other languages:
1. in the first case: "τμχ. με ΦΠΑ" this should be translated as "pcs. with VAT"
2. in the second case "τ.μ. με ΦΠΑ" this should be translated as "sqm. with VAT"
The string is stored as the elex_ppct_custom_fields_suffix custom field inside the product. The expected workflow would be to translate that string with the product.
However, the author does not register this field as translatable. Instead, they register and translate that string with a string translator in SettingsController::elex_ppct_return_wpml_string() - ....../wp-content/plugins/elex-product-price-custom-text-before-after-text-and-discount-for-woocommerce/includes/SettingsController.php
This would work correctly if the text is the same on all products, but when you try to define different texts for products, it conflicts.
Workaround:
1. Add the following XML code to WPML > Settings > Custom XML Configuration:
2. Open the ....../wp-content/plugins/elex-product-price-custom-text-before-after-text-and-discount-for-woocommerce/includes/SettingsController.php file.
3. Around line 121, replace the following snippet:
public static function elex_ppct_return_wpml_string( $string_to_translate, $name ) {
// https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/#hook-620585
// https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/#hook-620618
With:
public static function elex_ppct_return_wpml_string( $string_to_translate, $name ) {
// WPML Workaround for compsupp-7267
// We want to disable the rest of the code so it can be translated via custom field translation (instead of String Translator)
return $string_to_translate;
// https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/#hook-620585
// https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/#hook-620618
4. Do a small modification on the original product and save it
5. Update the translation and the text will be included in the translation editor
I tested this on the sandbox site and it works as you can see here:
- hidden link
- hidden link
As this plugin is not listed as compatible https://wpml.org/plugin/, could you please report this issue to the plugin authors?
