Problem: The client created a custom language, Afrikaans, with the code af-za by mistake and needs it to be /af/ to match the site they are migrating. They have already translated content and cannot start over but are unable to change the language code in WPML. Solution: Unfortunately, you cannot directly change the language code of an existing custom language in WPML. However, you can preserve your translations by transferring them to a new custom language with the correct code. Here are the steps to do this safely: 1. Navigate to WPML → Languages and add a new custom language for Afrikaans with the correct code (/af/). 2. Manually transfer your translations from the old language code (af-za) to the new one (/af/).
If this solution does not apply to your case, or if it seems outdated, we recommend checking the 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 our support forum.
Problem: You are experiencing an issue where the JupiterX popup does not function when WPML is enabled on your site. The popup worked previously but now fails to display expected images on the bottom of the screen. Solution: We could not replicate the issue in our sandbox environment. However, we recommend toggling the 'translatable' setting off and then on again for the content type associated with the popup. This action resolved the issue in our tests.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current setup, please visit our known issues page to check for related issues. Ensure you have the latest versions of your themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: The client is experiencing issues with navigation when trying to sync menus using WPML on their site. The WP Memory Limit is set to 40 MB, which is below the minimum required for WPML (128 MB), potentially causing the problem. Solution: 1. We recommend increasing the WP Memory Limit to at least 128 MB, ideally to 256 MB, to ensure smooth operation of WPML, especially with translations or high traffic. Here’s how to do it: - Open your site’s
wp-config.php
file (usually found in your WordPress root directory). - Add the following line just before the comment that says: // That's all, stop editing! Happy blogging.
define('WP_MEMORY_LIMIT', '256M');
- Save the file and re-upload it if you edited it locally. 2. After updating the memory limit, verify the new setting in Tools → Site Health → Info → WordPress Constants to ensure it displays 256M (or at least 128M). 3. For further guidance on translating menus, please refer to our detailed guide: Translating Menus 4. If the issue persists or if the navigation problem specifics were not addressed, please describe your specific issue in more detail, possibly with screenshots or a video link.
If this solution does not resolve your issue or seems irrelevant, it may 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 needed, do not hesitate to open a new support ticket for personalized assistance at WPML Support Forum.
Problema: El cliente está intentando que Yoast genere los sitemaps correctamente en su sitio multilingüe, pero encuentra que Yoast aplica el mismo slug del idioma en curso en todos los hreflang de idiomas alternativos, lo que resulta en URLs incorrectas en los sitemaps de cada idioma. Solución: 1. Desactivar todos los plugins excepto WPML y Yoast. 2. Activar un tema por defecto de WordPress. 3. Activar la opción de generar sitemaps de Yoast en los ajustes. 4. Verificar que el sitemap ahora muestra correctamente las URLs traducidas para cada idioma. 5. Si el problema persiste, crear un sitio de staging para realizar pruebas sin afectar el sitio en producción. 6. Si se utilizan diferentes dominios por idioma, se generarán sitemaps separados para cada idioma, de lo contrario, solo habrá un sitemap por sitio. Para más detalles, revisa nuestra documentación oficial en https://wpml.org/documentation/plugins-compatibility/using-wordpress-seo-with-wpml/#create-multilingual-sitemaps.
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/ y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client is working on optimizing a real estate site and has encountered issues with Google's PageSpeed Insights, which indicates that the WPML Browser Redirect feature is causing performance problems due to legacy JavaScript. This issue is affecting the mobile score, reducing it to below 90. Solution: We explained that modifying the Browser Redirect script to exclude legacy JavaScript would limit functionality to only modern browsers, which is not ideal as we aim to support a wide range of browsers. Additionally, we noted that using browser redirects could negatively impact SEO and Google indexing. Therefore, we recommended considering the deactivation of this feature if it is not essential for the client's needs. For more details on how browser language redirect can affect Google indexing, please visit our documentation.
If this solution does not apply to your situation, 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 our support forum.
Problem: The client is working on a site under development and needs to stop two ACF fields from being automatically translated, which are currently locked. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to ACF >> Field Groups. 2. Edit the field group containing the fields you wish to update. 3. Set the “Expert” translation option for that field group. 4. Individually edit each field and set the “Translation preferences” to “Copy” if you want the same default language value to appear in secondary languages. If you prefer not to display anything in a secondary language, select the “Don't translate” option. 5. Click the Save Changes button. 6. Re-save the default language pages to apply the updated settings. For more detailed guidance, check the documentation here: Recommended Custom Fields Translation Preferences for ACF and WPML.
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.
Problem: Der Klient konnte die Texte für die Startseite, die in den Theme-Einstellungen (The Kerge) definiert sind, nicht in der WPML String-Übersetzung finden. Er erwartete, diese Texte im Übersetzungs-Dashboard unter den anderen Texten zu finden, konnte sie jedoch nicht auffinden. Solution: 1. Wir empfehlen, zuerst sicherzustellen, dass alle WPML-Plugins auf dem neuesten Stand sind. Dies kann unter Plugins > Plugin hinzufügen > Kommerziell > Nach Updates suchen überprüft werden. 2. Um den fehlenden String zu finden, sollte der Klient zu WPML > Übersetzungs-Dashboard > Andere Texte (Zeichenketten) gehen und das Textsuchfeld verwenden. Wenn der String dort nicht erscheint, kann er über ein Dialogfeld, das Texte aus Adminbildschirmen sucht, hinzugefügt werden. 3. Es ist auch möglich, dass das WP Memory Limit zu niedrig ist. Wir empfehlen, das WP Memory Limit auf mindestens 256 MB zu erhöhen, indem folgender Code in die
wp-config.php
Datei eingefügt wird:
define ('WP_MEMORY_LIMIT', '256M');
4. Sollte das Problem weiterhin bestehen, könnte ein Update des Themes helfen. Informationen zu Theme-Updates finden sich hier: Theme-Update.
Falls diese Lösungen nicht relevant sind oder das Problem weiterhin besteht, empfehlen wir, ein neues Support-Ticket zu eröffnen und die aktuellsten Versionen von Themes und Plugins zu überprüfen. Besuchen Sie auch unsere Seite zu bekannten Problemen unter https://wpml.org/known-issues/.
Problem: The client is confused about the number of credits available versus credits assigned for automatic translations on their WPML account. They see 80,000 credits available but only 622 assigned to their site, and they are unsure how to manage these credits. Solution: We explained that the client has 80,000 credits available in their WPML.org account. Initially, the site had 12,000 credits assigned, of which 11,378 have been used, leaving 622 credits remaining. The client can transfer credits between their WPML.org account and their site using the 'add/remove credits' button. In total, including bonus credits and monthly credits, the client has received 92,000 credits from WPML. For detailed steps on how to assign credits, we recommend visiting our documentation: How to Assign Automatic Translation Credits to Your Sites.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is building a multilingual website using ACF and Bricks Builder and has encountered issues where the Bricks design is not loaded into the newly made page in other languages. Additionally, they are experiencing unwanted automatic translations. Solution: To resolve these issues and set up the website as before, follow these steps: 1. To disable automatic translation, navigate to WPML > Translation Dashboard and pause the 'Translate everything' mode. 2. From the same dashboard, go to the Jobs tab and cancel any ongoing translation jobs. 3. Edit your ACF field group and at the top, select 'Different fields across languages' to ensure correct translation settings. For more detailed guidance, visit Translate sites built with ACF and Recommended custom fields translation preferences for ACF and WPML. 4. To manually translate pages, edit your default language page, switch to the WordPress editor, and make this change permanent for pages or all website content. For more information, visit Using different translation editors for different pages. 5. Ensure you also translate other relevant content such as templates or menus.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If problems persist, we recommend opening a new support ticket for further assistance.
Problem: The client is unable to see the custom floating language switcher on their site despite following the provided instructions and using WPML's built-in tools.
Solution: 1. Verify PHP Code: Ensure the PHP code for the language switcher is correctly placed in the active theme's functions.php file. Check for correct hooking into the 'wp_footer' action and absence of syntax errors.
2. Check for PHP Errors: Look for any PHP syntax errors that might prevent the functions.php file from executing. Consider testing with a default WordPress theme like Twenty Twenty-One to see if the switcher appears.
3. Clear Cache: Clear any caching mechanisms to ensure changes are reflected immediately.
4. Plugin Conflicts: Deactivate all non-essential plugins to rule out conflicts. Reactivate them one by one to identify any issues.
5. Inspect Footer: Use browser tools to inspect the footer for any output related to the switcher.
6. WPML Settings: Confirm that WPML is properly set up and all necessary modules are activated.
If these steps do not resolve the issue, the client may need further personalized assistance. It is recommended to check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure that the latest versions of themes and plugins are installed. If the problem persists, please open a new support ticket at WPML support forum for more targeted help.
