Bug

Problem:
The client is experiencing an issue where the WPML String Translation plugin disables the preview rendering in the Cornerstone content editor. When the WPML plugin is deactivated, the content can be edited without issues. A PHP Fatal error related to DOMDocument::loadHTML() was found in the debug log.
Solution:
We recommend the following steps to resolve the issue:
1. Navigate to WPML >> String Translation.
2. Open the 'Auto register untranslated strings' section.
3. Select the 'Disable auto register of untranslated strings' option.
4. Click the 'Save Settings' button.
5. Clear all site/server/CDN caches and check if the Cornerstone preview works.
If you're still experiencing issues or if this solution does not apply due to updates or changes, 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 for further assistance.

Problem:
If you're experiencing slow 'Save languages' actions in WPML when MasterStudy LMS is enabled, it's due to MasterStudy LMS rebuilding its routes and flushing rewrite rules during WPML's 'Save languages' AJAX request, which is a costly operation.
Solution:
To address this issue, we recommend modifying the MasterStudy LMS plugin. Here are the steps:
1. Navigate to

wp-content/plugins/masterstudy-lms-learning-management-system/_core/lms/classes/page_routes.php

.
2. At the beginning of the

init()

method, add an early return for AJAX requests to prevent route/page generation and rewrite flushing during admin-ajax. Replace:

public function init() {

with:

public function init() {<br />if (wp_doing_ajax()) {<br />// WPML - No routes/pages generation and no rewrite flushing during admin-ajax.<br />return;<br />}

3. Optionally, to reduce the frequency of flush_rewrite_rules, modify it to run only once by replacing:

flush_rewrite_rules(true);

in two places with:

update_option('stm_lms_routes_needs_flush', 1, false);

and add at the end of the file:

add_action('admin_init', function () {<br />if (get_option('stm_lms_routes_needs_flush')) {<br />delete_option('stm_lms_routes_needs_flush');<br />flush_rewrite_rules(true);<br />}<br />});

This solution is a workaround. A long-term fix should come from the MasterStudy LMS team. We will contact them to discuss this issue, but you can also reach out to them to expedite the process.

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 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:
When WPML is enabled and a visitor switches language to /en/, WordPress rewrites .htaccess with:

RewriteBase /en/

and routes requests to /en/index.php. There is no physical /en/ directory as language URLs are virtual. This causes REST API endpoints (/wp-json/, /wp-json/wp/v2/) to break and results in intermittent server-level 404 errors. Disabling WPML stops this behavior, and locking .htaccess prevents the rewrite but is only a workaround.

Solution:
This issue is likely related to a known problem where .htaccess gets overwritten with the language folder. We recommend you ensure to have a full website backup and apply the solution outlined in the erratum. You can find more details and guidance here: Why is .htaccess getting overwritten with the language folder on my WPML website?

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 the problem persists, please open a new support ticket at WPML support forum.

Problema:
Estás trabajando con Elementor Pro y WooCommerce y te encuentras con que el widget de elección de idioma no aparece en la página de la tienda, aunque sí en otras páginas, incluidas las de productos de WooCommerce. El widget está incrustado tanto en el header como en el footer creados con Elementor Pro. A pesar de que existen traducciones para la página, WPML no parece detectarlas.
Solución:
El problema está relacionado con el uso del slug "formacion", que inicialmente era el slug de la tienda de WooCommerce y luego cambió a "catalogo-de-cursos". Este cambio ha afectado la forma en que WPML maneja las traducciones para esa URL. Para resolverlo, verifica y ajusta las traducciones del slug en cuestión. Además, asegúrate de tener instalada la última versión de WooCommerce (10.5.1), ya que se ha identificado un problema relacionado que fue corregido en esta versión.

Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos y verifiques que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.