Feature request

Problem:
Después de actualizar WPML, el elemento de bandera en el menú ahora incluye un atributo

role="menuitem"

, que es marcado como incorrecto por Google PageSpeed Insights porque no está contenido dentro de un elemento con

role="menu"

.
Solution:
Para resolver este problema, puedes eliminar o modificar el atributo

role

del selector de idioma en el menú mediante un filtro personalizado. Aquí tienes un ejemplo de cómo hacerlo:

add_filter( 'wpml_ls_menu_items', function( $items, $args ) {<br />    foreach ( $items as &$item ) {<br />        unset( $item['attributes']['role'] );<br />    }<br />    return $items;<br />}, 10, 2 );

Este código debe añadirse al archivo functions.php de tu tema hijo. Además, estamos considerando ajustar este comportamiento en futuras versiones de WPML para evitar problemas similares.

Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Si el problema persiste, no dudes en abrir un nuevo ticket de soporte. Estamos aquí para ayudarte.

Problem:
The client wants to display only the non-active language in the WPML Language Switcher Block within a block-based menu using the twentytwentyfour Theme, but cannot find the setting to achieve this.
Solution:
Currently, it is not supported to hide the current language in the Language Switcher block. This feature has been requested and the client's ticket has been linked to the feature request for additional support. Meanwhile, we recommend trying the workaround suggested in this forum thread: https://wpml.org/forums/topic/i-would-like-the-language-switcher-show-the-name-of-the-other-language-not-the-active-one/#post-16378075

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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.

Problem:
The client has created an ACF Options page with a field group intended for use across all language versions without translation. However, the

get_field()

function returns null for all languages except the default one, even after setting the field to 'Don't translate' and disabling the ACFML plugin.
Solution:
We have acknowledged this issue and escalated it to our second-tier team for further investigation and resolution. The feature request concerning non-translatable ACF Options pages is under review, and the client's ticket has been linked for tracking purposes. We will update the client as soon as there is any progress.

If this solution becomes outdated or does not apply to your case, we recommend opening 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. For further assistance, please visit our support forum at WPML support forum.

Problem:
When using Gutenberg to create a page and translating it with the Advanced Translation Editor (ATE), if you later edit the heading in the original language, the corresponding translated field in ATE becomes empty.
Solution:
Currently, this behavior is expected and there is no direct way to retain the old translations in ATE after changes are made in the original language. However, we have already submitted a feature request to our development team. Your ticket has been added as an additional vote for this request, which will be considered in future updates.

If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.

Problem:
The client is unable to translate URLs using WPML on their website.
Solution:
If you're experiencing issues with translating URLs using WPML, we recommend checking if your scenario matches the one discussed in this forum thread: https://wpml.org/forums/topic/bulk-translate-existing-pages-to-spanish-slugs-using-their-title/#post-17042792.
You might find it helpful to add the suggested code and resend translations. If you have only a few pages to translate, consider using the Quick Edit feature in WordPress or the WP Sheet Editor plugin, which can be found here: https://wordpress.org/plugins/wp-sheet-editor-bulk-spreadsheet-editor-for-posts-and-pages.

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