Problem: The client expressed frustration about having to manually select each image for translation for each product, with over 100 images per product and over 100 products, making the process very time-consuming. Solution: We acknowledged the inconvenience caused by the current manual selection process. We have updated WPML to version 4.7, which now includes a feature where all relevant images for the posts are automatically included when the post is selected for translation from the Translation Management Dashboard. This should significantly reduce the manual effort required.
If this solution does not apply to your situation, or if it seems outdated, we 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. If issues persist, please open a new support ticket.
Problem: The client reported an issue where product links were not directing to their translated versions, causing significant navigation problems on a multilingual site. Solution: 1. We reviewed the client's previous support tickets and internal notes to avoid repeating steps and to understand the issue thoroughly. 2. We requested the client to create a backup and provide new access credentials for secure troubleshooting. 3. After gaining access, we conducted tests and discovered that while full URLs translated correctly in some instances (e.g., on the Spanish versions of the site), there were inconsistencies. 4. Further investigation revealed that the issue was due to a configuration in Rank Math and a mismatch in permalinks that matched one product category slug.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is concerned that the hreflang tags on their website are not including query parameters (like '?add-to-cart=159246' or '?paged=10') after the question mark in URLs. Solution: We explained that excluding query parameters from hreflang tags is the correct and recommended approach for optimal SEO performance. Here are the reasons: - Hreflang Tags and Canonical URLs: Hreflang tags should point to the canonical versions of pages, intentionally excluding query parameters to avoid multiple URLs leading to the same content, which can confuse search engines. - Preventing Duplicate Content Issues: Including query parameters could lead to search engines indexing multiple versions of the same page, potentially resulting in duplicate content penalties. - Improved Search Engine Indexing: By pointing hreflang tags to canonical URLs without query parameters, it helps search engines recognize the primary version of each page, enhancing SEO rankings. We recommend verifying that the canonical tags on your pages are correctly pointing to the main site without query parameters. You can check this by viewing the page source and looking for the canonical link tag. For guidance on checking canonical tags, visit this article.
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 further assistance is needed, please open a new support ticket at WPML support forum.
If you use the Rank Math SEO plugin and its Remove base option in conjunction with WPML’s Different domains per language setting, this may lead to excessive redirections, resulting in the ERR_TOO_MANY_REDIRECTS error.
Solution:
Please make sure to have a full site backup of your site before proceeding.
1. Open …/wp-content/plugins/seo-by-rank-math/includes/modules/woocommerce/class-product-redirection.php file.
Problem: The client experienced an issue where 40,000+ duplicate images were created due to a hiccup, and after removing unused media, including media from translations, all media on translated pages went missing. The client is looking for a way to 'recycle' or 'retranslate' the media so that it works on the translated pages as it does on the non-translated pages. Solution: We recommend the following steps to address the issue: 1. If you have a backup from before these database changes were made, utilize it to restore the missing entries. 2. If no backup is available, follow these steps:
1
1. Create a full website backup.<br />2. Complete all translations marked as"update needed"in the Translation Editor by clicking "Complete."This will restore the missing images.<br />3. For pages/products created in secondary languages, manually restore the images in the page editor.
We always advise having a backup before making any changes to prevent such issues.
If this solution does not 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: The client reported issues with 'ghost' product categories in their database, where certain term IDs appeared in the term_taxonomy table but not in the terms table, causing discrepancies and errors. Solution: We identified that the problem was due to corrupted terms in the database, which is not directly related to WPML but to the WordPress database itself. To address this, we recommended: 1. Deleting records from the term_taxonomy table that do not exist in the terms table using the following SQL query:
1
DELETEFROM `eb21term_taxonomy` WHERE term_id NOT IN (SELECT term_id FROM eb21terms);
2. Deleting records from the term_relationships table that do not exist in the term_taxonomy table using this SQL query:
1
DELETEFROM `eb21term_relationships` WHERE term_taxonomy_id NOT IN (SELECT term_taxonomy_id FROM eb21term_taxonomy);
We advised the client to ensure a complete backup of their database before proceeding with these queries to prevent any potential data loss and suggested consulting a WordPress professional if they are not comfortable performing these operations themselves.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 reported issues with duplicate queries and missing translations in a multilingual WordPress setup using WPML and WooCommerce Multilingual (WCML). They also inquired about setting up a fallback option for untranslated products and categories. Solution: 1. We recommended deactivating WPML and WCML to check if the duplicate queries persist. After running WPML troubleshooting actions from WPML->Support->Troubleshooting, we identified that the remaining queries were not related to WPML. 2. For the fallback option, it can be enabled from WPML->Settings->Post Types Translation -> Translatable use translation if available or fallback to default language. We provided a link to our documentation for further guidance: documentation. 3. To address the issue of missing translations for product categories, we suggested setting certain taxonomies to "Translatable - only show translated items" from WPML -> Settings -> Taxonomies Translation.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, please check 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. For further assistance, you can also visit our support forum at WPML support forum.
Problem: The client needed to delete French and German languages from their site using MySQL because the backend option was not functioning properly. They had already started removing language entries from specific WPML tables but were unsure where else to look for remaining translated content. Solution: We advised that directly modifying the database to remove languages can be complex and risky, especially since WPML integrates deeply with WordPress's default tables. Instead, we suggested: 1. Re-enabling the languages in WPML. 2. Using the WordPress UI to filter and delete the content for each language. 3. Cleaning up any remaining entries from WPML's string tables using a query like:
1
DELETEFROM wp_icl_string_translations WHERE language='de';
4. Checking additional tables like
1
wp_postmeta
and
1
wp_termmeta
for any leftover data. If these steps do not resolve the issue, we recommended trying to clean up the site in a minimal setup or allowing us to assist further by providing temporary admin and FTP access.
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 at WPML support forum.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
