Documentation request

Problem:
1. When properties are duplicated on your website, they do not display the same main selected image for each language on the front end.
2. When properties are translated with WPML, the system shows doubled options in the backend, such as two descriptions and two sets of fields for each property in the translated versions.
Solution:
To address these issues:
1. Install the ACF Multilingual add-on to ensure compatibility between ACF and WPML. You can find the add-on and setup instructions here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/
2. Increase your WordPress memory limit as it is below the minimum requirement. Add the following lines to your

wp-config.php

file, just before the line

/* That's all, stop editing! Happy publishing. */

:

define( 'WP_MAX_MEMORY_LIMIT', '256M' );<br />define( 'WP_MEMORY_LIMIT', '128M' );

Afterwards, verify the new memory limit under WPML > Support > WordPress > Memory limit.

If this solution does not resolve your issue or seems irrelevant, 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:
When switching to English, all texts remain in German, and the header is not visible.
Solution:
If you're experiencing issues with texts not translating and headers disappearing when switching languages, it's likely due to unregistered Elementor widgets. We recommend registering your custom Elementor widgets for translation. You can learn how to do this by following our guide on registering page builder widgets.

We have registered the elements in your header and footer, and they should now appear correctly translated. If you encounter untranslated content on other posts or pages, you should contact the theme authors to ensure they register the custom elements they created. You can refer them to the same guide.

Additionally, you can add the necessary XML code for registration in WPML -> Settings -> Custom XML Configuration tab as outlined in the guide.

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:
El cliente utiliza el traductor de WordPress clásico para productos, categorías y blog, pero desea automatizar las traducciones del blog que está en 5 idiomas, sin afectar las traducciones existentes.
Solution:
Si deseas automatizar las traducciones de tu blog sin afectar el contenido existente, puedes cambiar el método de traducción para entradas específicas, para todo el contenido del mismo tipo de publicación, o para todo el sitio. Puedes seguir utilizando el "Editor de WordPress" para algunos contenidos y optar por el "Editor de Traducción WPML" para otros. Sin embargo, si ya has creado traducciones con el Editor de WordPress o el Classic Translation Editor, estas no estarán disponibles si decides usar el nuevo Advanced Translation Editor. En este caso, necesitarás recrear todas las traducciones existentes. El Advanced Translation Editor ofrece ventajas como traducción automática, memoria de traducción, glosario y corrector ortográfico. Para más detalles, visita Editor de Traducción Avanzado.

Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable 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.

Problem:
The client is experiencing two issues with the localization of custom fields using WPML and ACF (Advanced Custom Fields):
1. A custom field is displayed with a lock icon and is set to translate, but it does not appear in the Advanced Translation Editor.
2. An ACF field that includes a document from the media library is not visible in the list.

Solution:
We first clarified whether the ACF plugin was installed since only the Advanced Custom Fields Multilingual bridge plugin was visible. It's essential to have both the ACF plugin and the bridge plugin installed for proper functionality. We recommended checking the installation of the ACF plugin at https://www.advancedcustomfields.com/ and also suggested reading our guide on translating sites built with ACF at https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.

If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
Si estás experimentando dificultades para configurar la redirección de tu servidor detrás de un proxy utilizando dominios en lugar de directorios, y no estás seguro de cómo proceder.
Solution:
Te recomendamos añadir el dominio adicional en la configuración DNS del servidor y asegurarte de que apunte al mismo alojamiento que el dominio principal. En la mayoría de los casos, deberías utilizar un registro A (A Record) para que el segundo dominio resuelva hacia la misma instalación de WordPress. Alternativamente, podrías usar un registro CNAME para apuntar el dominio secundario al principal. Sin embargo, esto podría requerir pasos adicionales como verificar que el certificado SSL cubra ambos dominios y que el servidor acepte peticiones para cada uno de ellos. Para más detalles, consulta nuestra guía sobre cómo usar WPML con diferentes dominios por idioma en https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/.

Si esta solución no es relevante para tu caso, porque podría estar desactualizada o simplemente no aplicable, 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 del arreglo permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.

Problem:
The client needs assistance in creating a United States version URL for their website using the structure: https://www.cybernx.com/en-us/. They require confirmation on server-side changes such as DNS, rewrite rules, redirects, caching, and any potential impacts on existing URLs or SEO. Additionally, they need to know if any security rules or firewall settings might block this URL.
Solution:
We recommend adding a new language with the en-US language code in the WPML's languages table. You can find guidance on how to do this here: Editing WPML's Languages Table. After setting up the language, translate the homepage into English (US). Your default language homepage will remain accessible at https://www.cybernx.com/, and the newly translated homepage will be available at https://www.cybernx.com/en-us/.

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 this does not resolve your issue, please open a new support ticket.