Problem: The client reported an issue where incorrect translations of strings with placeholders (like those used in
sprintf
or
printf
functions) caused errors on a PHP 8.x environment. This resulted in an inability to place orders in the shop due to a missing placeholder in the translated string. Solution: We acknowledged the client's feature suggestion for WPML to scan strings in the string translation table for missing placeholders. However, after reviewing the suggestion and monitoring for similar issues, we have decided not to implement this feature. We have not observed other clients experiencing this problem, and our development team has chosen not to prioritize this as a future feature.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still encountering issues, we highly recommend checking the related 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 with us.
Problem: The client is trying to include superscripts for correct legal translations in WPML, but the Advanced Translation Editor (ATE) changes it to a normal "o". When using
<sup>o</sup>
, ATE does not allow saving and deletes the character completely. Solution: We informed the client that the ATE does not support the direct insertion of HTML characters unless they are included in the source text. We have an existing feature request for the ability to add or remove HTML markup in the ATE, and we have added this ticket to that request for internal tracking. Currently, the only way to add HTML into translations is through the Classic Translation Editor, which allows for the addition of HTML tags. For more information on the Classic Translation Editor, please refer to the following guide:
As an alternative, we suggested using the Degree Symbol (°) in the ATE to achieve the desired representation in the translation.
If this solution is not relevant to your case, because it might be outdated or not applicable, 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 you still need assistance, please do not hesitate to open a new support ticket. You can reach our support forum here: WPML Support Forum.
Problem: The client inquired about WPML's compatibility with the new Performant Translations feature that will be included in the upcoming WordPress 6.5 update, which aims to improve website performance with translations. Solution: We always ensure that WPML is compatible with major WordPress core updates. We have already tested WPML with the Performant Translations feature and found that it indeed improves site performance when using WPML. If you're experiencing issues or have concerns about compatibility, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If you encounter any problems, we encourage you to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: Der Kunde möchte, dass Übersetzer die Seiten und Beiträge anderer Übersetzer übersetzen können. Dies ist standardmäßig nicht möglich und die bisherigen Lösungen im Forum sind nicht update-sicher oder nachhaltig. Der Kunde verwendet das Plugin "Members", um benutzerdefinierte Rollen zu erstellen, und sucht nach einer Lösung, die es Übersetzern mit eingeschränkten Rollen ermöglicht, Übersetzungen anderer zu aktualisieren. Lösung: Wir haben bestätigt, dass es derzeit keine Lösung gibt, die über eine Child Theme's
functions.php
Datei implementiert werden kann. Wir haben jedoch in unserer Entwicklungs-Warteschlange gesehen, dass dieses Problem möglicherweise in der nächsten Version 4.6.9 von WPML behoben wird. Wir empfehlen, auf dieses Update zu warten, da es den gewünschten Mehrwert bieten könnte.
Wenn diese Lösung nicht relevant erscheint, öffnen Sie bitte ein neues Support-Ticket im WPML-Supportforum.
2. Create a new page and add the lazyblock with the necessary information, including the link. 3. Save and translate the page to the desired language. 4. In the Advanced Translation Editor (ATE), the URL should automatically set to the translated version. 5. Translate the remaining content and complete the translation. 6. The link should now point to the translated version of the page in the new language.
However, if you encounter a limitation where the URL inside the block attribute does not adjust automatically, you will need to translate the links manually in the Advanced Translation Editor.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem:
Der Klient schlug vor, ein SVG-Symbol anstelle des aktuellen PNG-Symbols für das WP-Admin-Menü zu verwenden und lieferte eine detaillierte Lösung, wie dies umgesetzt werden könnte.
Solution:
Wir haben den Vorschlag des Klienten als Feature Request an unser Entwicklungsteam weitergeleitet. Wir hatten bereits die Möglichkeit, SVG-Symbole zu verwenden, in Betracht gezogen und es besteht die Möglichkeit, dass dies in zukünftigen Versionen von WPML implementiert wird. Wir danken dem Klienten für das Feedback.
Problem: The client is trying to set up a custom role for site editors to manage translations without giving them super admin permissions. They have used the User Role Editor plugin to configure the role but are unable to see the edit button for translations in the backend or frontend, despite following the steps in the provided documentation and ensuring all checkboxes are enabled. Solution: We recommend updating WPML to the latest version, as this issue has been addressed in version 4.6.9. Before updating, ensure to create a complete backup of the site. For more details on the issue and the fix, please refer to the errata page:
Problem: The client is experiencing an issue where users with custom roles are unable to edit specific posts/pages that were translated by another user. They have tried using the Custom Role Editor plugin and creating custom roles programmatically, but the issue persists. They have also tried using code from the WPML forums to enable the editor role to translate, but it only works for default WordPress roles, not custom ones.
Solution: We recommend updating to the latest version of WPML, as this issue should be resolved in version 4.6.9. Before updating, ensure to have a complete backup of your site. You can find more information about this issue on our errata page:
Problem: The client's content managers, responsible for translations, lost access to posts and pages after an update, receiving a message stating they do not have the rights to translate from NL to ES. Solution: We recommend updating to the latest version of WPML, as this issue should be resolved in version 4.6.9. Before updating, ensure to have a complete backup of your site. For more information, please refer to our errata page: WPML custom role based on the editor role cannot edit translations and behave as editor.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us for further assistance: Contact WPML Support.
Problem: The client reported that the support links in email notifications for WPML forum tickets were not directing to the specific comment in the forum thread as they used to.
Solution: We acknowledged the issue and forwarded the details to our systems team for investigation. After the systems team implemented the necessary changes, we asked the client to verify if the email links for forum ticket notifications were now functioning correctly.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client is experiencing accessibility issues with the language switcher on their website, as indicated by the PageSpeed Insights test. Solution: We acknowledge an existing internal development ticket regarding this issue, but we cannot provide a specific timeline for its resolution. We suggest adding an
aria-label
attribute with a descriptive name to the language switcher link to improve accessibility, like so:
<a href="https://www.spotix.app/he/spots/..." class="wpml-ls-link" aria-label="Descriptive Name of the Link"></a>
Additionally, we recommend checking the following documentation for a potential workaround regarding missing alt tags for flag images in the language switcher: Missing alt tag for flag image in a language switcher
