Problem: The client reported that links from pictures in Elementor are not being translated anymore, specifically mentioning that a section on the homepage remains in French despite translations. Solution: We recommended adding the following custom XML configuration to WPML > Settings > Custom XML:
1
2
3
4
5
6
7
8
9
<wpml-config>
<elementor-widgets>
<widget name="image">
<fields>
<field editor_type="LINK">link>url</field>
</fields>
</widget>
</elementor-widgets>
</wpml-config>
After adding this, the client should make a small change to the default language page and re-translate. It might also be necessary to clear the Elementor cache by selecting 'Clear Data & Files'.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, we highly recommend checking related 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 experiencing issues with language changes and receiving numerous warnings from WPML. They suspect the 'fibosearch' plugin might be causing the language change issue. Solution: We recommended updating to WPML 4.7.1 and setting up a staging site. The client should then disable all other plugins and test with the default WordPress theme and WPML plugins only to check if the issue persists. If the problem is still there, it indicates a potential bug with WPML, and further investigation is needed. We also suggested testing in a minimal state and sharing a video of the issue if it continues. Additionally, we invited the plugin author to join the GoGlobal program to ensure compatibility with WPML. For further assistance, we opened a new support ticket and suggested checking related known issues at https://wpml.org/known-issues/.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend verifying that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where changing a SKU causes the product to go into "Need modifications" and you're being charged for translations despite no significant content changes, this might be due to minor text alterations such as the removal of line breaks. These changes are treated as new content by the translation memory, requiring re-translation. Solution: We recommend enabling WordPress revisions to track changes more accurately, which might help in identifying unintentional text modifications like line breaks. It's important to ensure that the text sent for translation matches exactly with previous translations to avoid unnecessary charges. If the issue persists and you believe it should not, please check our related known issues and verify you have the latest versions of themes and plugins installed. If this solution does not apply or is outdated, we encourage you to open a new support ticket for further assistance. You can do so here: WPML support forum.
Problem: You are trying to delete translations that WPML prompts to update, but you do not wish to update them as they are already correct. You are considering using an SQL request to manage this for all your products. Solution: Firstly, the icon indicating that translations need to be updated simply means that the original content was updated after the translation was completed. This does not necessarily require you to update the translation; it's just an indicator. There is no direct option to remove this warning.
However, if you want to manually set the translation status to avoid seeing the 'update needed' icon, you can do this through the database. You can assign the translation jobs to yourself and then modify the
1
wp_icl_translation_status
table. Set the status to 10, which marks the jobs as completed. This change will replace the 'update needed' icon with a pencil icon, indicating that the translation is complete but can still be edited if necessary.
Please note that this solution might not be relevant if it's 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client reported an issue where the translation status incorrectly showed as pending, even though there were no pending translations. Solution: Initially, we suggested following the instructions in our guide to resolve issues where the translation process is stuck. This guide can be found here: https://wpml.org/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/ When the problem persisted, we identified that 25 translation jobs were stuck in the database with a status of '2' . We resolved this by executing the following SQL command to manually change their status to '9':
1
2
3
4
update
`icl_translation_status`
set status = 9
where status = 2
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client's website crashed due to multiple WPML requests, specifically with POST requests to admin-ajax.php. The issue persists even after disabling other plugins, indicating that WPML is the cause.
Solution: We recommend enabling the debug mode to track any errors that might be causing the issue. To do this, add the following lines to the wp-config.php file:
1
define('WP_DEBUG', true);
1
define('WP_DEBUG_LOG', true);
1
define('WP_DEBUG_DISPLAY', false);
1
@ini_set('display_errors', 0);
1
define('SCRIPT_DEBUG', true);
This will create a debug.log file in the wp-content folder, which can help identify the problem. For more detailed instructions, please refer to our documentation on debugging WPML.
If these steps do not resolve the issue or if the debug log does not provide clear insights, we encourage you to share the log using a service like Pastebin and provide us with access to your wp-admin area for further investigation. Please ensure you back up your site before providing any access.
If this solution doesn't look relevant, please open a new support ticket in our WPML support forum.
