Problem: You are trying to cache translated posts but are unable to do so because of the _lsvary cookie, which affects caching behavior on your site. Solution: Currently, there is no update from the plugin authors regarding a solution to avoid the _lsvary cookie when caching translated posts. We previously reached out to the authors, and they are aware of the issue but have not provided a definitive solution yet.
We recommend contacting the plugin authors directly for the most recent updates on this issue.
The code below, provided by the client, eliminates the need to vary the cache based on currency. However, this approach is only suitable when a single currency is used per (sub)domain or URL. Please note that this code is untested and provided as-is, as it was not created by our team. We strongly recommend testing it thoroughly in a staging environment before implementation.
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 you still need assistance, please open a new support ticket at our support forum.
Problem: The client is experiencing rounding errors when converting product prices from Danish Krone (DKK) to Euro (EUR) with German tax on their WooCommerce site. The custom function used for conversion does not round the prices correctly, leading to discrepancies in the displayed prices. Solution: We recommend enabling "Round tax at subtotal level, instead of rounding per line" in WooCommerce > Settings > Tax > Tax Options screen for a potential alternative solution.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client is experiencing an issue where links under the 'Add to cart' button are pointing to the original language version (Danish) instead of the translated version (Norwegian) on their e-commerce site. Solution: We recommend the following steps to resolve this issue: 1. Ensure that the "Adjust IDs for multilingual functionality" option is enabled. You can find this setting by navigating to WPML -> Languages. 2. After enabling this option, it is advisable to clear your site's cache to ensure changes take effect, although this may not always be necessary.
The "Adjust IDs for multilingual functionality" setting in WPML helps ensure that content elements like posts, pages, media, and taxonomies are correctly linked across different languages. This setting is crucial for maintaining the integrity of ID-based content across your site, facilitated by themes, plugins, or custom fields. While enabling this feature might introduce a slight performance overhead due to additional database queries, proper caching strategies can effectively minimize this impact.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please do not hesitate to open a new support ticket with us for further assistance. You can do so at WPML Support Forum.
Problem: The client's WooCommerce store experienced a slowdown after installing multiple languages using WPML. The client considered removing WPML Media and untranslated strings but was unsure if these changes would significantly improve site speed.
Solution: We advised the client not to use PHP 8.3 as it is still in beta for WordPress and could slow down the site. Instead, we recommended using PHP 8.1. We suggested monitoring the site with the Query Monitor plugin to identify slow and duplicate queries. For managing strings, we directed the client to WPML > Support > Troubleshooting to delete unused strings and provided guidance on how to delete strings from WPML -> Strings Translation, which can be read more about here.
Additionally, we found that WPML Media does not significantly impact performance unless used for translating images specifically for different languages. We also noted that the site's hosting might contribute to performance issues due to resource limitations or database call restrictions, especially with increased content from multiple languages.
If these steps do not resolve the 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 further assistance is needed, please open a new support ticket here.
Problem: You are experiencing an issue where the src value in the img tag for product images on the translated version of your site is incorrect, showing a missing featured image. This problem occurs after images that were resized after they were translated. Solution: We found that the _wp_attachment_metadata was not updated for translations after the original image was replaced with a scaled one due to a script you ran. To address this, you can synchronize the metadata between the original and translated images by adding a script to your theme's functions.php file:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
functionwpml_sync_wp_attachment_metadata() {
// Get all original media attachments
global$wpdb;
$original_attachments= $wpdb->get_results("
SELECT element_id FROM {$wpdb->prefix}icl_translations
After adding the script, reload your dashboard page and then remove the script. Ensure to back up your database before proceeding.
Please note that this code has not been thoroughly tested and is more of an idea for fixing the problem. If it doesn't work as expected, you or someone with appropriate expertise must make any necessary adjustments. The custom coding falls outside the support provided here.
This solution might not be relevant 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 at WPML support forum.
Problem: If you're experiencing issues with internal links in translated texts pointing to the original content instead of the corresponding translated content in your WooCommerce store, and the 'Translate Link Targets' tool is not resolving the issue, this summary might help. Solution: Firstly, ensure you are using WP All Import Pro for importing. You can address this issue by creating a function to map and replace URLs during the import process. Here's a step-by-step approach: 1. Extract internal URLs from both the original and translated content using a unique identifier. 2. Map these URLs so that each original URL corresponds to a translated URL based on the data in your Excel sheet. 3. Replace the original URLs in the translated content with the correct translated URLs during the import process. For existing posts where links are incorrect, you might consider using a custom function to fix translated internal links. This function would scan each post for internal links, check if they are internal, and replace them with the correct translated URLs if a translation exists. Note: These solutions involve custom coding and might require adjustments specific to your setup. If these steps seem complex or if they do not resolve your issue, we recommend consulting with a professional from WPML Contractors.
Please note that this solution might be 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 the problem persists, please open a new support ticket.
