Problem: The client is concerned about the convoluted HTML structure generated by WPML, specifically the excessive classes within the language switcher elements, and is seeking a simpler structure.
Solution: We acknowledge the client's concern and explain that the current structure is maintained for backward compatibility. However, we are open to considering this as a feature request and will register it in our system for potential review and implementation in the future. In the meantime, we recommend creating a custom language switcher by following the instructions in our documentation: Custom Language Switcher.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we encourage you to 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. If further assistance is needed, please contact us through the WPML support forum.
Problem: The client wants to know if it's possible to bypass the frontend step when sending a login to a translator for review, allowing direct access to the advanced editor from the backend to save time. Solution: We currently do not have a feature that allows direct access to the advanced editor from the backend without going through the frontend. We have taken note of this request and suggested it as a feature request.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If this is the case, we recommend opening a new support ticket. We also 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. If you need further assistance, please contact us on the WPML support forum.
Problem: The client is experiencing issues with WPML where text breaks randomly, and paragraphs start with the previous paragraph's punctuation. Additionally, there are unwanted tags displaying that cannot be assigned to text in the translation.
Solution: We observed that the original text is highly formatted, which results in content being broken into different HTML tags such as
SPAN
,
A
, and others. This is expected behavior in the Advanced Translation Editor (ATE) when dealing with formatted text. The ATE highlights text with formatting markers to allow the same styling to be applied to translations without editing HTML directly, preventing the risk of breaking the page structure or producing bad HTML. Learn more about HTML markers in ATE
If the issue persists and does not fit the scenario described, we recommend checking other text that may be breaking. If there is no such case, please provide further details.
Regarding the removal of unwanted HTML markers, currently, there is no option to do this directly in the ATE. This has been filed as a feature request. As a temporary solution, you can save the translation with the HTML marker in ATE and then manually edit the translated page to remove the link. Guide to manually editing translations Discussion on removing HTML markers
Please be aware that mixing translation editing between ATE and manual editing in the WordPress editor has some implications and should be approached with caution. For more details, see:
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 you still need assistance, please open a new support ticket.
Problema: Il cliente sta riscontrando difficoltà nel creare duplicati per filiali di un sito, eliminando le lingue non necessarie. Dopo aver eliminato la lingua italiana e i suoi record sul database, molti campi ACF vengono eliminati. I campi ACF e il data entry del sito sono stati creati in italiano, che era la lingua predefinita, per poi essere cambiati in inglese. Soluzione: Se stai riscontrando questo problema, ti consigliamo di seguire questi passaggi: 1. Disconnetti le traduzioni tra loro. 2. Riconnettile indicando una nuova lingua di origine. Puoi trovare maggiori informazioni su questo processo qui. Un'altra opzione è esportare tutti i prodotti nelle varie lingue, cancellare tutti i contenuti, fare un reset di WPML e reimportare tutto impostando l'inglese come lingua di default. Come ultima risorsa, potresti modificare il database, ma noi non consigliamo questa opzione e non possiamo fornire assistenza per codice custom o query di database. Se decidi di procedere in questa direzione, puoi trovare alcuni suggerimenti qui. Tuttavia, questa soluzione potrebbe essere irrilevante perché è datata o non si applica al tuo caso. Se così fosse, ti invitiamo a aprire un nuovo ticket di supporto. Ti consigliamo vivamente di controllare i problemi noti correlati qui, verificare la versione della correzione permanente e confermare di aver installato le ultime versioni di temi e plugin.
Problem: When a WordPress user with editor permissions edits a translation of a post, they are saved correctly but the user is redirected to the "posts" admin view (wp-admin/edit.php) instead of staying on the edited post. Solution: We have identified this issue and it has been addressed in WPML version 4.6.7. We recommend updating WPML to the latest version to resolve this problem. If you're experiencing this issue, please ensure you have updated WPML to version 4.6.7 or above.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If after updating WPML 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. If the problem continues, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client wants to export their English blog texts with markup to have them professionally translated outside of WPML and then import them back into WordPress using XLIFF 2.1. Solution: We have opened a feature request for XLIFF 2.1 support within WPML and will provide an update once we receive feedback from our product manager. In the meantime, if you're experiencing this issue, we recommend checking our documentation on how to manually export and import translations using the XLIFF files. Please note that the solution provided might be outdated or not applicable to your case. 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 issue persists, please open a new support ticket with us.
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.
