Problem: The client was experiencing an issue where after updating a page in Elementor and saving the translation in WPML, the translation status reverted to a gear icon with the message 'English translation assigned to local translator' instead of showing the updated pencil icon. This issue persisted even after rolling back WPML versions and cancelling stuck translation jobs. Solution: We recommended the client to update WPML to the latest version and disable all plugins except for WPML plugins and Elementor, and switch to the parent Astra theme. The client was advised to make a small change in the default language page, save it, and then open and save the translation in the WPML Translation Editor. This step was to help confirm whether the issue was related to a plugin conflict or something within the translation workflow itself. After these steps, the client reported that the issue was resolved by making a small change and updating the page using Quick Edit, which restored WPML's change detection and normal behavior.
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: The client's website is automatically redirecting to the /EN/ version when accessed from a Dutch browser, despite the desired behavior to stay on the main URL (https://alplift.com/). This issue stops when the WPML plugin is deactivated. Solution: We found that the 'Always redirect visitors based on browser language (redirect to home page if translations are missing)' setting was enabled in the WPML settings. To address this, we recommend checking and adjusting your WPML language settings: 1. Navigate to WPML → Languages. 2. Locate the 'Browser language redirect' section. 3. Adjust the settings as needed to prevent unwanted redirections. Additionally, ensure that your browser cache and cookies are cleared to avoid issues caused by outdated data.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and confirm that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: The client is using the WP All Export - ACF Export Add-On Pro and is unable to see the WPML option during the import process. Solution: We recommend reading our guide on using the WPML Export and Import plugin. Here is the link to the documentation: WPML Export and Import. It is important to note that the language information is added later in the import process. For more details on how and why this happens, please visit: managing the visibility of imported multilingual content.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to translate items via the WPML editor for your site, but the translated items are not displayed on an archive page. Solution: This issue might be due to the use of the FacetWP plugin on your archive page template. FacetWP is compatible with WPML, but it requires the installation of a bridge plugin to function correctly with WPML. You should have received a notification about this in your WordPress admin. We recommend that you install the bridge plugin and follow the guides provided by WPML and FacetWP for setting up multilingual filters:
After installing the bridge plugin, please verify if the translated items appear as expected on the archive page.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket.
