Problem: The client encountered issues while updating recruiter information on translated destination pages using Elementor. Specifically, they were unable to save changes and received a warning about potential loss of edits when trying to replace a recruiter on the Finnish version of a page. Solution: We recommend ensuring that WPML and Elementor are used in accordance with our compatibility guidelines, which can be found here: https://wpml.org/documentation/plugins-compatibility/elementor/. The issue described was not directly related to WPML. When editing translated pages, it is crucial not to use Elementor directly but to utilize WPML's Translation Editor. This approach was successfully used on the German version of the page, where the recruiter was correctly updated. To resolve the issue on the Finnish page, the client should update the information using the Translation Editor to ensure the changes are properly saved and displayed.
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 do not hesitate to open a new support ticket at WPML support forum.
. Solution: We recommended removing the custom URL assigned in the ACF "Imóveis" custom URL option. This change allows the URL to use the slug configured in WPML. We asked the client to try this solution and inform us about the results.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is concerned about the potential impact of the twig template problem in the next WPML update on their site, especially since they are unfamiliar with the website's code. Solution: We asked the client to provide screenshots from the WPML → Languages → Menu language switcher and Widget language switcher sections to assess the usage of TWIG templates. Upon reviewing the provided screenshots, we confirmed that the language switchers on the client's site do not use TWIG templates. Therefore, the client should not experience any issues related to the removal of TWIG support in future updates.
If this solution does not seem relevant to your case, or if it becomes outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.
Problem: If you're experiencing issues where changes made in the backend of your website are not visible on the front end in preview mode when using Avada with WPML Multilingual CMS, this might be due to accumulated post revisions. Solution: We recommend trying the following steps: 1. Use a database cleaner plugin to remove accumulated revision posts from your site. This has shown to resolve the issue on a staging site. 2. To prevent this issue from recurring, limit the number of post revisions that are retained. You can do this by adding the following line to your
wp-config.php
file:
define('WP_POST_REVISIONS', 3);
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 the issue persists, please open a new support ticket.
Problem: After migrating from Polylang to WPML using the 'Migrate Polylang to WPML' plugin, the client experienced issues with duplicate pages and incorrect URL structures for translated pages. Additionally, some pages like Home and Contact Us were not available for translation in the WPML Translation Editor. Solution: 1. To address duplicate pages, we advised the client to check the Languages section on the affected pages and manually link translations if they were missing. This process is detailed in our guide: https://wpml.org/faq/how-to-link-already-translated-pages/ 2. For pages not appearing in the WPML Translation Editor, we recommended making a minor content update to the original page and then saving it to refresh the translation availability. 3. To correct the URL structure for translated pages, the client was instructed to manually adjust the slugs using the language switcher in the WordPress admin bar. This adjustment ensures that the URLs reflect the desired language structure without duplication.
If this solution does not resolve your issue or seems outdated, we 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with menu links not updating according to the language version on their website using WPML. Solution: If you're facing similar issues with translating your menu in a Full Site Editing (FSE) environment, we recommend following the step-by-step guide provided in the WPML documentation. You can find detailed instructions on how to translate navigation menus in the site editor by visiting this link.
If this solution does not apply to your case, or if it seems outdated, please check the 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. We highly recommend opening a new support ticket if further assistance is needed. You can do so by visiting the WPML support forum.
Problem: The client is unable to edit their website using WordPress and Elementor Pro due to an error message related to the WPML Sitepress Multilingual CMS vendor code. The error message indicates that headers cannot be modified after they are sent. The issue recurs after an unknown number of page edits, even after deleting and re-adding a user. Solution: We investigated the issue and found that it persists even when the WPML plugin is deactivated, suggesting it is not directly related to WPML. The problem was identified to occur when only the Yoast SEO plugin is active. Updating the Yoast SEO plugin resolved the issue, as demonstrated in a video we shared with the client. If you're experiencing this issue, we recommend trying the following steps: 1. Deactivate the WPML plugin to confirm if the issue persists. 2. If the problem continues, check if it occurs with only the Yoast SEO plugin active. 3. Update the Yoast SEO plugin to the latest version. If these steps do not resolve the issue or if it appears unrelated to the plugins mentioned, it might be due to other factors. In such cases, the solution provided here might be outdated or not applicable to your specific situation. 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 problem persists, please open a new support ticket.
Problem: The client is using the Blocksy theme with WPML on a multilingual WordPress site and has encountered an issue where the Content Blocks created using Blocksy's 'Hooks' feature do not switch languages when changing the site language on the homepage. Solution: We recommended replicating the issue on a clean installation to identify compatibility issues. Here are the steps we suggested: 1. Install the Blocksy theme and necessary plugins. 2. Create a content block using the 'Content Blocks (Hooks)' feature. 3. Use this block on a page. 4. Translate the page and the content block into the required languages. 5. Attempt to replicate the language switching issue. If the content still does not display in the correct language, it might be due to the footer not being selected on the translated pages. We provided a workaround which involves checking the footer selection on translated pages.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 necessary, please open a new support ticket for further assistance at WPML support forum.
Problem: The client needs help customizing the WPML language switcher dropdown to match a specific style shown in an example image, but only found a troubleshooting guide and not a tutorial. Solution: We recommend following these steps to customize your WPML language switcher dropdown: 1. Navigate to WPML >> Languages >> Menu Language Switcher. 2. Edit the language switcher settings to choose a similar option as shown in the example. 3. To achieve the same arrow and border style, copy the CSS from the Twenty Sixteen theme. For more detailed guidance on styling issues, please refer to our documentation: How to fix styling and CSS issues for the language switchers.
If this solution does not fully resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Translators were removed from WPML and could not be re-added, although they still existed as accounts on the website. Solution: We found that the issue was caused by a corrupt key in the database. We removed the
wpml-cache-translators-translate
entry from the
wp_options
table in the database, which resolved the problem and the translator users were visible again in WPML.
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 the problem persists, please open a new support ticket.
Problem: You are trying to translate the metadata 'Artikelnummer' and 'Kategorie' on a single product page, as well as a code snippet generating a chart with specific item-related properties using WPML. Solution: To translate the metadata, please add the following code to WPML > Settings > Custom XML:
After adding this code, make a small change to the default language template, save it, and re-translate. The caption text should now appear correctly. For the code snippet issue, if you are adding it via an Elementor template, it is best to manually edit the second language Elementor template and adjust the custom code. Since custom code is not translatable via the WPML editor, it should remain the same in both languages.
If this solution does not resolve your issue or seems outdated, we 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 problem persists, please open a new support ticket.
Problem: This is a compatibility problem with the Make Column Clickable Elementor plugin. You are trying to translate a popup in Elementor using WPML, but the popup displays in Greek instead of English. Solution: We recommend following these steps to address the issue: 1. Ensure you back up your site before making any changes. 2. Open the
functions.php
file of your theme using a code editor. 3. Insert the following code:
/**
* Convert the popup link in a column
* Based on compsupp-7641 workaround
*/
add_filter( 'wpml_pb_elementor_widget_dynamic_id_converters', function( $converters ) {
$isContainer = \WPML\FP\Relation::propEq( 'elType', 'column' );
$containerLinksLens = \WPML\FP\compose(
\WPML\FP\Obj::lensProp( 'settings' ),
\WPML\FP\Obj::lensPath( [ '__dynamic__', 'column_link' ] )
);
return array_merge(
$converters,
[
[ $isContainer, $containerLinksLens, 'popup', 'popup' ],
]
);
} );
This code snippet should help ensure that the popup is displayed in the correct language. We contacted the authors of the Make Column Clickable Elementor plugin and asked them to add this fix to their files. https://wordpress.org/plugins/make-column-clickable-elementor/. If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific 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.
Problem: The client installed WPML and registered their site, but the WPML setup page was blank. Despite following troubleshooting steps like adjusting wp-config, deactivating caching plugins, and reinstalling everything, the issue persisted. No errors were visible in the Chrome developer console. Solution: The client switched from PHP 8.2 to 8.1, which resolved the problem and the WPML setup page reappeared. Additionally, we recommended checking the debug.log for potential issues and provided a link to a known issue that might be relevant: https://wpml.org/errata/custom-database-prefix-and-having-a-30-languages-can-cause-a-database-error-when-visiting-translation-dashboard/. We advised the client to back up their database before attempting any fixes suggested in the link.
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 our support forum.
Problem: The client is working on a development site with IP restrictions and is unable to allow WPML plugin to connect to wpml.org for updates due to network or security settings. Solution: We recommend the following steps to resolve the connection issues: 1. Log in to your WPML.org account and navigate to the Sites page: https://wpml.org/account/sites/ 2. Delete the existing site key. 3. Log in to your site, go to the Dashboard >> Plugins >> Add new plugin > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link and then the Get a key for this site link. 5. Copy the newly generated key, paste it back into the input box, and press the Register button. 6. Take a backup of your site and update WPML plugins to the latest version. If the issue persists, try the following: - Go to WP Dashboard Menu >> Updates and press the "Check again" link. - Contact your hosting service provider and ask them to whitelist the following URLs: - wpml.org - cdn.wpml.org - api.wpml.org - api.toolset.com - cloudfront.net For more details, refer to this documentation: https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/
If these steps do not resolve your issue, or if the solution 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 needed, please open a new support ticket for further assistance.
If this solution does not apply to your case, or if it seems outdated, please check the 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. We highly recommend opening a new support ticket if further assistance is needed. You can do so by visiting the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
