Problem: If you're unable to see the '+' icon for translating pages and products in WPML, it might be due to a conflict with the Admin Columns Pro plugin. Solution: We recommend deactivating the Admin Columns Pro plugin temporarily to see if the translation icons reappear. If this resolves the issue, you can then try adjusting the settings within the Admin Columns Pro plugin to customize columns per post type, which might allow the translation icons to display without needing to disable the plugin entirely. You can adjust these settings by navigating to Settings >> Admin Columns.
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: You are trying to convert your footer to German using autotranslation with WPML, but even though the translation shows as 'completed', the footer still displays in English on the front end. Solution: The elements used in the footer are not available for translation in the WPML Translation Editor. We recommend you translate them manually by following these steps: 1. Edit the footer template using the Cornerstone editor. 2. In the top-right, click the language you want to edit. 3. Edit the elements with untranslated texts and manually enter translations. For more details, you can refer to the documentation on https://theme.co/docs/wpml#translation and https://wpml.org/documentation/theme-compatibility/xtheme/#frequently-asked-questions.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is attempting to export an XLIFF file for a French page that has already been translated from English to French. The client expected to see an option to export a published page that has been translated to XLIFF or a way to change the status of the completed translation. Instead, they received a message saying 'No translation in the queue.' Solution: 1. Ensure that you are working with the latest versions of WPML and other relevant plugins. You can check for updates in your WPML dashboard. 2. Verify that the page was originally created in English and then translated to French. If this is the case, you cannot export the French page back to English as an XLIFF file. 3. To export the XLIFF file, go to WPML > Translation Management, select the English page, and send it for translation to French. Even if it has already been translated, this action allows you to export the existing French translation as an XLIFF file.
If this solution does not apply to your situation, or if it seems outdated, we recommend checking the related known issues and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
Problem: You are trying to edit translations for a previously imported article using the advanced translation manager (ATE), but find that translations are not editable without redoing the entire translation. Solution: Unfortunately, it is not possible to edit imported translations directly in the ATE. You have two options: 1. Use the manual translation method. 2. Switch to the Classic translation editor. For detailed guidance, visit: Using different translation editors for different pages and Using the translation editor. Alternatively, to open translations in the WordPress editor instead of the ATE, follow these steps: 1. Open the default language post in the WordPress editor. 2. In the language meta box, switch the translation method to "WordPress editor". 3. A popup will appear, asking whether you want to set the WordPress editor as the default editor for this specific post, the entire post type, or the entire site. Select the option that suits your needs and save the changes.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where manually translated content in Cornerstone was overwriting content on the secondary language.
Solution: We advised the client to update all outdated plugins and themes, especially WPML-related plugins. To update WPML plugins, the client needed to: 1. Go to the 'Commercial' tab in the 'Add New' section of the 'Plugins' menu. 2. Unregister WPML from the site if the registration key didn't match. 3. Remove the actual site from their WPML account. 4. Register the site again with the correct key. After updating the plugins, we asked the client to check if the issue persisted by creating a new test page. When the issue was still present, we requested authorization to run tests and eventually escalated the issue to our 2nd tier support team.
Please note that this solution might be outdated or not applicable to your 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.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
