Problema: Si estás experimentando notificaciones al usar el modo incógnito, puede deberse a un código obsoleto que es más compatible con versiones anteriores de PHP. Esto puede afectar tanto a nuestros plugins como al tema Porto. Solución: Te recomendamos que cambies a la versión 7.4 o 8.0 de PHP, ya que es probable que no veas estos problemas con esas versiones. WordPress está actualizando su plataforma, lo que puede causar inconvenientes temporales, pero es para mejorar el sistema a largo plazo. Estamos al tanto de este problema y ya estamos en contacto con los desarrolladores para resolverlo. Si estás utilizando PHP 8.1 y deseas intentar una solución temporal, puedes modificar el plugin WPML Sticky Links. Ve a
if (!is_array($this->settings)){<br /> $this->settings = array();<br /> }
justo antes de:
$this->settings['sticky_links_widgets'] = 0;
Es posible que esta solución ya no sea relevante o no se aplique a tu caso. Si después de probar estos pasos sigues teniendo problemas, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, por favor, contacta con nosotros en el foro de soporte de WPML.
Problem: The client was experiencing an issue with translating templates using Bricks Builder and WPML. When attempting to translate certain templates by clicking the '+' sign, instead of initiating the Advanced Translation Editor (ATS), it redirected to the WordPress editor and changed the language in the admin bar. Additionally, when trying to edit with Bricks, the page appeared empty without copying the default language's content. Solution: We accessed the client's site and found that the translation jobs for the 'Single Member' template were not marked as in progress. We proceeded to delete the previous translations and duplicated the template to French and Arabic. After this, the content was successfully copied over, and the client could edit the translations using Bricks Builder as intended. If you're experiencing a similar issue, we recommend trying to delete the problematic translations and duplicating the template to your desired languages. This should allow you to edit the translations with the content copied over.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us.
Problem: The client is trying to translate products from Dutch to other languages after removing Visual Composer and is experiencing issues.
Solution: 1. We asked the client to provide more details or screenshots to better understand the issue. 2. We recommended deactivating all plugins except WPML, WooCommerce Multilingual & Multicurrency, and WooCommerce to check if the issue persists, reminding the client to back up the database first. 3. We identified that the 'Disable REST API' plugin installed on the client's website might be causing the problem, as WPML requires the WordPress REST API to function correctly. We advised the client to temporarily deactivate the 'Disable REST API' plugin, make a slight modification to the original content, save it, and then try saving the translation again in the WPML translation editor. For more information, we provided a link to the WPML documentation on REST API dependencies: https://wpml.org/documentation/support/rest-api-dependencies/. 4. We inquired if the content was created using WPBakery Page Builder and what happens when deactivating all plugins except the necessary ones for WPML and WooCommerce.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, 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 with us: Contact WPML Support.
Problem: The client was experiencing an issue where the dropdown menu was not showing in the second language. Solution: We resolved the issue by ensuring that the categories were set to translate and then translating them. Here's how you can do it: 1. Go to Appearance -> Menus. 2. Use the language switcher at the top to change languages, or click the pencil icon next to the languages at the top right. 3. Add the translated categories to your menu. 4. Expand each menu item to select which block should display in the translated menu.
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 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 you need further assistance, please do not hesitate to contact us in the WPML support forum.
Problem: The client needs to update the site/subscription key for their staging environments because they are experiencing issues with website connectivity to the WPML account, and translation jobs from staging are being sent as if they were from the production environment due to the usage of the same keys. The client is unable to access the Unregistration link on the staging website. Solution: We recommend registering the key directly in the
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and verify the version of the permanent fix. Also, confirm that you have installed the latest versions of themes and plugins. If you continue to experience difficulties, we encourage you to open a new support ticket in the WPML support forum.
Problem: The client had previously deactivated and deleted WPML and its additional plugins but found that there were still language files (French and English .json, .mo, and .po files) and a 'wpml' folder in the 'languages' directory within 'wp-content'. The client was unsure whether these files and the 'wpml' folder should be deleted and also inquired if deactivating and deleting WPML would remove related database tables. Solution: If you're not using WPML anymore, you can safely delete the related WPML files and folders. For detailed instructions on how to delete .mo and .po files for removed languages, please refer to our documentation:
Regarding the database tables, deactivating and deleting the plugin does not automatically remove them. You can use the reset option in WPML > Support > Troubleshooting to remove the tables if WPML is still installed. If you have already deactivated and deleted WPML, you will need to manually remove the tables from the database using PHPmyAdmin or a similar tool provided by your hosting platform.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at WPML 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 with us for further assistance.
Problem: The client was experiencing issues with WooCommerce products not displaying after translating them using WPML. The translated product pages were blank. Solution: We identified that the problem was due to a string that had been translated with variables, which caused a fatal error in WordPress. To resolve this, we recommended the following steps: 1. Navigate to WPML > String Translation; 2. Search for the "You must be" string; 3. Edit its translation and remove the variables, ensuring the final result matches the provided screenshot.
After following these steps, the website should function correctly.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also highly 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 further assistance is needed, please contact us through the WPML support forum.
Problem: The client was unable to view the Dutch version of a page on their website. Although the Dutch flag was visible when trying to switch languages in the front-end, clicking on it still resulted in the English page being displayed. Solution: We discovered that there was a 301 redirect from the Dutch URL to the English one, which was set up using the Redirection plugin. We disabled this redirect, and after doing so, the Dutch page became accessible.
If you're experiencing a similar issue where you can't switch to a different language version of a page on your site, we recommend checking for any redirects that might have been created with redirection plugins. If you find one, try disabling it to see if that resolves the issue.
Please note that this solution might not apply to your case, or it could be outdated. If after trying this step you still encounter problems, we highly 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 the issue persists, please open a new support ticket with us for further assistance.
Problem: If you're experiencing an issue where the automatic translation is stuck, it might be due to a corrupted entry that prevents the translation status from updating correctly.
Solution: We recommend the following steps to resolve this issue: 1. Go to the pages section. 2. Switch to the secondary language using the top admin bar. 3. Delete the page translation. 4. Also, delete it from the Trash. 5. Switch back to the primary language. 6. Translate the page again manually. Since the translation memory should have the content, it won't consume additional credits. Mark it as completed in the Advanced Translation Editor (ATE).
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket.
Problem: The client was experiencing issues with translating Advanced Custom Fields (ACF) because the translation mode for the fields was not selected. Solution: We accessed the client's field groups and selected the appropriate translation mode for the fields. We then instructed the client to update the post in the default language and its translation. We also provided a guide for translating ACF fields: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.
If you're experiencing a similar issue, we recommend checking the translation mode for your ACF fields and ensuring they are set correctly. After that, update your post in the default language and its translation. For detailed guidance, please refer to our documentation on translating ACF fields.
Please note that this solution might be irrelevant if it's 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 you still need assistance, please don't hesitate to open a new support ticket in our forum: https://wpml.org/forums/forum/english-support/.
Problem: The client is unable to log into the WordPress admin panel without entering recovery mode due to an error with WPML Multilingual CMS plugin.
Solution: We recommend creating a full website backup before proceeding. Then, deactivate and delete the current WPML plugin. Manually download the latest version of WPML from here by selecting "Download WPML manually". After downloading, install and activate the plugin to potentially resolve the error.
If this solution does not apply to your situation, or if it's outdated, we suggest checking the related known issues, verifying the version of the permanent fix, and ensuring that you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket with us.
Problem: The client was experiencing a fatal error when trying to synchronize attributes and translate products in bulk using WPML and WooCommerce. The error was a TypeError in
wc-attribute-functions.php
indicating that an array was given where a string was expected.
Solution: We recommended the following troubleshooting steps: 1. Navigate to WPML -> Support -> Troubleshooting and perform the following actions: - Synchronize posts taxonomies (for products and then for variations) - Clear the cache in WPML - Remove ghost entries from the translation tables - Set language information - Fix terms count - Fix post type assignment for translations
If the issue persists, we suggested: 1. Installing the Adminer plugin to investigate the database entries for the problematic product IDs. 2. Checking if the mentioned product IDs are valid and not in a corrupted state. 3. Bulk editing products in WordPress to potentially fix corrupted data.
If these steps do not resolve the issue, we advised the client to open a new support ticket for further assistance. 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.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, please do not hesitate to open a new support ticket with us for personalized assistance at WPML support forum.
Problem: The client was unsure if WPML inserts Hreflang tags directly into the raw HTML or via JavaScript, as some tags seemed to only appear after rendering when using crawling software. Solution: We insert Hreflang tags directly into the HTML using the
wp_head
hook from WordPress.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client is experiencing a permissions error when trying to access the 'OTGS Installer' option and encounters an error when updating the WPML plugin, which causes the site to stop working.
Solution: 1. We recommend deleting the OTGS Installer since it's no longer necessary if WPML is already installed. Use the Plugins > Add New > Commercial tab to add extra plugins, or manually download them from our site and upload them via Plugins > Add New > Upload.
2. Check for compatibility issues by reviewing a similar ticket and following the steps provided there. Also, ensure that you are using the latest WPML version by comparing your current version with the latest one available.
3. Create a full website backup, update all plugins and the theme to the latest versions, and then disable all plugins except WPML.
4. If updating from the backend is not possible due to an old plugin version, manually update by first creating a full website backup, then deactivating and deleting the old plugin. Download the latest version from here and install and activate it manually.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket in the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
