Problem: Post with Beaver Builder has a table with cell value "< $200 (local raw material use)". When ate returns the translation xliff, it contains block with an empty value. It triggers an error in the WPML plugin and makes it stuck on the client side without any possibility of moving forward.
Problem with the "<" symbol. If the symbol is removed, the translation works fine.
Solution: I offered temporary remove/replace "<" from text. After that client confirmed that things start to work
Problem: You are trying to use WPML to translate a shortcode that outputs tables on your site, but the tables generated by the shortcode are not being translated even after adding the shortcode in WPML’s Custom XML Configuration. Solution: Since the table content is generated via custom code in the Code Snippets plugin, it won’t appear in the translation editor by default. You need to register those strings for translation using the
wpml_register_single_string
hook in your code. After registering, you can translate them in WPML >> String Translation. To display the translated strings on the frontend, use the
wpml_translate_single_string
hook. For more details on registering and displaying strings, visit:
If this solution does not resolve your issue or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where a page translated into German is displaying mixed content in English, German, and sometimes Italian. This problem arose after switching between the Classic Translation Editor and the Advanced Translation Editor (ATE). Solution: We recommend the following steps to resolve the issue: 1. Ensure that the WPML plugin and all related add-ons are updated to the latest version. You can check for the latest versions and update instructions here: http://wpml.org/faq/install-wpml/ 2. If the page was initially translated using the Classic Editor, switch back to it to recover most of the translations. Review and fill out any missing items, then save the changes. 3. If you wish to switch to the ATE, open the existing page and its translation in a new tab, then switch to the ATE and manually fill out the existing translation or use automatic translation, which may require credits. For more details on switching editors, visit: https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/switching-from-classic-to-advanced-translation-editor/
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where prepaid credits are not updating on their website, showing an incorrect number. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key. 3. Log in to your site, go to the Dashboard >> Plugins >> Add new > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Then click the Register WPML link. 5. Click the Get a key for this site link. This will generate a new key for your site, and you can also assign the credits using that popup. 6. Copy the new key, paste it back into the input box, and press the Register button.
This solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
Problem: You are trying to translate a page to Japanese using automatic translation, but the translation is not displaying correctly on the front end. Although the page is translated to Japanese, it shows up as English. Solution: If you're experiencing this issue, we recommend checking if the translation has been saved and published correctly in the WPML translation editor. Sometimes, translations might not display due to caching issues, so ensure to clear your site's cache. If the problem persists, it could be related to a theme or plugin conflict. We suggest deactivating other plugins temporarily and switching to a default theme to see if the issue resolves. If none of these steps work, please contact our support team for further assistance.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem: You are using WPForms and WPML integration, and it is translating all the Smart Tags like {all_fields}, which stops them from working properly. The Smart Tags are being translated, resulting in {all_fields} being shown as {alle_Felder}. Solution: We recommend adding the following code to your functions.php file to prevent Smart Tags from being translated:
// WPML Workaround for compsupp-7788
add_filter( 'wpml_tm_job_field_is_translatable', 'compsupp_skip_wpforms_smart_tags', 10, 2 );
function compsupp_skip_wpforms_smart_tags( $is_translatable, $job_translate ) {
$data = $job_translate['field_data'];
if ( 'base64' === $job_translate['field_format'] ) {
$data = base64_decode( $data );
}
// Check if data exists and starts with '{'
if (isset($data) && strpos($data, '{') === 0) {
return false;
}
return true;
}
This solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If this does not resolve your issue, please open a new support ticket.
Problem: You are experiencing an issue where the menu disappears and is replaced by error messages after using the Auto Translation feature in WPML. This problem occurs when the menu, added using UberMenu, includes WPML shortcodes in the header content settings. Solution: We recommend removing the WPML shortcode from the header content settings where UberMenu is used. This adjustment should resolve the layout issue. If the header content needs to include that shortcode, try disabling all non-WPML and non-UberMenu plugins, switch to a default theme, and check if the problem persists. Always ensure to back up your site before making these changes.
If this solution does not apply to your case, or if it seems outdated, please visit our known issues page to check for related issues. Confirm that you have installed the latest versions of themes and plugins. If the issue continues, we highly recommend opening a new support ticket for further assistance.
Problem: The client is using WPML with WPForms to translate forms and integrate with ActiveCampaign. They need to receive the original English values of each field after form submission, regardless of the language the form is submitted in. However, they are encountering issues where translated values are sent instead of the original English values, causing problems with ActiveCampaign and other tools. Solution: We suggested checking if the input values that need to remain in English are appearing in the WPML Translation Editor when translating the form. If not, these values might be registered in WPML > String Translation. We recommended translating all option values in WPML > String Translation, and if the client wishes to keep the values the same in both languages, they should copy the original values. This approach should ensure that the original English values are sent to ActiveCampaign and other applications.
If this solution does not resolve the issue, we advised the client to test this setup and contact us for further assistance. We also recommended checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that they have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was experiencing issues with managing their website's URL after it changed, and they noticed duplicate URLs in their setup. They were unsure how to change the URL from https://cookie.bigrep.com/ to https://bigrep.com/ and why the URL was appearing twice. Solution: We advised the client to remove the WPML site key for the domain with issues by visiting https://wpml.org/account/sites, then generate a new key for that domain, and unregister and re-register WPML with the new key in their site's backend under Plugins > Add new > Commercial. Additionally, we explained that the URLs appearing, including the "cookie" one, are individual translation accounts used for each site and offered to hide them for the client.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
