Problema: Cuando el cliente duplica un producto, el permalink de los otros idiomas permanece con el permalink de la copia del producto, incluso después de editar el permalink del producto en el idioma base. El cliente necesita cambiar esto de forma masiva ya que tiene más de 4000 productos. Solución: 1. Verificar la configuración de WPML para cómo maneja los slugs de las URL: - Ir a WPML → Ajustes. - Desplazarse hasta la sección Opciones de traducción de documentos. - Buscar la opción URL de la página (slug) y asegurarse de que la opción seleccionada sea Copiar del idioma original. 2. Si esta opción ya estaba seleccionada y los permalinks no se actualizan correctamente, es necesario investigar un script o consulta SQL para actualizar en masa los slugs de los productos duplicados para que coincidan con el idioma base. 3. Verificar cómo los cambios en la configuración de WPML afectan a los productos ya duplicados y buscar ganchos o funciones de WPML que puedan desencadenar la sincronización masiva de slugs/permalinks.
Si esta solución no es relevante para tu caso, porque podría estar desactualizada o simplemente no aplicarse a tu situación, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problema: Necesitas ayuda para hacer que el icono de Ally Accessibility aparezca en otros idiomas además del inglés. Solución: Para ayudarte mejor, necesitamos más detalles sobre el problema: 1. Comparte el enlace de la página problemática o una captura de pantalla para entender mejor el problema. 2. Indica si el icono se añadió mediante un shortcode, un bloque, o automáticamente por Ally. 3. Confirma si el icono desaparece en todos los idiomas secundarios o solo en algunos específicos. 4. Por favor, añade el informe de depuración en el cuadro de Información de depuración. Hemos habilitado este cuadro para tu próxima respuesta: https://wpml.org/faq/provide-debug-information-faster-support/
Si esta solución no es relevante porque está desactualizada o no se aplica a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Problem: The client is experiencing intermittent high CPU usage spikes on their VPS hosting a multilingual website using WPML. Despite optimizing the site and deactivating most plugins, the issue persists. The client suspects WPML might be causing these CPU consumption problems. Solution: We recommended the following steps to address the high CPU usage potentially caused by WPML: 1. **Increase the WordPress Memory Limit:** - Access your site files via FTP or your hosting file manager. - Locate the
wp-config.php
file at the root of your WordPress installation. - Edit the file and add the following line of code just before the line that says
/* That's all, stop editing! Happy blogging. */
:
define('WP_MEMORY_LIMIT', '256M');
- Save the changes. 2. **Run WPML's troubleshooting tools:** - Go to **WPML → Support** in your WordPress dashboard. - Scroll down to the **Troubleshooting** section. - Perform the following actions one by one, waiting for each to complete before starting the next: 1. **Clear cache** 2. **Sync post taxonomies** 3. **Remove ghost entries** 4. **Fix element collation** 5. **Fix WPML tables collation** 6. **Set language information** 7. **Fix terms count** 8. **Cleanup and optimize string tables**
After completing these steps, monitor your VPS's CPU usage to see if the spikes persist. If the problem continues, 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 solution provided here becomes irrelevant or if the issue persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an error message after updating WPML, stating that the WordPress REST API must be enabled, despite it being accessible. The issue was compounded by hosting restrictions that blocked certain countries, potentially affecting the REST API's functionality. Solution: 1. We advised the client to contact their hosting provider to check access permissions to their site. 2. We suggested temporarily disabling any restrictions, flushing any cache, and then checking if the issue was resolved. 3. We recommended that the client ask their hosting provider to whitelist wpml.org and ate.wpml.org. 4. We confirmed that it was acceptable to temporarily activate plugins that might be blocking communication with our servers, but to be aware that these could be causing the issue. 5. We clarified that WPML needs to communicate with our servers for managing translations and updates, which is normal for large WordPress plugins. It's not necessary to remove all restrictions, just those that prevent communication with WPML servers.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket.
Problem: As a site admin, you're finding it difficult to edit product translations in WPML. After selecting a product in WPML > Translation Management, you're unsure how to proceed with translating it. Additionally, sometimes the WPML Advanced Translation Editor (ATE) shows the translated content as empty even though it exists on the front end. Solution: This issue arises due to how WPML's translation memory utilizes fuzzy matching. When you update the original content, WPML attempts to match the new content with existing translations. If the changes are significant, or if a close match isn't found, the ATE may display the translation fields as empty, requiring a re-translation of the content. This is to prevent inconsistencies in translations. For more detailed information, please visit how WPML keeps track of your translations.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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.
