Problem: You have changed the slug for your posts page to 'ideas', and your permalink structure is set to /ideas/%postname%/. However, the translated posts still display 'ideas' in the URL instead of the translated version. Solution: We currently do not support translating custom permalink structures directly. As a workaround, you could consider using a Custom Post Type (CPT), as CPT archive slugs can be translated. If switching to a CPT is not feasible, you might: 1. Create a category with the desired slug. 2. Assign this category to all relevant posts. 3. Update your permalink structure to include the category. Since category slugs can be translated, this method allows you to achieve a multilingual URL structure. For more details, please refer to our guides on Translating page slugs and Translating post categories and custom taxonomies.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problema: El plugin WPML no es compatible con el template que el cliente está utilizando, y no se muestra correctamente. Solución: Si el cliente compró o renovó WPML en los últimos 30 días, puede solicitar un reembolso completo a través del siguiente enlace: https://wpml.org/purchase/refunds/. Además, recomendamos revisar los temas y plugins que son compatibles con WPML para evitar problemas de compatibilidad en el futuro. Puedes encontrar la lista completa de temas compatibles aquí: https://wpml.org/theme/ y de plugins aquí: https://wpml.org/plugin/.
Si esta solución no es relevante porque está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente verificar 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. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte: https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problema: El cliente no podía ver el footer en la página en inglés de su sitio web. A pesar de seleccionar el idioma inglés y editar el footer desde Apariencia > Widgets, los cambios solo se reflejaban en la página en español. Además, cada cambio en el footer causaba que el selector de idiomas desapareciera del menú. Solución: Primero, se solicitó al cliente que verificara y tradujera las cadenas del footer siguiendo los pasos de nuestra guía de traducción de cadenas, disponible en https://wpml.org/es/documentation-2/guia-de-inicio/traduccion-de-cadenas/buscar-cadenas-que-no-aparecen-en-la-pagina-traduccion-de-cadenas/. Después de revisar la configuración del sitio con las credenciales proporcionadas por el cliente, descubrimos que el widget del footer estaba corrupto. Reemplazamos el widget por uno nuevo y lo tradujimos utilizando WPML -> Traducción de Cadenas, resolviendo así el problema. Adicionalmente, recomendamos leer nuestra guía sobre cómo traducir widgets con WPML en https://wpml.org/es/documentation-2/guia-de-inicio/traduccion-de-widgets/.
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 en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client is experiencing issues with widgets being disorganized after changing the default language. They are unable to translate widgets independently, specifically headers and footers, and are facing difficulties with translating WooCommerce settings for emails. Additionally, the shop page URL is broken, and attempts to modify settings with WPML result in further disruptions. Solution: For the shop page URL issue, since the shop page was initially created in English, you can directly edit its URL in the page editor. To modify the translation's URL (for Bulgarian, in this case), you need to enable the Page URL translation in WPML > Settings. Choose "Translate (this will include the slug in the translation and not create it automatically from the title)" under "Translated documents options". After enabling this, you can change the translated page URL inside WPML's Translation Editor. For more details on translating slugs, visit Translating Page Slugs documentation.
Please note, you should not directly edit a translated page slug via the WordPress Editor.
If this solution does not resolve your issues 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 problems persist, please open a new support ticket.
Problem: Nach einem Update wird ein neues Produkt in Deutsch erstellt und ins Englische übersetzt. Obwohl die Übersetzung als vollständig angezeigt wird, bleibt das englische Produkt im Entwurf, wenn das deutsche Produkt veröffentlicht wird. Solution: WPML unterstützt keine automatische Synchronisierung des Produktstatus zwischen den Sprachen. Sie müssen den Status Ihrer übersetzten Produkte manuell ändern. Alternativ können Sie ein inoffizielles Plugin verwenden, das diese Funktionalität bietet. Beachten Sie jedoch, dass dieses Plugin keine offizielle Lösung ist und möglicherweise die Leistung auf großen Websites beeinträchtigen kann. Hier ist der Link zum Plugin: https://github.com/OnTheGoSystems/wpml-synchronize-post-status
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen Ihnen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The client is experiencing issues with widgets being disorganized after changing the default language. They are unable to translate widgets independently, including headers and footers. Additionally, there are problems translating WooCommerce settings for emails, and the shop page layout is broken after changes made with WPML. Solution: For translating WooCommerce emails that have been customized or newly created, follow the steps provided in the WPML documentation on translating WooCommerce emails.
If you're experiencing similar issues with widget translation or layout problems after using WPML, 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 is outdated or not applicable to your case, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where the site key does not match when trying to register their WPML product on a multisite network. Solution: If you're encountering a similar issue, we recommend registering your main site first as the same site key applies to all subsites in a multisite network. There is no need to register each subsite separately. Follow these steps: 1. Delete all existing site keys. 2. Create a new site key (just one for the entire multisite). 3. Register the multisite with this new key. 4. Assign credits to the newly created site key. For detailed guidance on registering WPML in a multisite setup, please visit WPML Multisite Registration Documentation. Additionally, if you need to connect a subsite to the main site using a migration code to share its credits, please refer to How to Connect Your Sites.
Please note that this solution might be irrelevant if it's 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.
