Problem: The client was experiencing issues with custom fields not displaying correctly after translating pages using WPML's Advanced Translation Editor (ATE). The content from some custom fields was serialized in the database, which prevented it from displaying correctly in the WordPress editor. Solution: We identified that the serialization of complex custom field keys in the database was causing the issue. To resolve this, we applied a specific solution from the WPML errata. Here are the steps we followed: 1. Opened the page for editing in the default language (English). 2. Made a minor change in one of the text fields in the "Page problem tab". 3. Saved the changes. 4. Updated the Hebrew and Arabic translations in ATE. 5. Checked the "Page problem tab" fields by switching to Hebrew and Arabic in the WordPress editor to ensure the fields displayed correctly. For existing pages with issues, repeating these steps should resolve the problem. Additionally, we recommend bookmarking the errata page for future reference and subscribing to comments for updates on permanent fixes.
Please note that this solution might be outdated or not applicable to your specific 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 at WPML support forum for further assistance.
Problem: If you're experiencing an internal server error when trying to translate pages using WPML, particularly with pages containing images without metadata, this might be due to a known issue. Solution: We recommend waiting for the upcoming WPML 4.8.1 update, which addresses this issue. You can check the progress and details of this known issue on our errata page: WPML 4.8 Fatal Error When Translating Pages Containing Images Without Metadata.
If this solution does not apply to your case, or if it seems outdated, please open 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.
Problem: If you're experiencing a 404 error on your WooCommerce category page due to a compatibility issue with Rank Math, it might be related to the 'Remove parent slugs' option or incorrect slug translations for different languages. Solution: 1. Check if the 'Remove parent slugs' option in Rank Math is causing the issue. A temporary fix can be found in our errata: https://wpml.org/errata/rank-math-seo-remove-parent-slugs-option-causes-category-slug-translation-error-404/ 2. If the issue persists, you may need to adjust the slug translations: - Navigate to WPML > Settings > Slug translations and ensure it is enabled. - Go to WPML > Taxonomy Translation > Product Categories and check the slug translations for each language. - Ensure that the slug translations are either blank or a copy of the original WordPress settings: 'product-category'. 3. If you have modified the Rank Math plugin files as a workaround, ensure to update the slug translations accordingly. You might need to edit the original pages and update the translations in the Advanced Translation Editor.
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.
Problem: In WooCommerce, when admins process orders with their profile language set to English, it causes the product to switch to the English version, affecting product IDs and language in PDF orders. Solution: We recommend updating to the latest versions of WPML, String Translation, and WCML, which include fixes for this issue. Before updating, please ensure to take a full backup of your website and database. It is also advised to perform this update on a staging or development site first to avoid any disruptions to your live website.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing a conflict between WooCommerce bookings and WPML plugins, which was resolved temporarily by deactivating the 'WooCommerce Multilingual & Multicurrency' plugin. Solution: We recommend trying the beta version of the WPML plugin to see if it resolves the issue. If the problem persists, we suggest setting up a staging site with minimal settings to further diagnose the issue.
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 issue continues, please open a new support ticket at WPML support forum for further assistance.
Problem: El cliente estaba enfrentando un problema con las páginas de categorías de portfolio que no se mostraban, usando el theme Avada. A pesar de haber borrado una línea de código sugerida en la documentación de WPML para errores similares, el problema persistía. Solution: Identificamos que el problema se debía a que todos los slugs de las taxonomías coincidían con el slug del tipo de entrada, ambos configurados como 'film'. Para resolver esto, recomendamos cambiar los slugs en Ajustes -> Enlaces permanentes -> Opcional (https://ouffestival.gal/wp-admin/options-permalink.php). Aconsejamos al cliente modificar estos slugs a algo distinto de 'film' para evitar conflictos.
Si esta solución no resuelve tu problema, o si parece desactualizada o inaplicable a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos relacionados, verifiques la versión de la solución permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
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.
